Systems / 15 min read / 0 views
What I learned migrating a monolith
Planning slices, measuring risk, and preserving product momentum during technical change.
Choose slices people can understand
A migration plan should be visible enough for product, support, and engineering to share the same map.
Recent posts
Fresh notes from the archive, ordered by latest publication.
Architecture/12 min/9 views
A practical guide to contracts, retries, backoff, and keeping service interfaces pleasant under pressure.
Operations/8 min/4 views
A calm workflow for tracing slow requests from browser waterfall to database query plan.
Teamwork/6 min/5 views
How to make reviews faster, kinder, and more useful without lowering engineering standards.