Will AI Bring Back the Era of Giant Engineers?

Posted on May 07, 2026 · 20 mins read · English · Nuwan Jaliyagoda

Review Technology AI Engineering Philosophy

When was the last time you heard that one person invented something that changed the world?

Most of us can quickly name some century-old examples: Thomas Edison and the light bulb, Alexander Graham Bell and the telephone, Marie Curie and radioactivity, Nikola Tesla and alternating current, Alan Turing and computation. These names are powerful because they simplify history. They make invention feel human, memorable, and dramatic. They are the “giant engineers”.

But can you name a few from your generation? From the last decade? Yes, you get the point; modern engineering has not worked like that for some time. The systems that shape our lives today; cloud platforms, artificial intelligence, quantum computers, and supersonic aircraft are rarely produced by isolated individuals. We do not even know who invented them. What happened to innovation?

Most modern inventions are built by teams of engineers, institutions, research communities, and open-source ecosystems. So, within the last few decades, the so-called “giants era of engineering” was over. Not because individual brilliance disappeared, but because the complexity of modern technology became too large for one mind to command.

Now artificial intelligence (AI) complicates that conclusion.

AI coding assistants, research copilots, design tools, and agentic workflows are beginning to give individual engineers access to capabilities that previously required teams. With a good AI model, a single developer or engineer can scaffold a full-stack application, explore architecture alternatives, select the best framework from a list of hundreds, write documentation, and analyze large bodies of technical material with a speed that was unrealistic a few years ago.

This raises the central question of this article: “does the emergence of AI bring back the era of the giant engineer?” Let’s go through the question and see.

From Lone Genius to Collective Engineering

The stories from the giants’ era of invention are simple: a brilliant person sees what others cannot, creates something new, and changes history.

It is an attractive story, but it is usually incomplete. Even famous inventions were often built on networks of prior work. Edison did not invent electric light from nothing; he improved and commercialized a practical incandescent lighting system after many earlier inventors had explored electric illumination.

The “single inventor” story is often a compression of a larger system of experiments, failures, patents, manufacturing constraints, capital, and distribution. But what made the difference in between then and now? It is modern communication. With the global village, the collective nature of “knowledge production” is clearer. Even tiny changes become public and accessible to many people, so no one can dominate access to knowledge.

In a widely cited Science paper, “The Increasing Dominance of Teams in Production of Knowledge” (Wuchty, Jones, and Uzzi, 2007^[1]) analyzed 19.9 million research papers and 2.1 million patents across five decades. Their conclusion was direct: teams increasingly dominate solo authors in producing knowledge, and teams increasingly produce highly cited work as well.

Another important fact that changed over time is the burden of knowledge. To contribute meaningfully to a mature field, an engineer or researcher must understand more prior work, more tools, more constraints, more standards, and more failure modes. The Renaissance-style engineer who can master an entire domain alone becomes less realistic as the domain expands.

This is why the modern engineer became less like a lone inventor and more like a participant in a knowledge network.

The Emergence of AI

Over the last five years, we can see that AI is changing the norms of the world, and it attacks one of the main reasons the giants era declined: the cognitive bottleneck.

An engineer no longer has to manually search through every document, memorize every mechanism, produce every boilerplate test, or read every line of a design. A researcher can summarize literature, generate hypotheses, translate between domains, and explore unfamiliar methods faster. A technical lead can use AI to draft architecture decision records, compare implementation options, or simulate review questions before design meetings.

A controlled experiment on GitHub Copilot asked developers to implement an HTTP server in JavaScript. Developers using Copilot completed the task 55.8% faster than those without it (Sida Peng et al, 2023^[2]). In another field experiment involving consultants, researchers from Harvard Business School and collaborators found that participants using GPT-4 completed 12.2% more tasks and completed them 25.1% faster on tasks within the frontier of AI capability ^[3]. These are not philosophical claims. They are measurable changes in task execution.

But the same evidence also warns against naive optimism. The Harvard/BCG study found that when tasks were outside AI’s effective capability frontier, participants using AI were 19% less likely to produce correct solutions ^[3]. A 2025 randomized controlled trial by METR found that experienced open-source developers working on mature repositories took 19% longer when allowed to use early-2025 AI tools, despite expecting AI to make them faster ^[4].

So what does that mean? AI does not uniformly make engineers faster! It changes the shape of engineering work. It accelerates some tasks, slows others, and introduces new responsibilities around verification, context, security, and maintainability.

The New Giant is not a Lone Genius?

