A change is breaking if a client that worked yesterday has to change its code, its configuration, or its infrastructure to keep working today. That includes changes that keep every client running while quietly giving it wrong data — those are still breaking, only harder to notice. Most of the list below follows from one rule. On the request side, anything that narrows what the API accepts is breaking, because traffic that was valid yesterday must stay valid.

I’ve been doing vibe coding wrong. This month, I will pick a favorite OSS project of mine each week and contribute all the things I wish it had, starting with Apache Camel.

In the AI era attention is the new gold and this is a good argument against reducing headcount. You need a pool of attention that is going to be available to run all the items in your roadmap very fast.