The Software Engineers Survival Guide in the Age of AI

Ah, 2025—what a wild time to be a software engineer. Some days I’m deep in code reviews, juggling sprint planning, untangling serverless configuration issues, and figuring out why a feature flag isn’t behaving as expected. Between shifting priorities and the relentless pace of change, I often pause and think: Is this really the job I signed up for?

Let’s talk about it—the AI revolution. It’s exhilarating, bewildering, and, if I’m honest, sometimes downright terrifying.

Why Am I Feeling This Way?

Some days I’ve got it all sorted: integrating the latest API, dabbling with machine learning models, even sneaking the odd LLM-powered tool into my workflow. Other days, I wonder, “In five years, will ChatGPT-42 be coding better than me while also planning my family holiday and figuring out the best Magic draft strategy?”

Sound familiar?

The AI Tsunami—A Blessing and a Curse

• Unprecedented Automation: Generative AI can already whip up code, optimize queries, even design systems. The tasks that used to fill my workday? Now a bot’s snack. This frees up time, but also raises that existential “Will they need ME?” question.
• Moving Goalposts: The old idea that learning the latest framework would keep you relevant is fading. Now it’s about learning to wield the tools that wield the tools. Code is becoming less the end product, more the “glue” between services and models.
• Shifting Value: The myth that “hardcore coders” will always be indispensable? Let’s just say I’m teaching myself more about prompt engineering and ethical AI than optimizing algorithms these days.

The Emotional Engineering Rollercoaster

I’ll be candid: I sometimes feel insecure about the future of my job. There are up days—I’m picking up a new skill, mentoring someone, or solving a hairy bug the bots can’t crack. But there are also days when the pace of change feels overwhelming, and I scroll forums seeing folks claim “AI will make you obsolete by Tuesday.”

• The Good News: Most evidence suggests someone needs to build, test, and understand these intelligent systems. Human creativity, judgment, and that all-important “human in the loop” work are not disappearing.
• The Twist: That “someone” will need skills that are always evolving. Think of it like Magic: The Gathering—formats change, metagames shift, and you have to adapt your deck or get left behind.

Future-Proofing Yourself (Or Trying To)

Here’s a few ways I’m trying to surf the AI wave instead of getting wiped out:

• Double Down on the Human Stuff: Communication, collaboration, domain expertise, and empathy are more important than ever. Bots don’t know your customer like you do.
• Learn How AI Works: You don’t need to invent the next neural net, but understanding how they work, how to steer them, and how to debug their quirks? That’s gold.
• Stay Playful: I tinker. I run little AI experiments. I automate the boring bits. Sometimes the best way to tackle fear is with curiosity (or if that fails, a well-timed walk in the garden with my grandkids).

From Kiwi to Queenslander: My Evolving Perspective

Maybe being from New Zealand originally—with our number-8-wire spirit—helps me keep adapting. Now I’m in Brisbane, learning to swap chilly Whangarei nights for sub-tropical evenings and Maroons vs. Blues debates. When the game changes, we tinker, adapt, and figure it out as we go. I’ve seen enough meta-shifts in both tech and Magic to know: Change is a constant, but so are clever, resilient people.

So, whether today’s an “up” or a “down” on your emotional engineering rollercoaster, know this: You are not alone. Most of us are making it up as we go along, hoping there’s still a spot at the table for us in the next draft.

Let me know how you’re dealing with the shifts—what excites or worries you these days as a software engineer? Or, come play a game of Magic. The bots aren’t that good… yet.

Cheers from sunny (and occasionally stormy) Brisbane!