There's a generation of developers, myself included, who chose this career partly because of what it wasn't. It wasn't sales. It wasn't presenting. It wasn't navigating a room full of opinions and personalities. You sat with a problem, you talked to your computer, and at the end of the day something worked that hadn't worked before. That was enough.
That world is closing. Not because anyone took it away on purpose, but because the most fundamental part of it, the long focused conversation between a developer and a computer, has been quietly handed off to a model. The computer talks back better than we do now. So the value of what we used to bring to that conversation has shifted.
I've been thinking about this for months, mostly because I can feel it happening to me.
Chapter OneWhat the computer used to be for
Introverted programmers (and I'll just say introverts from here on, because there's no shortage of us) found something specific in this profession. It wasn't just that the work could be done alone. It was that being alone with the work was where we were best. The flow state, the slow build of a mental model, the long uninterrupted afternoons where a problem slowly resolved itself: these aren't accidents of the job. For a lot of us, they're the whole point.
I should be honest about my own experience here. The COVID years were, professionally, the best of my life. Full work-from-home was a revelation. I was more productive than I'd ever been. Code quality went up. I shipped more, fought less, and ended each day with something to show for it. I was, and I know this is the part that's hard to admit out loud, genuinely happier.
The current partial-WFH world is harder for me, and I suspect for a lot of people like me. Two or three days a week of office time isn't a small interruption to deep work; it's a different mode entirely. The flow doesn't survive the commute. The afternoon I'd planned for a tricky refactor becomes a series of fifteen-minute conversations and a stand-up I forgot was on the calendar. I leave more drained and with less to show for it. That's not anyone's fault; it's just the math of context switching, applied to a brain that was wired to go deep, not wide.
I'm not arguing that hybrid is wrong, or that offices are bad. I'm describing a specific cost that the industry largely doesn't price in: the people who built their careers on uninterrupted thinking are the ones now being asked to interrupt themselves the most.
Chapter TwoWhat the computer is for now
And then on top of that, the actual work changed.
The long conversation with the computer, the part introverts loved, got compressed. Boilerplate disappears in a prompt. Architecture sketches that used to require a whole evening alone now happen in a few minutes of chat. The model is, frankly, a better introvert than I am. It thinks in code, it never gets tired, and it doesn't need a coffee break.
So if the computer is now doing the part we were uniquely good at, what's left for us?
The push at work isn't toward coding in isolation anymore. It's toward collaboration, knowledge sharing, stakeholder management, demos, presentations, discussion. The currency of the job has shifted from what you can build to what you can communicate.
Every job description I read now has the same shape. The technical bar is still there, but it's table stakes. The differentiators are all the things introverts used to be quietly excused from: "drives alignment across teams," "presents to senior leadership," "evangelizes engineering practices," "partners closely with product and design." Nobody's writing "spends a quiet afternoon making something work."
Customer calls, executive demos, cross-team syncs, hallway influence: these aren't bonus skills anymore. They're the job. And for a lot of us, they're the parts of the job we specifically structured our careers to avoid.
Chapter ThreeThe rise of the creative dev
Here's where it gets more interesting, though, and I want to be careful not to make this purely a lament. Because the same shift that's hard for quiet introverts is genuinely good news for a different kind of developer, and may actually be good news for the profession overall.
The quiet specialist
Deep technical knowledge. Long focused sessions. Communication was a nice-to-have. The job was to build the thing correctly, and someone else would talk about it.
The creative communicator
Technical fluency plus the ability to shape the work: framing the problem, selling the approach, telling the story, bringing a humane touch to output that increasingly comes from machines.
LLMs can imitate creativity. They can't be creative. There's a difference, and the gap is going to define who thrives in this next phase of the industry. Some examples of where genuine human creativity now matters more than ever:
Clever prompting
Getting a model to produce something genuinely good requires taste, framing, and intuition about what to ask for. That's a creative skill, not a technical one.
Knowledge curation
When everyone has access to seas of information, the people who can navigate, filter, and synthesize it well are the ones who add value. That's editorial work, not lookup.
Storytelling around the work
Polished docs, decks, and reports take seconds to generate now. What used to be a moat, the ability to produce them, has become a baseline. What stands out is the human shaping behind them.
Bringing the humane touch
An AI-written email reads like an AI-written email. So does an AI-written PR description, and an AI-written design doc. The developers whose work feels distinctly theirs are going to be the ones people remember.
This is genuinely a moment for extroverted developers and for introverted developers who happen to communicate well. The technical-only career path is narrowing. The technical-plus-communicative one is widening. If you can code and present, code and sell, code and tell the story behind what you built: there has rarely been a better time to be you.
Chapter FourThe uncomfortable truth
Introverted developers have three options. None of them are comfortable.
We can step aside and let extroverted developers take the roles we used to default into. We can actually become more extroverted, which is harder than it sounds but real and possible. Or, and this is the path most of us will probably take, we can get good enough at performing extroversion to do the parts of the new job that demand it.
I want to be clear that the third option isn't fake or shameful. Most extroverted public speakers are exhausted afterward. Most performers introvert hard between shows. The skill is being able to access the mode when the job requires it, and recover when it doesn't. It's a learned behavior, not an identity.
But it does mean developing skills most of us actively avoided developing. Speaking up in meetings before we've fully formed our thought. Presenting work without two weeks of preparation. Pushing back in real-time instead of writing a thoughtful follow-up email at 11pm. Building hallway relationships that don't have a tangible deliverable. Making small talk. Networking. The whole catalog of soft skills that we, often correctly, looked at and said: I'd rather code.
Coding is becoming the part the computer does. Everything else is the part we do.
Chapter FiveWhat I'm actually doing about it
I don't have this figured out. I'm writing this partly to think out loud, and partly because I suspect a lot of other quiet developers are feeling some version of the same thing. But here's what's slowly working for me:
Treating soft skills as engineering problems. Public speaking, structured communication, executive presence: these are skills, not personality traits. They respond to practice and feedback like any other skill. The same brain that learned distributed systems can learn how to run a stakeholder meeting. It's just less fun.
Protecting deep work fiercely. The shift toward collaboration is real, but it doesn't mean abandoning what we're best at. Block calendars. Decline meetings that could be a doc. Use the time you do get alone to do the kind of thinking the model still can't do: the framing, the system design, the part where you decide what's actually worth building.
Leveraging the model where it helps with communication, not just code. Use it to rehearse a difficult conversation. To rewrite a draft you're not happy with. To prep talking points for a meeting that's making you anxious. The same tool that's pushing us out of pure coding can be a real accomplice in becoming better at the human parts.
Finding the version of "extroverted" that's authentically yours. You don't have to become the loud one in the room. You just have to find your version of being present in it. Some of the most influential people I work with are quiet; they just speak with clarity and conviction when they do speak. That's a reachable target.
To the quiet developers
The world we trained for is not the world we now work in. That's a real loss, and it's okay to grieve it a little. The era of "I just want to code in peace" was a beautiful era and it gave the industry some of its best work. But it's narrowing, and pretending otherwise won't help us.
The good news, and there is good news, is that the things we'll need next aren't beyond us. They're just outside our comfort zone. And it turns out comfort zones expand if you push on them consistently.
It can't replace humans.
So let's bring the human back into the work.
Thanks for reading ✦
Comments