Finding Joy in the Journey: Life as a DBA

You ever feel like there’s so much you want to learn… and somehow even more that you need to learn? Yeah, same. With limited time and energy, deciding what to focus on can get a bit overwhelming, especially when you’re in a constantly evolving field like tech.

After a year in my current role, I’ve been reflecting a lot on how I make those choices. This blog post is partly a way to unpack that process and partly a reminder to myself to stay balanced and intentional.

Where I Start

There’s the stuff that’s exciting, new and fun… and then there’s the work that moves the needle, career-wise. But here’s the thing, I’ve found that when I can find the intersection of those two, that’s where the real magic happens

Overload vs. Overwhelm

I came across a simple idea recently that lingered with me:

• Too much to do

• Too much to hold

One is about the sheer volume of tasks. The other is about the mental weight we carry.

Tech can hit you with both at once. You start chasing every hot new tool, trend or framework. Next thing you know, you’re spinning your wheels and making no real progress.

So I’ve learned to focus. I keep a short list (just 4 key areas) of what I’m intentionally learning. That doesn’t mean I don’t explore smaller topics or chase down rabbit holes occasionally (those often turn into blog posts), but the main list stays tight.

Here’s my current focus:

• dbatools – diving into advanced automation, CI/CD, and provisioning

• Database DevOps – building deploy pipelines with GitHub, PowerShell, Jenkins

• Grafana – exploring it as an alternative to enterprise monitoring tools

• GCP and AWS – basics for managing SQL workloads in the cloud

How I Decide What to Learn

If you’re not sure where to begin, here are a few questions I ask myself:

1. What’s trending? Cloud platforms, automation, AI integration — following industry trends helps me stay relevant and future-proof.

2. What excites me? I’m way more motivated to learn something when it aligns with my interests — like performance tuning, scripting, or automation.

3. What’s my current skill gap? A little honest self-inventory helps. I might be strong in T-SQL, but maybe my infra-as-code knowledge needs work.

4. Who can I learn from? I reach out to peers, read blogs, hit forums, and watch MVP videos. Tech is too big to learn in isolation.

5. Am I staying flexible? Rigid goals are fine in theory, but adaptability is key. I tweak my list as I go — and I don’t beat myself up for it.

6. What’s my timeline? I break things into smaller, time-bound goals. Mastering Jenkins might be a long haul — but building one pipeline by next month? Totally doable.

7. Am I making time to learn? Blocking out learning time during the week helps me avoid that “I’ll get to it later” trap.

From Pressure to Possibility

The tech world can often feel intense, job uncertainty, tighter resources, and constant competition. But instead of seeing it through a lens of scarcity, I choose to embrace an abundance mindset. There’s plenty of opportunity, knowledge, and room to grow for everyone.

That said, trying to master everything at once is a fast track to burnout. Tech moves fast, but you don’t have to chase it all at once. Focused learning beats scattered efforts.

And if you ever feel limited (by time, tools, or expectations) remember that constraints can be a catalyst. Some of the best innovations come from working within tight boundaries. At its core, tech isn’t just about code and logic, it’s also about creativity and imagination.

Why I Blog

This post is part reflection, part self-reminder, and part personal archive. Blogging has been huge for me in reinforcing what I’ve learned. Here’s why I think everyone should try it:

• Personal reference – I’ve saved myself so many headaches by searching my own posts.

• Knowledge sharing – We all have “aha!” moments. Why not document and share them?

• Authentic expression – Your blog is your voice. It doesn’t have to be perfect or profound.

• Career boost – Your blog becomes your portfolio. It says: “I care enough to teach.”

• Deeper learning – Explaining things forces clarity.

• Connection – Your readers might become collaborators, mentors, or friends.

• Fulfillment – It’s satisfying to create something that helps someone else.

  
  

If you’re worried no one will read it — who cares? Write for yourself. That’s where it all starts.

Lessons I've Learned in the Past Year

This past year as a Senior DBA (with a good dose of DevOps) has stretched me in all the right ways. Here’s what I’ve added to my toolkit:

• dbatools automation via PowerShell

• CI/CD using GitHub, Jenkins, and Azure DevOps

• Distributed Always On Availability Group to scale out reads overcoming replication limitations

• Table Partitioning & Compression to boost performance and slash storage along with automated partition maintenance

• Flyway

• Devart dbForge DevOps

• Grafana

• Zabbix

• Kusto & Azure Data Studio

• Confluence for documenting insights for blog reference

• Google Big Query (Data Warehouse) via CData & Simba ODBC

• Ola Hallengren script automation

  
  

It’s been a winding road. But I’ve learned to lean into the curves.

Final Thought

Learning in tech isn’t about stuffing your brain with everything. It’s about finding that sweet spot where curiosity meets utility and creating a little space for joy in the process.

So whether you're just starting out or a few years in, I hope this post helps you navigate your own learning journey. And if nothing else, I hope it reminds you that you’ve got more control (and more joy) than you think.