When Labor Becomes Cheap, Motivation Becomes Everything
Frederick Taylor sold a bargain: trade autonomy for a safer life. In factories, that bargain raised living standards ...
The Gray Beard and the Machine
9 min read
When Twenty-Seven Years Feels Like a Liability
21.02.2026, By Stephan Schwab
Martin had been writing software for twenty-seven years when the machine arrived. At first it felt like replacement — another cycle of the industry discarding experience for something cheaper and faster. But what he discovered, alone at his desk one evening, changed everything he believed about his own obsolescence. This is a story about fear, about identity, and about what happens when the thing you thought would destroy you becomes the thing that reminds you who you are.
The message appeared in the team chat on a Tuesday morning: “Exciting news! We’re rolling out GitHub Copilot to all engineering teams. Training sessions start Thursday.”
Martin stared at the words. Around him, the open-plan office hummed with the usual sounds — keyboards, murmured conversations, someone’s phone buzzing. He was fifty-three years old. His hair had gone gray at the temples a decade ago and had since surrendered entirely. He had written his first program in BASIC on a Commodore 64, had survived the transition from mainframes to PCs, from desktop to web, from monolith to microservices. He had outlasted technologies that younger developers had never heard of.
But this felt different.
The Training Session
Thursday came. Martin sat in the back of the conference room, arms crossed, watching the enthusiastic young developer from the platform team demonstrate how the AI could generate entire functions from a comment.
“Watch this,” she said, typing: // function to validate email addresses using RFC 5322
The AI wrote thirty lines of code in seconds. The room made appreciative noises.
Martin felt something cold settle in his chest. It wasn’t the code itself — he could have written that function, probably better, with proper edge case handling. It was the speed. The effortless, mechanical speed.
For twenty-seven years, his value had been tied to knowing things. Knowing how memory allocation worked. Knowing why that legacy module behaved strangely on Thursdays. Knowing the difference between what the documentation said and what the system actually did.
Now a machine could summon that knowledge in milliseconds.
The Quiet Weeks
He didn’t use Copilot at first. He told himself it was principle — that he wanted to understand the code he wrote, not just accept suggestions from a statistical model. But late at night, when the apartment was quiet and his wife was asleep, he admitted the truth to himself.
He was afraid.
Afraid that if he tried it, he would discover he was already obsolete. That the decades of accumulated knowledge, the patterns burned into his nervous system, the instincts that let him smell a bug before the tests even ran — that all of it was now worthless. That a junior developer with an AI could outproduce him in an afternoon.
He watched his younger colleagues embrace the tool with the casual confidence of people who had never known a world without Google. They paired with the AI the way they paired with each other — naturally, without existential crisis.
Martin felt like a man watching his own funeral.
The Integration That Wouldn’t Die
Three weeks later, he was assigned to fix an integration with a payment processor. The integration was twelve years old, written by a contractor who had left no documentation and had apparently harbored a deep suspicion of comments. The code was a labyrinth of nested conditionals, magic numbers, and variable names like temp2 and finalFinal.
The junior developers had already tried. One had spent a week adding logging statements. Another had attempted to refactor the module and introduced a subtle bug that only manifested in production, three days after deployment, on transactions above €10,000.
Martin sat down with the code on a Friday afternoon. The office emptied around him. He barely noticed.
By midnight, he had mapped the control flow in his head. Not on paper — in his head, the way he had always done it, building a mental model of the system the way a chess player sees positions. He knew where the bug lived now. He could feel it, the way a doctor feels wrongness in an X-ray before they can articulate why.
But proving it would take hours of tracing values through the maze.
He looked at the Copilot icon in his editor. He had disabled it weeks ago. His cursor hovered over the settings.
The Conversation
He enabled it. Not because he had accepted anything. Because he was tired, and the bug was urgent, and he needed help.
He typed a comment: // this function calculates the retry delay but the documentation says exponential backoff while the implementation looks linear
The AI responded with an analysis. It was wrong — it had misread the nested loop structure — but it was wrong in a useful way. It forced him to articulate why it was wrong, which clarified his own thinking.
He corrected it. Asked a follow-up question. Got another partial answer.
It was like talking to a very fast, very knowledgeable junior developer who had no intuition and perfect recall. Someone who could fetch any fact instantly but couldn’t smell the bug.
He could smell the bug. He always could. That hadn’t changed.
What changed was that now he had a partner who could run alongside him, verifying his hunches at machine speed, checking edge cases he didn’t have time to trace manually, suggesting patterns he might have forgotten from frameworks he hadn’t touched in years.
By two in the morning, he had the fix. Not because the AI had found it — it hadn’t, couldn’t — but because the AI had done the mechanical work while he did the thinking.
The Morning After
He sat in the empty office as the sky lightened. The fix was committed. The payment processor was working.
He felt strange. Lighter.
For weeks, he had believed that the AI was his replacement — a cheaper, faster version of himself that would render his experience worthless. But that wasn’t what had happened. What had happened was that the AI had amplified his experience. The patterns he had spent decades building were still valuable, perhaps more valuable than ever. The AI had no patterns. It had probabilities. It could generate code that looked right but was subtly wrong in ways that only experience could detect.
The machine needed him. Not his keystrokes — those were cheap now. His judgment. His intuition. The thing he had built over twenty-seven years that no training dataset could replicate.
The Integration That Wouldn’t Die, Continued
"The machine needed him. Not his keystrokes — those were cheap now. His judgment."
The following Monday, the team lead asked how he had fixed the integration so fast. Martin hesitated.
“I used Copilot,” he said. The words felt strange in his mouth. “Not to write the code. To think out loud. It’s like having a very fast rubber duck that can also look things up.”
The junior developer who had introduced the production bug looked at him with an expression Martin couldn’t read at first. Then he recognized it: relief. The older developer wasn’t fighting the future. He was adapting.
“Can you show me how you use it?” the junior asked.
Martin nodded. And for the first time in months, he felt like he had something to teach that mattered.
What Actually Changed
The fear didn’t disappear entirely. It never does. There will be another technology next year, and another the year after, and one of them might finally be the one that makes his skills truly obsolete. The industry is not kind to those who stand still. This pattern has repeated every decade since 1969 — the tools change, but the need for human judgment persists.
But Martin had stopped standing still. He had remembered something he had forgotten in the panic of the announcement: his value had never been typing speed. It had been the ability to look at a system and understand it, to see patterns that tools could not see, to make decisions that algorithms could not make.
The AI accelerated everything except the things that mattered most. And those things — judgment, intuition, the accumulated wisdom of twenty-seven years — those had become more valuable, not less.
The machine hadn’t made him obsolete. It had reminded him what he was for.
For the Gray Beards Reading This
"The machine hadn't made him obsolete. It had reminded him what he was for."
If you are reading this and you recognize yourself in Martin’s fear, I want to tell you something that might sound patronizing but is meant sincerely: you have something the machine does not have.
You have spent decades building a model of how software actually works — not how it’s supposed to work, but how it fails, how it surprises, how it behaves when the documentation lies. You have developed an instinct for wrongness that no statistical model can replicate. You have seen enough production incidents to know that the most dangerous code is the code that looks correct.
The AI is a powerful tool. It can help you work faster, check your assumptions, suggest patterns you might have forgotten. But it cannot do your job. It can generate code at machine speed, but it cannot evaluate that code with human judgment.
Your judgment is not obsolete. It is, if anything, more essential than ever — because now there is more code being generated, and someone has to decide if that code is trustworthy.
That someone is you.
The End (Which Is Not an Ending)
Martin still has moments of fear. He sees announcements about new AI models that can pass coding interviews, that can debug production issues, that can architect systems. Each announcement brings a small pulse of the old dread.
But he also sees the junior developers struggling with the code the AI generates, missing the subtle bugs, trusting the machine when they should be questioning it. He sees the production incidents caused by AI-generated code that no one reviewed carefully. He sees the gap between generating code and understanding code.
And he knows that gap is where he lives. It’s where he has always lived. The tools change, but the gap remains.
He is fifty-three years old, and he is learning new things. Not because he has to, but because he wants to — because the AI has removed the drudgery and left the interesting parts. The parts that made him fall in love with software in the first place, back when he was seventeen and the Commodore 64 was new. That intrinsic motivation — the curiosity and pride that no management framework can manufacture — is what the machine cannot replicate.
The gray beard is still here. And he’s not going anywhere.
Contact
Let's talk about your real situation. Want to accelerate delivery, remove technical blockers, or validate whether an idea deserves more investment? I listen to your context and give 1-2 practical recommendations. No pitch, no obligation. Confidential and direct.
Need help? Practical advice, no pitch.
Let's Work Together🎭 This Week's Episodes
Telenovelas show what we can't say in client meetings. The drama is heightened, but the patterns are real.
La Verdad
The emergency board meeting Don Hernando demanded has arrived. Mariana and the Vulcano Capital team want answers. Alejo has one final card to play....
When Players Revolt
They fixed the validation bug properly — six hours, no corners cut. But the database migration script Anton wrote Monday night to handle legacy NUL...
Technical Consultancy
Senior Developer Advocate
Embedded into your team as an active contributor, increasing effectiveness and elevating engineering clarity.
Technical Advisor
Peer-style technical assessments before far-reaching decisions; reduce architectural and product risk early.
Product & Delivery
Ship working software to real users earlier. Measure impact and adapt based on evidence rather than assumption.
Custom Software Development
High quality, maintainable software. Short-term augmentation that leaves lasting capability in your own team.
Recent Articles
- When Labor Becomes Cheap, Motivation Becomes Everything (06.04.2026)
- Authentication Methods That Work in 2026 (03.04.2026)
- Developer, Not Engineer. And Why It Matters (30.03.2026)
- The Product Manager Is Dead. Long Live the Product Developer. (27.03.2026)
- Building Products in the Age of AI (23.03.2026)