Featured image of post Surfing the AI Tsunami: My Pragmatic Plan to Stay Current (Without Drowning)
Artificial Intelligence Developer Life

Surfing the AI Tsunami: My Pragmatic Plan to Stay Current (Without Drowning)

Honestly? Keeping up with AI is *exhausting*. Here's how I'm personally trying to filter the noise, focus on what actually helps my coding day-to-day, avoid the hype cycle burnout, and maybe even keep my weekends.

Okay, let’s have a real chat. Does anyone else feel like keeping up with AI developments is less “lifelong learning” and more like frantically treading water while a giant wave labelled “AI Everything, All The Time” looms over you? Seriously, blink and there’s a new model, a new framework, a new library, some breathless think piece declaring my entire skillset obsolete. It’s flat-out exhausting, and the FOMO is intense.

I know this cycle personally. I’ll see something shiny – maybe the latest paper on Retrieval-Augmented Generation (RAG) or a cool demo of autonomous AI Agents – and my brain instantly goes into overdrive. “Whoa, this could totally change how we handle X!” or “Imagine building Y with this!” Next thing I know, it’s 11 PM on a Tuesday, I’m elbow-deep in a half-baked quickstart, chasing cryptic errors, convinced this is the silver bullet.

The initial dopamine hit of “figuring it out” is great, but then the reality check hits hard. I try to move past “hello world,” and suddenly I’m wrestling with minimal docs, flaky examples, and tech that’s clearly still got sharp edges. My evenings and weekends evaporate into debugging sessions (sorry, family!), and often, the main takeaway isn’t a cool new feature, but the hard-won, slightly frustrating knowledge that maybe this particular shiny thing isn’t quite ready for prime time for my needs. It’s a cycle that leaves me feeling busy but not necessarily productive, just… drained.

This whole experience got me thinking: there has to be a more sustainable, less frantic way for working developers like us to engage with AI without burning out or constantly feeling like we’re falling behind.

This post is the first in a series where I want to share what I’m learning (and frankly, struggling with) as I try to navigate this AI landscape pragmatically. So, how are I trying to ride this wave without getting completely pummelled? Here are a few strategies I’m trying to stick to:

1. Focus Your Sips: You Can’t Drink the Ocean Anyway

Let’s just accept it: we cannot learn it all. The firehose of information is too much. Instead of chasing every single new announcement (a habit I’m actively trying to break!), I’m forcing myself to ask: “What actually helps me or my team build better software, fix real problems, or make my own workflow smoother right now or in the very near future?”

For me, right now, that means focusing on:

  • Getting Smarter with My AI Coding Buddy: Really mastering GitHub Copilot (or your tool of choice like ChatGPT, Claude, etc.) beyond basic autocompletion. Using it effectively for refactoring, explaining complex code snippets, generating test cases, drafting documentation – essentially, making it a true force multiplier for tasks I already do.
  • Integrating, Not Inventing: Learning how to confidently call existing, relatively mature AI APIs (like Azure OpenAI, OpenAI’s API, Anthropic’s, Google’s, etc.). Adding specific, valuable features like text summarisation, content moderation, semantic search, or maybe a simple, scoped chatbot where it clearly solves a user need. I don’t need to build the Large Language Model (LLM), just use the service effectively and responsibly.
  • Basic Prompt Crafting: Realising that getting useful output from an LLM is a skill. I’m trying to learn the fundamentals of clear instructions, providing context, and iterating on prompts to get what I actually need, rather than just getting frustrated with vague answers.

I’m deliberately not trying to become an expert on transformer architectures or the nuances of different quantization techniques right now. That’s fascinating stuff, but it’s not directly helping me ship code next week. The focus is on practical application using tools stable enough to integrate reliably.

2. Your Bedrock: Solid Engineering Still Rules

