$ git log --grep="architecture"
Architecture
System design, boundaries, and the shapes we choose.
5 posts
- 5 min read
The Fix Took Production Down for Three Days
In August I wrote about a webhook that let broken services start, and I fixed it. Last week that fix refused to admit its own replacement. There is no correct setting here, only a choice of failure and a bill that comes with it.
- 3 min read
Find the Path With a Person Waiting on It
Every system has one path where a human is physically standing there, waiting. Find it, then take everything optional out of it — a short piece on why the doors kept scanning while nobody could log in.
- 6 min read
Roles Are Not Permissions: Why Hiding a Page Is Not a Guard
The menu item disappeared, so the feature was secure. Then someone typed the URL. What multi-tenant authorization taught me about the difference between what a user sees, what a user is, and what a user may actually do.
- 5 min read
Overengineering: Future-Proofing, Ego, or Just a Way to Learn?
I knowingly built 25 microservices for a prototype that could have been a monolith. Here's why I'd do it again — and when you shouldn't.
- 4 min read
gRPC vs REST: Debugging, Observability, and the Reality of Adoption
REST feels like home because you can debug it with a browser tab. gRPC is better on paper — so why does adoption still hurt?