Found at “The New Software Lifecycle” on 2026-07-19T10:59:22+02:00.

AI compresses the lifecycle, but unevenly, and the unevenness is the whole story. Implementation drops from weeks to hours. Requirements, architecture, and verification stay slow because they’re judgment work. So specification quality becomes the bottleneck, and verification moves to the middle.—Addy Osmani

About this new AI-driven SDLC, Kin Lane asked me and other API product folks on LinkedIn:

How does this apply to the API lifecycle?

This is my answer:

The article and the paper it refers to validate the importance of doing API Design the right way: capturing JTBD, writing user stories, understanding consumers’ needs, iterating using API prototypes, and validating before implementing.

Building things incorrectly isn’t a risk anymore because the cost of implementation has dropped dramatically. LLMs can now build what you ask them to in any programming language, bug-free. What’s now a risk is building the wrong things. That’s why validating your API design is so important.

A “side effect” of this new SDLC is that now almost anyone can build an API. You don’t need to be a developer to be able to design an API, implement it, and release it. You don’t even have to know OpenAPI or any other API specification. What you do need to know, however, is your domain. You need to understand what you’re building and who you’re building for.