Amidst all the “AI will change everything” talk, it’s easy to get distracted. But here’s the thing: fundamental software engineering principles are more critical than ever. Clean code, good architecture, automated testing, understanding data structures, system design thinking – this isn’t going away.

In fact, these skills are essential for integrating AI effectively. An LLM can generate code, sure, but if you don’t have the skills to evaluate it, refactor it, test it, and integrate it into a well-structured system, you’re just creating tech debt faster. AI tools amplify your abilities. Using Copilot on a fragile, untested codebase won’t magically fix it; it might just help you write more fragile code quicker. Being a strong engineer who can leverage AI is way more valuable than being someone who knows AI buzzwords but lacks the foundations. Good engineering is my anchor in this storm.

3. Learn Slow and Steady: Sustainable Pacing Beats Burnout

That frantic sprint down rabbit holes I mentioned earlier? Total recipe for burnout. I’m trying to adopt a more sustainable learning pace:

  • Pick One Thing: Seriously, just one small, concrete goal at a time. Maybe this month, I’ll dedicate learning time only to understanding how to effectively use RAG with a specific vector database for a single use case. Or maybe just focus on getting better at writing prompts for code explanation. Small, focused wins feel achievable and less overwhelming.
  • Timebox Ruthlessly: This is key for me. I try to schedule a specific, limited block of time – maybe 2 hours every other Friday, or 30 minutes a few times a week – dedicated only to exploring that one chosen AI topic. When the time’s up, it’s up. This prevents it from bleeding into family time or weekend projects (mostly!).
  • Embrace “I Don’t Know Yet”: Giving myself permission not to have an immediate opinion or deep knowledge about every new AI paper or tool release has been liberating. It’s okay to say “That sounds interesting, I’ll check it out when/if it becomes relevant to my work.” I’m trying to wait for the initial hype dust to settle before diving deep into the truly cutting-edge stuff.

4. Build Your Signal Filter: Curate Your Inputs

My brain has finite bandwidth. I realised I was letting every breathless LinkedIn post or clickbait tech headline hijack my attention and dictate my learning priorities. No more.

  • Aggressively Unfollow: If a source consistently feels like hype over substance, or just makes me feel anxious, I hit unfollow. No apologies. My mental energy is too valuable.
  • Seek Out Pragmatic Voices: I’m actively looking for a small handful of bloggers, newsletters, or company tech blogs that offer balanced, practical insights, tutorials, code examples, and realistic case studies. Bonus points if they openly discuss limitations and challenges.
  • Prioritize “How-To” Over “Hot Take”: I’m trying to favour content that shows how to actually use a tool or technique in a realistic context, rather than just high-level announcements or opinion pieces about benchmark scores.

Wrapping Up: Staying Afloat, Staying Pragmatic (and Sane)

This AI wave is undeniably powerful, and yes, it is changing aspects of our work. But freaking out and trying to master everything overnight isn’t the answer (at least not for me). You don’t need to be a theoretical physicist to use electricity, and you don’t need to be an AI researcher building foundational models to leverage AI effectively in your development workflow.

My plan? Filter the relentless noise, focus on how AI can practically help me and my team solve problems today, keep sharpening those core engineering skills, learn at a sustainable pace that respects my time and energy, and be incredibly picky about my information diet.

By trying to stay pragmatic, I hope to navigate this AI tsunami, harness its power where it truly makes sense, and crucially, avoid drowning in the hype (and maybe, just maybe, reclaim some evenings!). Keep coding, keep learning (sensibly!), and let’s figure this out together.

This is just my current approach, born from my own struggles with AI overwhelm. Technology choices are always context-dependent. I’m really keen to hear how you are managing this! What strategies are working for you? What tools are genuinely useful? Drop a comment below! Look out for future posts where I’ll dive deeper into specific tools and techniques I’m experimenting with.

Resources I’m Finding Useful (for now!):

© 2020 - 2025 Michael Dugmore
Built with Hugo
Theme Stack designed by Jimmy