Notes
Engineering and architecture writing.
Articles
Choosing a stack by proof of concept
A proof of concept answers a decision, not a demo — one question, one timebox, criteria written down first, including the one almost nobody tests for.
Why your DynamoDB app got slow as data grew
Five patterns that are invisible at a thousand records and fatal at a hundred thousand — and how to find them in your own code before you change anything.
When per-user identity pricing stops working
Managed identity costs per user; self-hosting costs per engineer. Where the lines cross is a calculation most teams skip — and the lock-in is not the protocol.
A release plan is a return plan
Promoting a change through dev, staging and production lowers the risk and proves nothing. What has to be written down first is how to put production back.