Coding Speed is not the Constraint. Context is.
With Cursor, Windsurf, Roo Code, Claude Code, GitHub CoPilot, we are able to generate entire files, refactor codebases, and autocomplete faster than we could ever imaged. P&L leaders expects that speed will ripple across software development. Yet why haven't we seen ROI increases in most organizations?
Because the bottleneck has moved.
Those AI coding assistants improve the same thing: how quickly code gets written once you already know what you’re building.
The actual constraint in software delivery is context -- the domain business domain context and enterprise proprietary knowledge.
Commonly, the context required to work effectively are fragmented. API contracts live in one place, authentication rules in another. Business workflows exist as diagrams. Articles in Confluence are incomplete, mixed with outdated versions or scattered in different projects. Slack threads, Zoom meetings. Legacy code bases. The list goes on.
Developers spend most time reconstructing, understanding the context than producing code. They require support from product managers. This cognitive overhead compounds with every new service, team, and dependency.
With no sufficient context, it is hard if not possible to turn vibe coding into economic gains in enterprise software delivery pipelines.
Read more on my blog: https://maptonik.hashnode.dev/coding-speed-is-not-the-constraint-context-is
Top comments (0)