This article clearly comes from a very lived experience. There’s so much that resonates about not just this transition from traditional coding to AI-assisted/AI-enabled coding. The narrative is a little dev centric, but it’s not wrong in identifying that so much of the end-to-end process timing is outside of the development team.
This paragraph, however, really hit home:
3. The deploy trust spiral
I can’t count the number of teams I’ve worked with that were scared to deploy. Tests are flaky, observability is a mess, nobody trusts the canary process, and the last time someone deployed on a Thursday it ruined everyone’s weekend. So what do they do? They batch changes into bigger releases. Which are riskier. Which makes deploys scarier. Which makes everyone batch more.
Congratulations, you’ve built a fear spiral.
Now add faster code output to this environment. More code, same terrified deploy culture. The batches get bigger. The risk gets higher. The releases get less frequent. You have given a team that was already scared of shipping even more reasons to not ship. Incredible work.