Acronyms, Collisions, and the Cost of Not Asking
I promised a follow-up to a post about tech vocabulary,[1] and this is it. That one argued that dramatic words and vague words fail the same way: they carry attitude where information should be. I…
The Blast Radius Was Four Rows
A while back I read an incident report that described the “blast radius” of a “catastrophic” data issue. I kept reading, looking for the part where something exploded. The actual damage: four rows in a…
A Decision Framework (and When to Stop Arguing)
This is the finale of the “Where Does Business Logic Live?” series. Over five posts we have looked at , the , the , the reality, and the . Now let’s make it actionable. This…
Security, Misconceptions, and Hybrid Architectures
This is Part 5 of the “Where Does Business Logic Live?” series. We have made the , the , and the comparison. Three things remain before we can build a decision framework: how security actually…
Where Does Business Logic Live? A DBA’s Guide to the Stored-Procedures-vs-Application-Layers Debate
Few architecture questions generate more heat and less light than this one: should business logic live inside SQL Server stored procedures, or outside the database in application layers? Ask a room of developers and DBAs…
ADO Doesn’t Mean What You Think It Means
You’re in a meeting. Someone says “ADO.” Your brain - conditioned by 20+ years of muscle memory - immediately conjures up connection strings, recordsets, and ADODB.Connection. Then you realize they’re talking about a CI/CD pipeline….