Why Most Developers Never Become Software Architects – Insights from Top‑Voted Zhihu Answers

In typical small development teams of around ten people, the architect role is rare and usually occupied by the most senior developer, so architects account for less than 10% of engineers.

Original Zhihu question: zhihu.com/question/36658435

Answer 1 (1300+ upvotes)

Architects and programmers are fundamentally different; architects think in a way that most programmers do not, even though both can write code.

Answer 2 (1500+ upvotes)

Being an architect is not a particularly enjoyable career path. Developers find the work more fun and can quickly gain recognition in areas such as graphics, artificial intelligence, blockchain, or security, whereas architects rely mainly on accumulated experience and the number of projects.

Answer 3 (1800+ upvotes)

Most teams only need one person to spend a few days each month on architectural decisions; a ten‑person team needs at most one part‑time architect, while a team of over fifty people may require a dedicated architect.

Answer 4 (3300+ upvotes)

Writing code and doing architecture are distinct activities. Architects decide how to split a system into modules and where to deploy them, and they must be able to hold the technical direction of the whole team.

Answer 5 (5000+ upvotes)

Many programmers lack opportunities to practice architecture. Working on high‑concurrency systems at large e‑commerce companies provides the experience needed for architect roles, but only a few developers get such exposure, creating a feedback loop that separates experienced architects from the rest.

One concrete example mentioned is the open‑source microservice project mall‑swarm on GitHub, which has over 11 K stars and demonstrates a full‑stack architecture covering Spring Cloud components and Kubernetes deployment.