
Data Architecture Patterns: Warehouse, Lake, Lakehouse, Fabric and Mesh
Warehouse, lake, lakehouse, fabric and mesh compared by data flow, ownership, governance and consumption, with guidance on when to pick each.
Clusters, workloads, Helm and the interview questions that go with them.
View all 90 postsAI agents, tool calling and the Model Context Protocol (MCP).
View all 3 postsLLMs, local models, GenAI on Azure and AI coding tools.
View all 43 postsSecurity in the pipeline: SAST, SCA, secrets and supply chain.
View all 18 postsMetrics, logs and traces with OpenTelemetry and Grafana.
View all 21 postsInfrastructure as code with Terraform and friends.
View all 12 postsIdentity, network and workload security in the cloud.
View all 30 postsImages, containers and local container tooling.
View all 19 postsBuilding and running a home lab for hands-on cloud and Kubernetes practice.
View all 11 postsQuestion banks for DevOps, cloud, security and architect roles.
View all 18 posts
Warehouse, lake, lakehouse, fabric and mesh compared by data flow, ownership, governance and consumption, with guidance on when to pick each.

How payers review whether care is medically necessary (prospective, concurrent and retrospective review) and why it leads to denials.

When pre-approval is required, how a request moves between provider and payer, and why delays and denials happen.

The three code sets on every claim (diagnoses, procedures and supplies), plus modifiers and how codes link together.

A practical guide with lab, office-visit and durable medical equipment examples, and why Medicare and commercial payers treat the code sets differently.

How payers and repricers apply contracted rates, fee schedules and DRGs to billed charges, and what that means for providers and patients.

What a provider network is, how payers contract with providers, and why the same visit can cost very different amounts depending on network status.

How each plan type trades off cost, choice of provider and referral rules, with examples of which one fits which patient.

Why insured patients still get bills: a worked example of how a claim's allowed amount is split between the plan and the patient.

A hands-on walkthrough of Safe Harbor and Expert Determination, then a Python framework that de-identifies and re-identifies PHI in 837 and 835 files.