The Pitfalls of DevOps and Full‑Stack Expectations in Start‑ups

Recent trends that the author dislikes are the rise of DevOps and the notion of “full‑stack” developers. As DevOps becomes more popular, it feels as intolerable to the author as the decline of x86 and single‑core CPUs.

DevOps is described as close collaboration that blurs the lines between pure developers, operations, and QA, breaking the traditional waterfall cycle and requiring developers to also be responsible for testing and release environments.

This expanding responsibility has led to the demand for “full‑stack” developers who can code, test, perform business analysis, act as system administrators, and serve as DBAs. The author questions whether any organization, especially those that are not startups, should be forced to operate like a fledgling company.

In a typical startup with a small team, developers often have to take on DBA duties and other roles because dedicated teams do not exist. This multitasking extends to all positions—development, QA, deployment/operations analysis, system administration, and database administration—leaving developers with no choice but to wear many hats.

The article points out a hierarchical view of technical roles: developers at the top, followed by system administrators and DBAs, with QA, operators, and release managers at the bottom. While a skilled developer can perform lower‑level tasks, the reverse is not feasible; a QA engineer cannot act as a developer, nor can a build engineer become a DBA without the necessary expertise.

Specialization exists for a reason: human knowledge is limited, and constantly switching tasks is costly. Forcing developers to assume other specialized roles results in less time spent on actual coding, the need to keep up with a vast knowledge base, and eventual burnout.

The author warns that treating developers as interchangeable “technical labor” harms both the individuals and the quality of software. Companies should let developers focus on writing code rather than diluting their role with unrelated responsibilities.