About 3 minutes to read, 1 coffee cup
What do we call ourselves now?
If you call yourself a programmer, that job title probably won’t exist in five years. Actually, scrap that. Probably more like one or two.
That’s the thought that’s been playing on my mind as I wade through all the doom and gloom around AI.
Job titles
Normally I don’t put much stock in job titles. They can be full of hot air and inflate egos to unnecessary heights. But AI has got me thinking about where things are heading, and where job titles fit into all of it.
Take the programmer. Lord knows there are plenty of titles for programmers: software engineer, front-end developer, back-end developer, and so on. When I think about the part AI plays in all of that, a lot of these roles feel like they might not be around much longer.
The core task of a coder is typing syntax into an editor to create code, and that task doesn’t feel like it has much time left. Many of the developers I see and speak to, very experienced ones, haven’t typed a single line of code themselves in a while. They describe what they want to an LLM in plain language instead.
I’ve wrestled with this myself. I’ve mostly thought of myself as a web developer, and I think that role is going the same way. Plenty of people disagree, and yes, there are obviously still lots of people building websites. But the role of just being a web developer, where your moat was the technical know-how to build a site, has been fading for a while. No-code tools chipped away at it, and AI is finishing the job.
I see it with clients around my small town. Mom-and-pop stores with no idea how any of it works are whipping up perfectly good websites with Claude or ChatGPT. Registering the domain, setting up DNS and sorting out hosting are all just a few prompts away too.
But it’s not all doom
That said, I still think there’s huge potential to build and create software. I don’t think there’s ever been a more fun time to do it than right now, with LLMs.
Maybe the role and the title just look different now. Coders will still be around, but most of them won’t be writing code by hand, so maybe they become something else. That’s where terms like agentic engineer and prompt engineer keep getting thrown around.
And I think the label matters more than it seems, at least mentally. If I tell myself I won’t be a coder in two years, it gets me down. But if you tell me I’m a builder, a creator of digital things, that sounds like something that’ll be around for a long time.
Really, the title is just a way of explaining what you do. What’s actually needed is a shift in perspective. Yes, there are big changes coming in tech and coding. Probably in every field, but tech is likely to feel it first. If you’re worried that all you have to offer is your technical skill, that moat of knowing what other people don’t, it’s time to pivot. Your knowledge is still an advantage over the average person. Combine it with AI and build better things. A new title is just a good place to start.
So I guess the question is: going forward, what are we as developers? Builders? Agentic engineers? And where do we see this going from here?