I’ve been staring at my editor a lot lately.
Not because I have writer's block, but because I'm trying to figure out where I fit in this new landscape.
We are firmly in the AI generation era. Tools are writing boilerplate, refactoring code, and even debugging faster than we can. It’s easy to feel like the ground is shifting beneath our feet.
Recently, I saw a LinkedIn article making the rounds. You might have seen it too. The headline was stark:
"Will the Developer Position Disappear in 2028?"
It stopped me mid-scroll.
Not because I believe robots are taking my chair tomorrow, but because it forces a very uncomfortable question about trajectory. If 2028 is the rumored tipping point, what does that mean for the path I'm on right now?
This leads me to a question I can’t seem to shake:
If AI handles the syntax, the boilerplate, and the "obvious" solutions... what is left for us?
What should we actually be studying right now? What skills do we practice so we don't just survive, but stay relevant?
And more specifically... What do I have to be in 2028?
I don't have the answers. I'm just a developer trying to navigate the noise.
- Do we double down on fundamentals so we can spot AI hallucinations?
- Do we go wider, focusing on architecture and systems design?
- Do we go softer, investing in communication and product sense?
- Or is there a third path I haven't considered?
I’d love to hear how you are approaching this.
What are you studying right now to stay relevant? And more importantly, why?
Top comments (0)