If AI ever brings back the giant engineers again, they will look different from the historical archetype. The old giants were imagined as people with extraordinary internal knowledge. The new giant may be a person with extraordinary orchestration ability. An engineer who knows how to ask the best questions, decompose problems, evaluate machine-generated outputs, and decide when to trust or question AI. Their power might not come only from knowledge, but from how well they can coordinate tools, models, data, tests, people, and constraints.

It is something like this: a weak engineer can generate more weak output. A stronger engineer with AI can explore more alternatives, detect flaws early, and move faster through the work. But the difference between the two may become sharper, not smaller. AI appears to democratize capability, but it may also amplify inequality between shallow users and deep users.

The giant engineer of the AI era is therefore not someone made by AI. It is someone extended by AI.

The Philosophy of Autonomy, Knowledge, Creativity, and Responsibility

Now, it is the best time to discuss some philosophy: how AI can change the life of an engineer. I have identified four main facts.

First, AI changes autonomy. An engineer can act with greater independence because AI reduces dependence on prior knowledge, expert support, or access to resources. A solo founder can build a prototype faster. A junior engineer can build apps with frameworks they are not even familiar with. A researcher can go through an entire body of literature much faster. But autonomy without understanding is fragile. Engineers may become dependent on opaque systems.

Second, AI changes the way we understand knowledge. Engineering knowledge becomes less about memorizing syntax and more about understanding. The value shifts from recall to judgment. Knowing the exact command matters less than knowing whether the command is safe, scalable, secure, and appropriate in context.

Third, AI changes creativity. It makes ideation cheaper. An engineer can generate more design alternatives, more tests, more user interface alternatives, and more architecture sketches. But cheap ideation can also create noise. Creativity is not just generating options; it is selecting and refining the right ones.

Fourth, AI complicates responsibility. If an AI-generated code path introduces a security flaw, who is responsible? The model provider? The engineer who accepted it? The organization that encouraged AI use without review standards? The team that merged it? It is getting more complicated. We may get more individuals with more leverage, but leverage without accountability is dangerous.

Next, take a look at this under the ethical and social considerations. The possible return of the giant engineer has both positive and negative consequences.

On the positive side, AI can reduce the barriers to creation. A small team or individual can build what previously required a large team. Engineers with fewer resources can get high-quality technical assistance or expert mentorship through AI models. Researchers can use AI tools to navigate literature and accelerate hypothesis generation. Open-source maintainers can automate documentation and focus more on implementation.

On the negative side, AI may concentrate power. The best models, compute infrastructure, data pipelines, and deployment platforms are controlled by a small number of organizations. If the future giant engineer depends on proprietary AI infrastructure, then the real giant may not be the engineer; it may be the platform.

Also, one of my biggest concerns is that, if “AI allows fewer people to produce more output”, organizations may undervalue mentoring, junior hiring, and long-term capability building. This would be short-sighted. Today’s senior engineers exist because earlier systems gave them time to learn. If AI removes entry-level learning pathways, the industry may weaken its future expert base.

Counter Arguments

It is always better to have some counter-arguments for the hypothesis. We should question the thought, “will AI bring back the era of Giant Engineers”.

One major counterargument I see is that AI will make individual engineers less important, not more. If everyone has access to the same tools, maybe engineering becomes commoditized. However, even if some routine coding tasks lose value, higher-level engineering judgment becomes more valuable. When implementation becomes cheaper, choosing the right implementation matters more. When code becomes abundant, architecture, reliability, security, and product clarity become scarcer.

Another point is that AI productivity studies are too early to support strong conclusions. The tools are changing quickly, and results depend heavily on task type, developer experience, codebase maturity, and measurement method. That is exactly why the right conclusion is balanced: AI is neither magic leverage nor useless hype. It is a capability frontier that engineers must learn to navigate.

Conclusion

The previous giants era of engineering ended because modern technology became too complex for isolated individuals. But now, AI challenges that reality by giving individuals access to unprecedented cognitive and creative leverage. However, in my personal opinion, AI will not bring back the old era of giants, but it may bring a new era: an era with engineers who can combine deep fundamentals, machine assistance, systems thinking, ethical judgment, and disciplined verification.

The future may no longer reward engineers who merely generate more code. It will reward engineers who can decide what should be built, understand what the machine produced, verify whether it is correct, and take responsibility for its consequences. AI may give individuals the reach of a team. But only engineering judgment can turn that reach into reliable progress.

The giant engineer may return, but not as a lone genius standing above the system. The new giant will be the one who knows how to think with the system, build through the system, and remain accountable inside the system.

What do you think about it? Yes, this post does not have a comment section to share your thoughts. But you are invited to share your thoughts in my LinkedIn post here.