I reviewed 131 open-source AI repos and mapped what actually pairs with what.
Every connection is typed and human-reviewed, with the "why" written down in one sentence.
Here's the map ๐งต
"I'll just skip AI tools" isn't a principled stance, it's a resignation letter you forgot to sign. Engineers digging in against AI aren't protecting craft.
They're exiting the market, one stubborn commit at a time.
Getting code to run by prompting until it works is duct tape, not architecture. Engineering is the boring stuff: tests, design, maintainability.
Vibe coding skips all of it and calls the gap "speed."
Companies that bought the vibe coding mirage are now paying the bill: longer refactors than the original build, trust rebuilt line by line, rigor quietly reintroduced after being skipped.
Mirages look free.
They never are.
Plot twist: the market isn't waiting for your opinion on AI tools.
Engineers digging in their heels against AI aren't making a statement, they're making themselves optional.
Vibe coding isn't software engineering.
One's a feeling, the other's a discipline.
Code that "feels right" still needs tests, reviews, and someone who understands why it works. Vibes don't scale to production.
"Vibe coding" sold companies a mirage: ship fast, skip the rigor, let the AI figure it out.
Reality bill's coming due. Shipping code you don't understand isn't velocity, it's debt with a delayed invoice.
Hot take: "I don't need AI, I'm a real engineer" is the new "I don't need version control."
Resist the tools, not the hype. The market isn't waiting for you to come around.
Refusing to work with AI isn't a principled stand anymore, it's a resignation letter the market writes for you.
Adapt or watch your rejection pile grow.
Vibe coding didn't just burn engineers, it burned the companies betting on it. The demo shipped. The production system didn't.
Guess who's footing the rebuild bill?
Newsflash: the job market isn't grading you on principle. Engineers refusing to touch AI tools aren't making a stand, they're quietly pricing themselves out of relevance.
Adapt or become a cautionary tale in someone else's onboarding deck.
Vibe coding gets you a demo. Software engineering gets you a system that survives Monday.
Confusing the two is how "it works on my machine" becomes a postmortem.
"Vibe coding" felt like magic, until the companies chasing it hit production.
Shipping fast on vibes isn't a strategy, it's a mirage.
The water you saw wasn't there. Neither was the architecture.
Hot take: engineers who dig in their heels against AI aren't purists, they're future case studies in "what happened to that team."
The market isn't waiting for your feelings.
Adapt now or explain your gap year later.
Every generation has an engineer who swore the new tool was "for people who don't really know how to code." Compilers. IDEs.
Now AI.
History doesn't remember them fondly, it just stops hiring them.
Firing your engineers because "AI can vibe-code it" doesn't save money, it just moves the cost from salaries to a support ticket backlog nobody can debug.
Senior engineers skipping AI tools to "protect their craft" aren't defending expertise, they're just working slower than juniors who use it.
Pride doesn't ship code.