A concise editorial brief on the 10x developer myth is quietly killing careers, with the trade-offs and questions that matter before your next move.
The myth begins with a comparison
Two developers receive the same vague comparison: one is a “10x” individual contributor, the other is merely reliable. The label hides different systems, tickets, reviewers and risk tolerances. One may be shipping a new surface; the other may be preventing a migration failure. Before accepting the ranking, ask what outcome and context the comparison includes. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
Speed has a shadow
Fast implementation can be valuable when the problem is understood and the change is safe. Speed creates debt when it bypasses discovery, testing, accessibility, security or handover. The cost often arrives after the applause, paid by the next engineer or the on-call rotation. Ask what had to remain true for the fast result to be good. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
The quiet maintainer
A maintainer notices a recurring alert, updates a runbook and removes a fragile dependency. Nothing flashy appears in a demo. The next incident is shorter because the system is easier to understand. Such work can be hard to attribute and easy to ignore, which is why engineers should record the baseline, decision and observed consequence without inventing savings. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
Why output is easy to count
Lines changed, tickets closed and hours logged are visible. Product correctness, reduced ambiguity and avoided failure are less visible. A metric becomes dangerous when it stands in for the outcome rather than helping the team inspect it. Ask what behaviour the measure encourages and what important work it makes invisible. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
The cost of heroics
A hero who fixes every production problem may look indispensable while making the team fragile. Knowledge stays in a private channel, decisions are made at midnight and nobody else gets the context. The individual receives praise but may not develop the ability to design a system that others can operate. Heroics can be a symptom of missing ownership. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
A tool does not own the result
A code assistant, framework or internal platform can reduce mechanical work. It does not decide whether the requirement is valid, whether the data is safe, or whether an operational failure is acceptable. Tool fluency is useful evidence when connected to a result. A demo without an evaluation or owner is merely a faster way to produce uncertainty. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
Review is part of production
Reviews slow a change and protect a system; both can be true. A useful review explains the risk, not just a preferred style. Engineers grow when they can make a decision legible, respond to challenge, and update the design. A culture that calls every question “low velocity” may be optimising for the appearance of autonomy. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
The incident nobody celebrates
During an incident, the strongest engineer may not be the one who types fastest. It may be the person who defines the blast radius, communicates clearly, restores safely and turns the learning into a change. Incident work should not be used to manufacture blame or a fake personal score. It is evidence about system and process resilience. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
The manager’s measurement problem
Managers want a fair view of contribution but often inherit dashboards that count activity. Ask the manager which outcomes matter, who controls them, and how invisible reliability or mentoring will be recognised. If the answer is only “be a 10x developer,” the expectation is not yet actionable. Specific examples are a fairer basis for growth. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
The counterargument for exceptional skill
There are engineers whose judgement, depth and pace genuinely create unusual leverage. Denying that would flatten excellence. The problem is treating a rare combination as a moral standard for everyone, ignoring support systems and rewarding unsustainable intensity. Recognise exceptional skill by the durable outcomes it enables, not by mythology around exhaustion. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
A healthier definition of leverage
Leverage is making a good decision travel: a clear design, a reliable interface, a reusable tool, a calm incident response, or a teammate who can now operate independently. It is not always scale in the number of commits. Ask which part of the organisation became more capable because of the work and how another person can verify that claim. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
When AI changes the task
When generative tools change routine drafting, the valuable work may move toward evaluation, integration, domain understanding and accountability. The ILO source describes exposure and transformation at a broad level, not a schedule for one team. Map your own tasks and learn the surrounding judgement. Do not present tool adoption as a guaranteed job shield. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
A week without theatre
For one week, record decisions, interruptions, rework, review time, incidents and handoffs rather than trying to maximise output. The exercise can show whether the constraint is technical, organisational or poorly defined. A team may discover that the fastest improvement is a clearer requirement or fewer simultaneous priorities, not a more intense developer. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
How careers get damaged
The myth can damage careers by encouraging overwork, brittle code, poor collaboration and silence about uncertainty. It also disadvantages people with care responsibilities or health limits when visibility is equated with availability. A sustainable engineer can be ambitious while declining a metric that rewards harm. Ask what the organisation actually promotes. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
The decision a team can make
A team can replace the slogan with a decision: measure a small set of outcomes, review quality and reliability, recognise enabling work, and revisit metrics when they distort behaviour. This will not remove judgement from performance conversations. It makes the judgement explainable. Keep evidence of contribution, including work that cannot be published. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.
Build systems that do not need a hero
The best engineering organisation is not one that needs a star to rescue every week. It is one where architecture, documentation, ownership, testing and escalation make good work repeatable. Individual excellence still matters, but it compounds when the system lets other people succeed. That is a more useful ambition than being indispensable. The Future of Jobs and ILO material listed for this article can support a cautious discussion of changing skill demands and task transformation, not a claim that one developer is literally ten times another. Engineering outcomes depend on system context, review quality, reliability, product decisions and team design. No defensible benchmark turns lines of code, hours online or tool count into universal productivity. Use the team’s own incident, delivery and quality evidence where available, and ask how confidential work may be described without exposing it. This is not performance-management or employment advice. The practical test is to write down what would change your mind. Ask for the relevant document, example, owner, or decision date; do not substitute a confident anecdote for evidence. A move can be attractive and still be a poor fit for your cash obligations, energy, location, or learning needs. Conversely, a less glamorous option may be the sounder experiment if it preserves runway and gives you a way to observe the promised work before making an irreversible commitment. Keep a short record of what was promised, what actually happened, and which assumption remains untested. That record is useful in a conversation, a review, or a later search, but it is not proof of a market-wide rule.