Enterprises are increasingly investing copious amounts of cash in artificial intelligence without much to show for it. This could be, in part, because the wrong people are leading the change. The common assumption is that AI will replace junior developers, but the real opportunity lies in combining the fresh perspective of young developers with the hard-won judgment of senior engineers. The future of software development belongs to teams that blend both.

The factory doesn't redesign itself

Zara Zhang recently pointed to Paul David's classic 1990 paper, "The Dynamo and the Computer," as a way to understand why so many companies have adopted AI without meaningful results. David's argument, simplified, is that electricity did not immediately transform factories. For a long time, factories simply swapped the central steam engine for an electric motor while keeping the same layout, the same workflows, and the same assumptions. Electricity was new, but its potential was stifled by being force-fitted into old factory systems.

The big productivity gains came later, when factories stopped treating electricity as a cleaner steam engine and started redesigning work around smaller motors distributed throughout the factory. Once each machine had its own motor, the factory no longer had to organize itself around a single driveshaft. Work could be reorganized around the flow of production.

This is a decent description of where many enterprises are with AI today. Companies buy copilot licenses by the thousands, wire agents into existing applications, and then wonder why results are so uneven. This is the equivalent of swapping the steam engine for an electric one and declaring the AI modernization work done. It is not. The real payoff will not come from asking AI to write the same tickets slightly faster. It will come from changing how teams define work and how — and what — developers build. The "factory" has to change.

Experience cuts both ways

There is an obvious danger in romanticizing youth. Plenty of bad software has been written by people with unlimited confidence and limited context. Enterprises need software that works, but "works" also means it complies, scales, respects security boundaries, and more. This is where experienced developers matter. A lot.

The agent era makes engineering judgment more important than ever. AI makes it easier to generate code, but easier code generation can become easier technical debt generation. The limiting factor becomes less "Can we create something?" and more "Can we create the right thing, in the right place, with the right constraints?" Taste is required.

Senior engineers are often better at seeing those constraints because their experience gives them taste. They know why a weird validation rule exists, and they remember the customer who depended on undocumented behavior. They understand why a simple schema change can turn into a multi-week migration. But experience also has a shadow side, because it can make the current process feel inevitable. A senior engineer may see an AI assistant as a faster autocomplete because that is the easiest way to fit AI into an existing mental model. A junior developer, less invested in the old workflow, may ask more interesting questions: Why are we doing this ticket at all? Why isn't the spec executable? Why can't the agent generate the test harness first?

It is not that experienced developers do not know these questions. Rather, they may not have the energy to rage against the machine.

The value of inexperience

The worst way to use junior developers in the AI era is to treat them as cheaper versions of senior developers. That was always a bad idea, but AI makes it worse. If the job is "take this ticket, generate some code, and send it to a senior person for review," the junior developer becomes a human wrapper around a coding assistant. That helps no one. The junior does not learn much, the senior gets buried in review, and the enterprise ends up with more code, which is hardly a good thing.

Instead, junior developers should be given room to explore new workflows, with just enough oversight from experienced colleagues. That might mean giving newer developers interesting questions to answer, such as:

• How would we redesign onboarding if every internal API had an AI-readable contract and examples that actually worked?
• How would we change code review if the agent produced a change summary, test evidence, dependency risk, and rollback plan with every pull request?
• How would we build features if product requirements were written as executable acceptance tests rather than vague prose?
• How would we reduce toil if agents could safely perform routine migrations, dependency updates, or incident triage within clearly defined boundaries?

These are not toy problems. They are not "junior work." They are exactly the sort of process redesign that enterprises need but generally avoid because everyone is too busy running on the existing hamster wheel.

Finding the balance

So what should engineering leaders do? First, stop treating AI adoption as an individual productivity contest. We seem to be moving away from the idea that "lots of tokens" equals "great engineer," but the fact that we even flirted with it is damning. Measuring AI productivity in lines of code written is a stupid mistake. Instead, ask questions like, "What part of our software delivery process no longer makes sense?" AI's biggest gains will come when we change how we specify, test, review, and ship software.

Second, mix up AI workflow teams. Not committees or PowerPoint-producing centers of excellence. Combine two or three newer developers who are already fluent in AI-native tools with two or three senior engineers who understand production, security, architecture, and organizational constraints. Then give them a real workflow to redesign, such as dependency upgrades or test creation.

Third, make the senior engineer's job less about saying no and more about defining the guardrails within which others can say yes. Golden paths are key to using AI effectively. Good senior engineers should define the paved roads: approved patterns, test requirements, observability standards, and so on. Then let junior developers and agents move quickly inside those boundaries.

Fourth, reward deletion. This may be the most important point. Returning to the factory electricity metaphor, enterprises will fail with AI modernization if they simply add AI without removing outdated processes. Deleting legacy steps, redundant approvals, and unnecessary handoffs is as valuable as adding new capabilities.

Bring everyone to the table

The future of software development will not belong to the young, and it will not belong to the old. It will belong to teams that combine the talents of both. Newer developers bring impatience. They are less likely to accept the existing workflow as sacred. They are more likely to try weird tools, compose them in unexpected ways, and wonder why enterprise software development feels like a ritualized exercise in waiting for permission.

Experienced developers bring judgment. They know that software has users, auditors, attackers, budgets, latency, history, and consequences. They know that the right answer is often boring, and boring is good. Enterprises need the developer who asks why the factory is still organized around the old drive shaft, and they need the developer who knows which machines will kill someone if moved casually. In sum, every development team needs people who know why the old system exists, as well as those who do not.

The history of technology is full of examples where the established experts missed the next wave because they were too invested in the old way. It is also full of examples where enthusiastic newcomers built something fragile because they ignored the lessons of the past. AI is neither the first nor the last technology to require this balance. The companies that get it right will be those that deliberately create environments where junior developers can challenge assumptions and senior developers can provide the guardrails that keep experiments from becoming disasters. That is not just a nice-to-have. It is the only way to make AI work for the long term.

Source: InfoWorld News