July 1, 2026
When engineering teams adopt AI, usually, the business expects an increase in engineering output and delivery speed. In reality, that rarely happens, teams may have some increase in output, code gets written faster, pull requests get opened sooner, raw output goes up.
However that reaches a ceiling very fast. The business metrics barely move. Cycle time doesn't collapse. Throughput doesn't 10x. Deadlines don't suddenly become trivial.
Sometimes teams report a modest improvement. Sometimes, things get worse, code piles up into code review and manual QA, releases get bigger, riskier and things break in production.
Its not about models or tools #
It's tempting to read this as a limitation of the models. It isn't. Today's models are already capable of producing large volumes of correct code across a wide range of tasks. In most teams, they're no longer the bottleneck.
What most companies fail to understand is that by simply adopting AI coding tools they're just accelerating one step of the pipeline. The real constraint now sits everywhere around the act of writing code:
- Requirements clarification and task decomposition
- Code review
- Testing and validation
- Deployment and release
In other words, the entire software development lifecycle (SDLC) outside the coding phase.
Amdahl's Law applied to software delivery #
Amdahl's Law comes from parallel computing. It says the maximum speedup you can achieve is capped by the portion of the system that can't be parallelized. Even with infinite compute, the sequential part becomes the bottleneck — it defines the upper bound.
Now map that onto software delivery: Even if AI makes coding 10x faster, your total delivery speed is capped by everything else.
A concrete example
Take a fairly typical breakdown (the numbers are made up just to make the point)
Without AI:
| Stage | Time |
|---|---|
| Coding | 8h |
| Review | 4h |
| Testing | 4h |
| Deployment | 2h |
| Total | 18h |
After AI:
| Stage | Time |
|---|---|
| Coding | 1h |
| Review | 4h |
| Testing | 4h |
| Deployment | 2h |
| Total | 11h |
The speedup:
S = 18 / 11 ≈ 1.6×
An 8x improvement in coding efficiency turns into a 1.6x improvement in delivery. That's exactly what most teams are experiencing. And that's where a lot of the disparities in AI coding and productivity discussions come from.
Coding is not the bottleneck anymore #
Here's the shift many teams haven't internalized yet: delivery speed is no longer bound by how fast you write code.
Code generation is no longer an expensive resource. Review, validation, and safe integration are. You can't ship faster unless you can:
- Review faster
- Verify faster
- Merge faster
- Manage risk at scale
A faster engine doesn't help if half the road is blocked. The work now isn't improving the engine, it's clearing the road.
From Code Generation to Risk Validation #
This new world puts renewed pressure on having strong fundamentals: robust CI/CD pipelines, comprehensive automated test suites, and well-designed release and rollout strategies. These are and have always been the systems that make high-velocity development sustainable.
We are also now seeing agents, more and more, moving off the developer's machine, becoming more autonomous and capable of handling increasingly complex work. Agents are now triggered by automations and continuous loops that continuously push new code, creating a load that can become unsustainable. We can now have small teams with pressure on the software delivery lifecycle that was only previously seen on large companies.
To keep pace, we'll need agents to actively support the parts of that lifecycle now under high load. First-pass code reviews, automated security analysis, and intelligent triage systems become critical. Agents can classify risk, suggest reviewers, and surface potential issues early, helping developers focus their attention where it matters most.
Raising the Ceiling #
These are the questions we need to ask ourselves to move fast and reap the benefits in this new world:
- How quickly can the team review new changes?
- Do we need human inspection for all changes?
- How much confidence do we have on our automated suite?
- Do we know the level of risk of a given change?
- What level of review does a low risk change need?
- How quickly can we deploy, with what cadence?
- Where is human time actually being spent?
- Are humans doing low value work that can now be done by AI?
These questions reveal where the true constraints now lie. They expose inefficiencies in validation, review, deployment and time allocation, that were previously hidden by slower development cycles.
Answering them is how teams raise their ceiling. Writing code faster is a small part of the delivery lifecycle teams need systems that allow them to ship faster, with confidence.
Workshops #
Beyond AI-Assisted Coding: Engineering the AI-Powered SDLC
Workshop: September 26, 2026
Enrollment closes September 21, 2026
Learn how to move beyond AI-assisted coding to agentic engineering: workflows that operate across the full SDLC, built on specification, orchestration, verification, and continuous improvement loops.