---
title: "Comment by Ascendra Ventures on \"AI Can Build the Whole Stack. Why Does Specialization Still Matter?\" | Hashnode"
description: "The distinction between wearing many hats and being an expert in all of them is the one that gets lost in a lot of current hiring talk. AI makes it possible for"
url: "https://hashnode.com/posts/ai-can-build-the-whole-stack-why-does-specialization-still-matter/6ada1973d6dc982a9c3856c7/comment/6adac8e7a48cd2e249e9404b"
---

[Discussion](https://hashnode.com/posts/ai-can-build-the-whole-stack-why-does-specialization-still-matter/6ada1973d6dc982a9c3856c7)

Comment [AI Can Build the Whole Stack. Why Does Specialization Still Matter?](https://hashnode.com/posts/ai-can-build-the-whole-stack-why-does-specialization-still-matter/6ada1973d6dc982a9c3856c7)

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[Oct 23](https://hashnode.com/posts/ai-can-build-the-whole-stack-why-does-specialization-still-matter/6ada1973d6dc982a9c3856c7/comment/6adac8e7a48cd2e249e9404b)

The distinction between wearing many hats and being an expert in all of them is the one that gets lost in a lot of current hiring talk. AI makes it possible for one engineer to produce a database schema, a pipeline and a frontend in a day. It does not give that engineer the experience to know which part of the output is quietly wrong.

Your point about tradeoffs is the honest version of the argument. If a company gives one person a whole team's responsibilities, it is choosing speed and accepting more risk in the areas that person knows least. That can be a fine choice, as long as it is made on purpose.

On client work we handle it by splitting a project into clearly defined problems and asking which ones carry real risk, usually security, data and payments. Those get a specialist review even when the rest is built quickly by a generalist.

Which area do you see generalists underestimate most often?