Why “Just One Programmer” Is a Dangerous Myth in Software Projects

Several respondents on Zhihu share stories that illustrate a common misconception: project owners claim they are "just missing a programmer" and expect a single fresh graduate to deliver a complete system. The author argues that this phrase masks a deeper problem—most projects actually need a whole technical ecosystem comprising architects, analysts, developers, testers, and operations staff.

One anecdote describes a university department requesting a simple website with news, photos, management, and grade‑query features. The author sketches a three‑column homepage in Dreamweaver, shows it to the requester, and receives a vague, disappointed response. Later, the requester criticizes the prototype for missing features, revealing a mismatch between expectations and the minimal deliverable.

Another case involves a colleague from a state‑owned enterprise who wants to launch an internet‑based venture (CMS, crowdfunding, CRM, payment, product wiki) with a budget of 30 w and a six‑month timeline. Despite lacking market research, customer leads, or a clear promotion plan, the team is urged to outsource a static five‑page site for a few thousand dollars, then later to emulate Apple’s design, and finally to copy e‑commerce sites, exposing the unrealistic scope and misunderstanding of required resources.

The author generalizes the pattern: outsiders tend to oversimplify other industries while over‑estimating the importance of their own, leading to statements like "we just need a designer" or "we just need a product manager". The core message is that saying "just one programmer" is equivalent to saying "nothing else is needed," which is false and sets projects up for failure.

In conclusion, the author urges professionals to avoid such misleading shorthand, recognize the full spectrum of technical roles needed for successful software delivery, and refrain from using comforting but inaccurate phrases that mask the real work required.