One post tagged with "claude code"

Anthropic recently published The AI-Native SDLC playbook, and it's the most concrete writeup I've seen discussing the effects of cheaper code generation on a delivery process, written by a company where AI authors 80% of merged code. If you run engineering at any scale, I suggest you read it.

It consists of six stages from Plan to Maintain that work in a loop rather than a linear chain of handoffs. Each stage commits an artifact that the next stage reads. The chain of commits is the audit trail. Humans stop reading every line and start judging intent and risk.

GitLab's CEO responded with the line that will likely outlive the playbook itself: "when implementation becomes abundant, trust becomes scarce."

Code is abundant now. Your data is not. An agent can regenerate your code in an afternoon, but it cannot regenerate the production state your company accumulated over years. The playbook's recovery model quietly assumes otherwise, which leads to our claim: the loop does not close at the database.

The database is the one stateful component in your infrastructure. It's where the history lives, and you cannot roll back history by redeploying an older version of it.