Conversations about AI and careers often start from anxiety. I hear developers wondering whether the tools they use today might reduce the value of their role tomorrow.
I understand where that concern comes from. The shift is fast, uneven, and hard to interpret while it's happening.
When uncertainty lasts, fear can become the default lens. For me, the useful question isn't whether change is happening. It's how to respond to it without defaulting to fear or denial.
The market is shifting
The direction of the market is clear. AI is already changing how work gets done, even if adoption is uneven. Some companies are still hesitant because of data leakage or security concerns, while others are already using it heavily. The market is adapting quickly.
That shift changes how developers are perceived. The period where developers were seen as an extremely scarce resource, and companies reorganized everything around keeping them happy, isn't necessarily gone, but it has toned down a lot.
In practice, I started noticing expectation shifts in everyday work before I saw them in org charts. Tasks that used to get a day of exploration are now expected in hours because teams assume AI can accelerate the first draft. That changes how planning conversations happen, even when headcount doesn't change.
That may be true in some cases. At the same time, it's hard to imagine this change fully reversing. AI is reshaping how work gets done across many domains, not just software development. Even if some companies course-correct later, the baseline has already moved. That's a big part of why job security feels less static than it did a few years ago.
From fear to agency
When job security feels less predictable, it's natural to look for certainty. One common reaction is avoidance: if you don't engage with AI, maybe the pressure will pass.
I sometimes compare it to aging: you can ignore your birthdate, but time still moves. The point isn't to be dramatic. It's to recognize that ignoring a change doesn't pause it. In the same way, avoiding AI doesn't reduce its impact on the market or on our roles. It mostly reduces our time to adapt.
Once that became clear to me, I stopped spending energy on whether the shift was real and started focusing on adaptation. What helped most was simple: learn, listen, read, and try things in small loops.
Learning has practical limits
That response sounds simple, but it runs into practical limits very quickly. Not everyone has the chance to learn at work. In my case, I'm lucky that my company pushes the use of AI. I get time to learn, and I'm allowed to experiment, including on personal projects. That's not the case everywhere.
I used to think learning happened in stable cycles: a stretch of delivery, then a stretch of catching up. Over time, I started seeing that the cycle itself has changed. The gap between what teams do now and what the market expects can open much faster than it used to.
Even when employers support learning, there are limits. Companies invest time in what serves them. If a new technology isn't useful in your current environment, it's very hard to get time allocated for it.
That dynamic isn't new. AI didn't create it, but it has accelerated the pace of change developers are expected to keep up with. What used to be a slow gap can now become visible much faster.
That constraint shapes what people end up learning. If you only learn what your employer uses, over time you become very specialized in that stack. That can be fine for a while, but it's also a risk when the market changes faster than your local environment.
Finding realistic space to learn
I don't have a perfect recipe for learning. It depends a lot on where you are in your life. Sometimes it's easy to invest time, sometimes it's not. The goal isn't to do everything. It's to look at your day or your week and find where learning can realistically fit.
Listening to a podcast while doing dishes. Watching a short video or listening to an audiobook while commuting. Reading a bit before going to sleep. Starting the day a little earlier to experiment with something.
None of that is mandatory. You're allowed to have a life outside of work. I still had to treat my own learning as my responsibility, even with strong support at work. My employer invests in me, but not in every direction I may need over time.
Things won't simply go back
That responsibility doesn't disappear if the technology slows down. Even if AI were to stop improving tomorrow, there's already a lot you can do with it today, and people are finding ways to use it that meaningfully improve how they work.
I can't say whether you or I will lose our jobs because of AI at some point. What I do feel confident about is that things won't go back to how they were.
You might still find places that don't embrace AI, just like some companies still need COBOL programmers today. But those niches tend to shrink over time. For me, the practical question is how much I can adapt in a given season of life, then making sure I actually protect that time each week.
- Patrick