Microsoft Fabric
Lakehouse topology, Direct Lake, refresh, CI/CD blast radius, and Fabric platform contracts.
Fabric Lakehouse Design: One Lakehouse with Schemas, or Many Lakehouses?
How to choose between multiple Fabric lakehouses and a schema-enabled lakehouse for bronze, silver, and gold, including CI/CD and naming fallout.
Microsoft Fabric Fabric 
Power BI Direct Lake: Do You Still Need to Refresh a Semantic Model?
How to choose notebook, pipeline, or scheduled refresh for lakehouse semantics, and when Direct Lake beats a SQL endpoint for heavy facts.
Microsoft FabricPower BI Fabric Semantic Migration: How Do You Rebind Reports When the Model Moves to Lakehouse?
Why lakehouse migrations fail on NULL versus zero, float pennies, and type rebase settings, and how to treat parity as a contract.
Microsoft Fabric Fabric 
GitHub Actions Fabric CI/CD: How Do You Limit Blast Radius Across Dev Workspaces?
Why Fabric deployment tooling can republish unchanged notebooks and how to design for stable identities and smaller blast radius.
Microsoft Fabric Fabric OneLake Shortcuts: Should Shortcuts Stay Bronze-Only?
Argue that bronze should be a contract of OneLake shortcuts and clean views, not a second physical copy of upstream gold and silver.
Microsoft Fabric Fabric Power BI Gold Semantic Contract: Can You Choose Which Columns Reach the Direct Lake Model?
Argue that device gold tables only become platform assets when unmatched keys, captions, and relationships are explicit in the semantic model.
Microsoft FabricPower BI Fabric Gold + Direct Lake: Direct Lake or Import for Large Event Facts?
Show why telemetry events belong in gold with contract and service-item enrichment and Direct Lake storage mode for volume.
Microsoft Fabric Fabric Workspace Naming: Any Issues with Names Like "(Dev) ProjectName"?
Argue that inconsistent workspace display-name prefixes create operational tax and that a one-time rename with stable catalog names is cheaper than perpetual translation layers.
Microsoft Fabric