The Merge Conflict

For experienced developers navigating the AI identity crisis.

Abstract

A generation of software engineers, those with 5 to 25+ years of professional experience, now face an unprecedented identity crisis. The standard narrative these days frames developers as becoming obsolete. We reject this framing.

Deep engineering experience, systems thinking, and architectural intuition represent competencies that resist automation. What experienced developers feel is not a resistance to progress, but a rational response to an industry that stopped valuing the thing that makes software work.

The Thesis

Your value has never been in the lines of code you produce. It's in the lines of code you prevent: the architectures you steer away from, the edge cases you anticipate before they get pushed upstream, and the domain knowledge that you carry which no model has ever been trained on.

The Merge Conflict is built on a single premise: you are not alone in feeling this, you are not wrong, and you are still extremely valuable.

Who This Is For

Developers with 5-25+ years who feel the ground shifting
Senior engineers tired of the "vibe coding is the future" discourse
Anyone who's debugged production at 2am and wonder if they still matter
Builders who want to merge their experience with AI; not choose one or the other

Who This Is Not For

Non-developers (this is by devs, for devs)
The "coding is dead" crowd
Anyone looking for AI tool tutorials
People who think real developers write their own code, period

Installation

git merge experience ai-revolution --strategy=ours

Just kidding. There's no clean merge strategy for this. That's the point.

License

MIT, because everything good in the coding world starts with open source.

Maintained by Mark Shust · 25 years of code and counting.

Problems Output Terminal Debug Console

⚠ Identity crisis unresolved — expected clarity, received existential_dread your-career.js:1

⚠ Variable yearsOfCraft is assigned but never valued by hiring managers your-career.js:7

✕ mass_layoff has no catch block industry.js:2023

⚠ senior is deprecated in favor of prompt_engineer — are you sure about that? titles.d.ts:1

ℹ 0 problems are actually your fault. The merge conflict is systemic.

[2025-02-02 18:17:00] Andrej Karpathy tweets "vibe coding". The lexicon shifts overnight.

[2025-02-24 00:00:00] Claude Code released. Senior devs felt a disturbance in the force.

[2025-03-15 09:14:22] First junior dev ships production app without understanding HTTP.

[2025-09-12 11:45:33] AI generates "perfect" code. You find 3 race conditions in review.

[2025-11-20 16:20:00] The conversation is morphing into "do we even need architects anymore?"

[2026-01-09 08:00:00] Experienced dev realizes: AI isn't the threat. Being undervalued is.

[2026-03-05 23:59:59] The Merge Conflict goes live. You're here. That's the first step.

› career.getStatus()

→ "it's complicated"

› ai.canReplace(seniorDev)

→ TypeError: Cannot read property 'judgment' of undefined

› experience.valueOf()

→ Infinity

› imposterSyndrome.isValid()

→ true (but everyone has it, even the AI)

› merge(experience, ai)

→ { result: "superpower", conflicts: 0, regrets: 0 }

› console.log("You belong here.")

You belong here.

~/your-career $ git merge ai-revolution
Auto-merging your-career.js
CONFLICT (content): Merge conflict in your-career.js
Automatic merge failed; fix conflicts and then commit the result.

~/your-career $

~/your-career $ git commit -m "resolve conflict: keep both"
[main 7a3f2c1] resolve conflict: keep both
✓ You're in. Check your inbox.
1 file changed, all years of experience preserved

⚠ 1 conflict remaining main*

JavaScript UTF-8 LF