Insights
Published when there's something specific to say — a decision, a shipped feature, a problem worth documenting.
Latest
Default-deny, explicit-allow row-level security on every table sounds obviously correct. The real cost shows up later, in performance and in how carefully you have to write each policy.
The default stack across both divisions, and the specific tradeoffs that made it the default -- not a sponsored take, just the reasoning.
A written record of what was decided, what alternatives were considered, and what changed -- including the decisions that didn't work out.
Discovery, design, and a written scope before a single line of code -- the actual sequence client work follows, not a sales pitch.
This isn't a marketing blog. Every post connects to something that actually happened: a decision, a shipped feature, a product update, a lesson worth writing down. There's no fixed schedule — a post goes up when there's something specific to say, not on a calendar built to look active.
