A Long Overdue Blog Update

It’s been almost three years since I wrote any blog entries, but now I am back, and I plan to be adding some new content over the coming months. Hopefully, 2027 will be a productive year!

So where have I been? I am happy to share that in October 2024, I joined the then-named Pure Storage as a Field Solution Architect, focusing on structured data, databases, Oracle and Open Source. Since then, the company has grown larger and stronger, and was renamed Everpure this year. Everpure is a dynamic and innovative company, and one of the many great things about working at Everpure is that I once again have access to real hardware in an amazing lab!

Prior to Everpure, I had worked at EMC since 2012, and I have fond memories of my time at EMC and then Dell Technologies, which acquired EMC in 2016. I still have many friends there and I wish them well.

Like everyone else in technology, I have watched over the last three years as AI has exploded from a remarkable niche into a technology that touches everything we do.

And I suppose one of the reasons I have been less motivated to blog over the last 24 months has been the growth of AI, which continues to revolutionize our work and our lives. I found myself asking, “Why bother blogging in the age of AI?”

I expect, like many of you, I have begun to rely on my search engine’s own AI to scan a multitude of sources before it presents me with an answer to my technical query. This approach is dramatically faster than having to click through a series of random links, often accompanied by nuisance pop-up ads or, in some cases, even malware trying to perform a browser hijack. This feature alone has boosted productivity.

However, typically the AI bot does not tell us from whence it found the relevant information. Even when I ask the AI bot to list the sources, I sometimes find the links do not support the conclusion the AI chatbot yielded, which can be very frustrating.

Make no mistake. This blog is not going to morph into some anti-AI screed. AI today is a disruptive but also powerful tool. And it is not going away. And as someone who has spent way too many evenings grinding through debugging the perfect regex pattern to perform some required function, there are many parts of AI I adore.

Neither am I trivializing the impact of AI. Scores of jobs have been and will continue to be lost to AI automation, and the impact on society may well be as profound as the agricultural or industrial revolutions of the past, when livelihoods were suddenly rendered obsolete en masse. Despite the economic devastation wrought by those events upon the men and women who had relied on the old structures, few of us would advocate for a return to a pre-industrial or subsistence farming way of life.

I will also note that those of us who work in the private technology sector have never enjoyed the types of robust job protection seen by government employees and their public sector unions, or the media-entertainment industry, which has moved to enact contractural protections for its creative assets and resources. I do not foresee a WGA-type organization moving to protect technology writers or bloggers from having their content consumed wholesale by AI.

So why bother to blog at all if all our energy and creativity is simply consumed and anonymized by a soulless AI bot?

Plagiarism, of course, isn’t a problem confined to AI LLMs. And it can sometimes be hard to properly identify. After all, there are only so many ways you can perform certain functions in an Oracle database, only so many permutations of a sub-function. I have always tried to link to, acknowledge and provide credit where I have built upon or extended someone else’s work. That, I believe, is what any ethical technologist should strive for.

And AI is only as good as the source material it feeds off. Recently I spent two days with Claude, Gemini and ChatGPT all feeding me useless code because the underlying documentation was scarce and inaccurate. More than once I have had a confident AI bot deliver me reams of code that fails a basic syntax check.

When I started this blog back in 2012, I made the tag-line “When you just want this Oracle *** to work!” It was a somewhat irreverent acknowledgement that many of the technical resources of that time spent a significant amount of their content not actually providing actionable information. More often than I care to admit, I found myself several hours into a Linux or Oracle patching exercise, trying to resolve some thorny tangential dependency issue, simply because I wanted to explore a new or interesting feature in the database.

I call it the “Signal to Noise Ratio Problem”. Lots of information, some of it extremely useful but much of it of little practical use. Sorting the wheat from the chaff became something of an art.

Although, as stated, AI has often helped me arrive at the right solution quickly, the amount of AI-generated content is compounding the signal-to-noise ratio problem. We’ve all seen database blogs that are essentially just old Metalink articles regurgitated. Now we have AI-generated summaries of regenerated Metalink articles to contend with as well.

But regardless of the LLMs and the plagiarists, this blog was always sort of my lab notebook. It was as much for my benefit as anyone else’s. If other technologists found value in it, so much the better!

So I will continue as I began. Not only hoping to remind my future self how some feature or process worked, but striving to deliver useful insights, solutions and tips to fellow technologists without allowing this blog to become an extension of my employer’s marketing department. While I may frequently explore how to leverage Everpure’s storage technology to deliver the best outcomes for database engineers, I will try to avoid sales hype wherever possible.

If you are a fellow human reading this directly; Welcome! I am happy you are here.

And if it is just me, Claude, ChatGPT and Gemini, I will add them to my imaginary friends, and we’ll have some fun too.

Leave a Reply