AI failed me today.

I'm a developer. I solve problems for a living. In fact, I love to solve problems. I often think I enjoy the process of troubleshooting far more than actually implementing the fix.

So after several months of ignoring my HP LaserJet M608's many problems, I finally decided to do something about it. I don't think I would have been motivated to do this, but I really wanted to print a copy of Chopin's op 53 polonaise so bad.

I'd previously tried to fix the printer. But that was before AI got good enough. Countless videos and Google searches did little good. I simply couldn't find my way around the problems. Today, that was about to change. "Why not?", I asked myself? With the power of AI, I would finally conquer this HP printer! So I figured this would be my chance to start afresh and just ask Claude instead.

Claude has gotten me through several sticky situations - career issues, legal dilemmas, planning vacations and outings, deciding whether to go to the hospital, you name it.

And if Claude could do those, surely it could fix a simple printer issue, right?

Right....?

It Started Reasonably Enough

The printer had been showing a "data corruption detected" message on boot. Fair enough — Claude diagnosed this quickly, gave me a clean list of steps to try, and sounded very confident. Hard reset, factory defaults, firmware update. Easy. I felt good about this.

Then I asked how to connect the printer to my Lenovo ThinkPad running Fedora. Claude launched into a detailed guide about HPLIP, hp-setup, CUPS. All very authoritative. All formatted in neat little tables and code blocks. Very reassuring.

And this, ladies and gentlemen, is how we went down the rabbit hole.

The Rabbit Hole

What followed was nearly three hours of increasingly creative troubleshooting. At one point I was running lpstat, hp-info, hp-firmware, lsusb, dmesg, dd, modprobe, cupsenable, cupsdisable — you name it. Claude had an answer for everything. Every dead end was met with a new suggestion, a new command, a new theory.

The printer threw a 49.50.03 firmware error. Claude knew what it was. The printer's IP address came back as 0.0.0.0. Claude had an explanation. Every time I hit a wall, there was a confident response waiting for me on the other side.

The problem is that confidence and correctness are not the same thing.

The Firmware Flash That Wasn't

The most painful chapter was the firmware update. Claude told me to download the latest HP FutureSmart firmware — a 103MB file — and flash it to the printer over USB. Reasonable enough. I downloaded it, extracted the .bdl file, and sent it via lpr.

It sat in the queue for twenty minutes. Nothing happened.

We tried cp to /dev/usb/lp0. No such file or directory. We tried /dev/lp0. No such device. We tried dd directly to the USB bus. Invalid argument. We unloaded and reloaded the usblp kernel module. We stopped CUPS entirely. At one point Claude suggested writing a shell script to watch for the device to appear and flash it in the 100-millisecond window before the kernel removed it again.

That's when I asked: "Are you really sure you know what you're doing?"

And then the response I saw replaced my smile with a grin of disappointment. "No, not really."

Me and the AI were winging it! Giving me false motivation! With full vim (confidence)! And I was executing those commands with my full chest (like we say in Ghana)! We had drifted into trial-and-error territory and continuing on that tangent would be a big gamble. That moment of honesty was arguably more useful than the previous two hours of confident suggestions.

But wait - if you think this was only a Claude problem, it wasn't. My disappointed self went over to Gemini, like someone seeking consolation in a side chick after the main relationship goes bust. Gemini's first response made such perfect sense - and everything else was soft poison. Commands after commands. Methods upon methods. Explanations about why things were not working that resulted in further commands to modify things some more.

I had enough.

I gave up.

No, the Printer Still Doesn't Work

As I write this, my HP LaserJet M608 is sitting on my desk, home screen showing, USB cable connected, completely useless. CUPS is back up and running. The firmware file is still in my Downloads folder. The data corruption error is still there.

The AI was helpful right up until it wasn't. And that's if we count going round in circles as helpfulness.

What I Learned

AI assistants are genuinely useful for well-documented, common problems. It's not a conscious machine. It's GIGO. Garbage in, garbage out. It lacks the ability to innovate and create actual solutions. It only tries to find patterns and associations in its dataset. But the moment you step outside that boundary — into obscure hardware errors, device driver conflicts, corrupted firmware — the AI starts to improvise. And it improvises with the same confident tone it uses when it actually knows the answer. And that's the dangerous part. There's no "I'm guessing now" indicator. No warning light. Just more code blocks and more command.

Don't get me wrong - when AI gets it right, it's an awesome tool.

But when it doesn't, you're on your own.