Originally published at https://blog.akshatuniyal.com.
A letter to every developer sitting quietly with fear in their chest — you are not a line item to be optimized away. (A perspective on the human cost behind the AI gold rush.)
I've been sitting on this feeling for a while. Watching colleagues and friends go quiet. Those still standing are under daily pressure to justify their own existence against a machine. Thought it was time to say it out loud.
There is a particular kind of silence that settles over a room when someone realizes their life's work might be expiring. Not the comfortable silence of a Sunday morning, but the hollow kind — the kind that follows a sentence like "we've already automated 80% of coding in our company," delivered casually at a conference, between sips of water, by someone whose net worth would make your annual salary look like a rounding error.
That silence is where millions of software developers live right now. And I think it's time someone wrote about it honestly — not as a tech forecast, not as a productivity bulletin, but as a human story.
The Hands That Built Everything
Let us be clear about something before we go further. Every app on your phone, every website you've scrolled, every payment you've tapped through, every hospital system that tracked your records, every satellite that beamed your video call across continents — a human being wrote that. Likely a sleep-deprived one, running on cold coffee and sheer stubbornness, debugging at 2am because the production server was on fire and real people were depending on it working.
Developers did not just "write code." They made judgment calls. They argued over architecture. They chose the right abstraction at the right moment, not because a model predicted the next token, but because they understood the business, the user, the edge case nobody had written a ticket for. They carried entire systems in their heads. They mentored juniors. They read the room in a sprint meeting and knew when to push back.
This is the community that is now being told — sometimes gently, sometimes with the bluntness of a tech billionaire's tweet — that their time is up.
"The people being 'disrupted' are not abstract workers in a productivity chart. They are real humans with EMIs, with children's school fees, with aging parents — and a career they built with years of genuine sacrifice."
The Cruelty of Casual Declarations
What makes this moment particularly painful is not just the change itself — change is inevitable, and most developers know it. What stings is the tone. When a CEO casually announces that AI writes most of their code now, what developers hear is not a business update. What they hear is: you were replaceable all along.
There's a difference between saying "the landscape is shifting, let's navigate it together" and saying "coding will be dead by year-end" as if you're announcing a quarterly earnings beat. One acknowledges humanity. The other discards it. The powerful have always had the luxury of treating disruption as exciting. They rarely have to live inside it.
And so the developer — already stretched thin, already quietly doubting whether they're good enough in a field that never stops moving — now opens LinkedIn every morning to find another think-piece about their own obsolescence. Another company bragging about headcount reduction. Another VC with a newsletter telling them that their value was always just syntax, and syntax is now free. Nobody announces this with cruelty. That's almost what makes it worse. It arrives like weather. And the weight of it just sits there, accumulating, day after day, with nowhere to put it.
A Poem for the Ones Still at Their Desks
// Still Compiling
You learned the language nobody taught in school,
sat with the errors till the errors became friends,
pulled meaning from a blinking cursor,
made a living from the logic that nobody sees.
You carried the system home inside your head,
dreamed in stack traces, woke to fix the build,
your name was in no headline, but the thing you made
was quietly keeping someone's world from falling still.
Now they hold up a mirror and say: look,
a machine does this faster. Clean. Efficient. Free.
As if the years you spent, the craft you took
apart and rebuilt — were just a recipe.
But here's what doesn't compile in their pitch:
a tool holds no pride, loses nothing, cares for none.
It cannot feel the weight of getting something right
after the tenth attempt, at 3am, alone.
You were never just a resource. You were the reason
the lights came on. Don't let them dim that — not this season.
What the Wise Already Knew
History has seen this before. Looms replaced weavers. Calculators replaced human computers. Automated switchboards replaced telephone operators. And yet — human ingenuity did not end. It relocated, evolved, and found new ground. But here's the part we conveniently skip in that optimistic retelling: the transition hurt. Real families bore the cost of "progress" while those who owned the machines counted the gains.
Gandhi once said, "First they ignore you, then they laugh at you, then they fight you, then you win." I keep thinking about that. The developer community right now is somewhere in the middle of that arc — being laughed at, being dismissed, being told to "just learn prompting" as if decades of craft were a minor inconvenience to be retrained over a weekend. But communities that have been underestimated have a long history of outlasting the people who underestimated them.
Darwin's most misunderstood lesson wasn't about strength. It was about adaptability. Developers, of all people, know this instinctively — they've been adapting since the day they wrote their first "Hello World" in a language that was obsolete five years later. The tools changed constantly. They kept up. This is not new. What's new is that this time, the people asking them to adapt are also quietly hoping they won't need to.
"A ship in harbour is safe — but that is not what ships are for." — John A. Shedd
There's a vast difference between a ship choosing to sail into new waters, and a ship being scuttled at the dock by the people who commissioned it. One is evolution. The other is abandonment. And right now, too many developers are being handed an anchor and told it's a life jacket.
"What the caterpillar calls the end of the world, the master calls a butterfly." — Richard Bach
I want to believe that. I genuinely do. But that comfort belongs to the caterpillar who is given the space to transform — not to the one being told the cocoon is a performance issue.
What We Owe Each Other
If you are a developer reading this: your anxiety is legitimate. Your feelings are not weakness — they are the entirely rational response of a thoughtful person confronting genuine uncertainty. You are allowed to feel threatened without being told to "just upskill" as if that costs nothing — not in time, not in money, not in the emotional labour of rebuilding your identity from scratch.
If you are a leader, an executive, an investor reading this: the developers in your team are not legacy infrastructure. They are people who chose this craft because they loved it. The least you owe them is honesty, lead time, and the basic human decency of not announcing their redundancy via a tweet at a conference they weren't invited to.
And if you are someone who uses technology — which is everyone, everywhere, always — remember occasionally that behind every seamless interface is a person who lost weekends to make it feel that way. That person deserves more than being phased out in a keynote slide titled "Efficiency Gains."
The Code Will Change. The Craft Won't.
Tools have always changed what developers do — they have never changed why developers matter. The judgment, the empathy for the end-user, the ethical instinct about what a system shouldn't do, the ability to ask the right question before writing a single line — these are irreducibly human. AI can autocomplete. It cannot yet care.
The community that built the internet, that shipped open-source software used by billions for free, that debugged other people's messes out of sheer professional solidarity — that community has more resilience than any algorithm. But resilience should not be asked of people who are given no runway, no support, and no acknowledgement of what they've already given.
To every developer quietly carrying this weight right now —
I see you. A lot of us do, even if we haven't said it.
You are not obsolete. You are not a cost to be optimised.
You are someone who chose a hard craft and gave it real years.
That doesn't expire. Not in a keynote. Not in a tweet. Not ever.
written with empathy · for the builders who kept the lights on · and still do
About the Author
Akshat Uniyal writes about Artificial Intelligence, engineering systems, and practical technology thinking.
Explore more articles at https://blog.akshatuniyal.com.
Top comments (0)