You’re Not Replacing Developers. You’re Creating More of Them
Why enterprise CTOs need a plan for scaling vibe-coding beyond the engineering org.
Vibe-coding isn’t replacing developers.
It’s multiplying them.
AI tooling, LLM copilots, and low-friction APIs have made it possible for analysts, architects, and even operations staff to build working software without involving product or engineering teams.
At first, that sounds like a win: more builders, more velocity, more innovation.
But look closer.
These new builders don’t bring the same habits, tooling expectations, or architectural instincts as your traditional dev teams. They’re shipping features without unit tests and designing workflows without thinking about observability. Stitching together APIs without planning for integration debt.
Suddenly, your org has more developers. Just... less disciplined ones.
That’s not a knock. It’s a reality.
As enterprise CTO, you are now responsible for supporting two distinct types of development muscle:
Your core engineers think in systems, pipelines, and scale.
Your domain-driven builders, who think in outcomes, workflows, and prompts.
Both are valuable.
Both accelerate business outcomes.
But both need radically different support models.
Next week, I’ll release a deeper dive into supporting the modern business process/analyst vibe coder.
I’d love your in-the-field feedback. Have you seen vibe coding outside of your best and brightest experienced architects? What have been the successes and failures?