“Normal” engineers are the key to great teams

Debate over “10x engineers” and what they really are

• Commenters strongly disagree on whether 10x engineers meaningfully exist.
• One camp says there’s a clear long tail of talent: a few people consistently solve hard, high–leverage problems, design key systems, or ship massive value; they’re needed for novel domains (AI, compilers, core infra).
• Another camp argues many so‑called 10x engineers are just fast mess‑makers: cutting corners, ignoring maintainability, and leaving tech debt and brittle systems for others. Those people are “10x problems,” not 10x engineers.
• Several note that the original “10x” research compared best vs worst, not best vs average; the meme has drifted and is now mostly rhetorical.

Teams, systems, and process vs. lone heroes

• Many argue that great organizations are those where average but competent engineers can move fast because systems, tooling, and processes support them.
• They emphasize: clear ownership boundaries, good documentation, CI/CD, observability, and a healthy culture over mythical heroes.
• Hero programmers can become single points of failure and create bus‑factor risk; some products ended up requiring a whole support team around a single “wizard.”
• Others counter that in practice a small minority often carry most of the technical load or set the direction; pretending everyone contributes equally is seen as managerial self‑deception.

Behavior, culture, and sustainability

• Multiple commenters describe being or working with “10x” people who burned out, rewrote everything at 3 a.m., or insisted on shiny tech while undermining business needs. Over time they saw that focused, boring, careful work beats crunch and rewrites.
• A recurring theme: true high performers multiply others—through mentoring, pairing, design clarity, and removing friction—rather than just typing faster.
• There’s criticism of finance‑style valorization of extreme output and wealth; others say tech has indeed adopted that culture, attracting people who optimize for money and status.

“Normal” engineers and long‑term value

• Many praise solid “1x–3x” engineers who: write readable code, avoid over‑engineering, care about users, and can be trusted to ship predictably. Those people keep systems running for years.
• Several note the real threat is not lack of 10x engineers but prevalence of 0.1x or negative contributors who introduce bugs, complexity, and constant firefighting.

Metrics and incentives

• Measuring individual productivity is seen as fundamentally fraught: tech debt, design trade‑offs, and long‑term impact are hard to quantify.
• Attempts to treat engineers like factory workers (tickets closed, LOC) are viewed as corrosive, pushing short‑term output over durable systems and effective teams.