Seven Rules for Evolving a REST API Without Breaking Clients
The seven rules I follow to change a REST API without breaking the web apps, mobile apps and integrations that use it.
The seven rules I follow to change a REST API without breaking the web apps, mobile apps and integrations that use it.
New tools ship every week. How to stay current where it matters, and why fundamentals last longer than any framework.
Burnout rarely comes from one hard week. It usually comes from work that never quite stops. Ways to keep a pace you can sustain for years.
Every network call will eventually fail or hang. How to stop one slow dependency from taking your whole service down with it.
Why 'save to the database, then publish an event' quietly loses data, and how the outbox pattern makes events as reliable as your database.
Renaming a column shouldn't need a maintenance window. How to change a live database in separate, reversible deploys while old and new code run side by side.
Why I usually start with a well-structured monolith instead of microservices, and the signs that a module should become its own service.
What changes when your teammates and clients are 13 hours behind or 2 hours ahead: schedules, hand-offs and keeping your evenings free.
Habits that keep you productive, visible and trusted when your team and clients are spread across time zones.
How I set up a typed and versioned React component library, from the folder structure to publishing and getting teams to use it.
How to set up JWT auth in Express with short-lived access tokens and rotating refresh tokens in httpOnly cookies, plus the common mistakes.
How I mentor developers so they become independent quickly, while still leaving time for my own work.
How to run code reviews that catch bugs and teach the team without holding up everyone's work.
Code, reviews, meetings, mentoring and production issues all compete for the same day. The routine I use to keep time for deep work and still unblock the team.