• Post author:
  • Post category:AI
  • Reading time:6 mins read

Over the past year or two, I’ve had more conversations than I can count about AI and what it means for the future of work. Somewhere along the way, the conversation almost always shifts to content creation.

“Why would anyone still write blogs?”

It’s a reasonable question.

AI can generate articles in seconds. It can summarize research, draft outlines, suggest headlines, and rewrite awkward paragraphs. I’ve used it to do all of those things myself. The featured images on my recent posts? AI-generated. Some of the outlines? AI helped me organize them. There have even been times when I’ve thrown a half-formed idea, consisting mainly of fragmented bullet points and random screenshots, into ChatGPT just to see if it could help me figure out what I was actually trying to say.

One of the more unexpected benefits has been using AI as a sort of conversational memory aid. After years of working on projects, troubleshooting obscure issues, organizing events, and writing about whatever happened to consume my attention that week, it’s easy to forget just how much you’ve actually done. Sometimes, all it takes is a prompt asking, “What have I been working on lately?” for connections to emerge between experiences that had been sitting in separate mental boxes. The stories, lessons, and opinions are still mine, but AI has become surprisingly good at helping me remember the raw material I already had.

A few years ago, I might have been uncomfortable admitting that. Now, I don’t see the point in pretending otherwise.

AI has become another tool in my toolbox, no different than spellcheck, Grammarly, Google, or Stack Overflow before it. The difference is that it’s a much more capable tool. It helps me think through ideas, identify blind spots, and get past the hardest part of writing: turning a blank page into a first draft.

But I’ve also realized that AI hasn’t changed the reason I write in the first place.

When I started blogging, I thought I was documenting solutions for other people. To some extent, that’s still true. If someone stumbles across a post that saves them an hour of troubleshooting or helps them avoid a mistake I made, that’s incredibly rewarding.

What I didn’t expect was how often I’d end up helping myself.

I’ve lost track of the number of times I’ve searched my own blog trying to remember how I solved a problem. What Docker command fixed that issue? Why did I choose one approach over another? What was the exact configuration change that finally got something working? It turns out that maintaining a blog is a surprisingly effective way to create a searchable archive of your own experiences.

The older I get, the more I appreciate having that archive. At the same time, I think the value of personal blogs has changed.

There was a time when publishing information was enough. If you knew how to configure a piece of software or solve a technical problem, simply sharing the steps had value because that information wasn’t always easy to find.

Today, information is everywhere.

AI can explain how to configure Home Assistant. It can tell you how PostgreSQL indexes work. It can summarize documentation that would have taken hours to read through manually. In many cases, it’s remarkably good at it.

What it can’t do is tell your story.

It can’t explain why I decided to migrate away from Ollama after spending weeks chasing latency issues in my local voice assistant setup. It can’t capture the frustration of troubleshooting a certificate renewal problem that turned out to be caused by an unexpected interaction between multiple systems. It can’t describe the trade-offs involved in designing a product strategy after hearing the same concerns from customers over and over again.

Most importantly, it can’t honestly tell you what it got wrong along the way.

Those experiences are where the interesting parts live.

The tutorials and technical explanations are useful, but the context behind the decisions often matters just as much. Why did you choose this approach instead of another? What assumptions did you make? What would you do differently if you had to start over?

Those aren’t questions with universally correct answers. They’re reflections shaped by experience.

I’ve also noticed that the posts people respond to most aren’t necessarily the most polished. They’re the ones where I share what actually happened. The unexpected challenges. The trade-offs that weren’t obvious at the beginning. The moments where my original plan fell apart, and I had to rethink it.

There’s something reassuring about hearing that other people don’t always get it right the first time.

Maybe that’s part of the reason blogs still matter.

Long before AI entered the picture, I learned a tremendous amount from strangers on the internet who took the time to document what they had learned. Someone wrote the forum post that solved an obscure issue I was having. Someone published a guide that made a difficult concept easier to understand. Someone shared a hard-earned lesson that kept me from making the same mistake myself.

Most of those people had no idea who would eventually read their work. They shared it anyway.

I think blogging is, at its best, an extension of that idea.

It’s contributing back to the collective knowledge that all of us benefit from. It’s leaving behind breadcrumbs for the people who come after us, even if we never meet them. Sometimes those breadcrumbs help a stranger halfway around the world. Sometimes they help a future version of ourselves who has forgotten the details of a problem we once knew how to solve.

AI has changed how I write, and I expect it will continue to do so. It has made me more productive and helped me communicate ideas more clearly. In many ways, it’s become one of the most useful tools I use on a daily basis.

What hasn’t changed is why I still sit down and hit “Publish.”

I still believe there’s value in documenting what we’ve learned, sharing our experiences honestly, and adding our own perspective to the conversations happening around us. The internet doesn’t need another thousand generic articles repeating the same advice. It does, however, benefit from people who are willing to share what they’ve actually experienced: the successes, the failures, the lessons learned, and the things they wish they had known sooner.

As long as people continue solving problems, changing their minds, and learning through experience, I think there will always be a place for personal blogs.

The tools we use to tell those stories may evolve. The stories themselves still matter.

Jonah May

Hey there! I’m Jonah May, a Product Architect and Product Engineering Manager at CyberFortress, a Platinum VCSP dedicated to keeping data safe and recoverable. When I’m not working on backup strategies and automation, you’ll find me deeply involved in the Veeam community—as a Veeam Vanguard, Veeam Certified Architect, VCSP Technical Ambassador, and co-founder of the Veeam Community Hackathon. I also help lead the Texas and Automation Desk Veeam User Groups, where we nerd out over all things backup, automation, and infrastructure.Beyond tech, I’m a Scout leader, having earned my Eagle Scout back in the day. I love sharing knowledge, solving problems, and making technology work smarter, not harder. If you’re into Veeam, automation, or home labs, let’s connect!