Using Claude for Frivolous (or not?) Purposes

I used Claude Cowork for something silly, but I was curious to see if it could handle it. Dairy Queen has a customer feedback website, and a unique code is on each receipt. When you submit a survey, you get a code for a free Dilly Bar. 😋

I took a photo of the receipt, and gave Claude instructions to complete the online form based on my overall experience. Much to my surprise, it did this flawlessly: no interruptions, headless (no browser takeover), and I got the code I needed. Impressive! 🤯

While this was a somewhat silly example of what AI can do for us, there are many scenarios where completing online forms is a tedious exercise and an AI helper can spare us the hassle. Would I trust it yet to do something critical? No. But a feedback form? Perfect use case.

Vibe Coding: The Revolution is Here

The vibe coding revolution is here. I’ve been stuck trying to write up my own thoughts on what it means for someone like me to be able to create software in a few minutes, but David Pierce did a great job on the topic in this article at The Verge.

The article crystallizes much of what’s been going around in my head for the past five months since I vibe-coded my first thing (a browser extension for work) in early January. The irony is not lost on me that those same type of tools, and the cost of them, are the reason AWS told me and 16K others we didn’t have jobs anymore. 🫠

Since then, I’ve vibe-coded five more software projects that solve specific challenges for me (yes, I need to write about them!). No developer would ever make these because it just isn’t economically viable for them to do so; the addressable market is just too small.

This is indeed a software revolution; that’s not hyperbole.

I’ve been around long enough to see similar shifts, though never quite of this magnitude. In the early ’90s, new desktop publishing software allowed anyone to create sophisticated page layouts and print them on laser printers. Previously, this was the purview of people who knew how to use QuarkXPress and ran print presses. Suddenly, regular users could create things that were “good enough”, no pros needed. Vibe coding is this, but 1000x.

Now that we live in a world run by software, the impact of regular users being able to create their own apps is massive, and I’m able to do things I never could before. I used to say that after I retired, I’d learn how to be a developer to create the tools I always had in my head.

Now I don’t have to wait. 🚀

Man versus Machine: IBM’s Watson Supercomputer on Jeopardy

Image from Wired.com

Today I watched something that completely and totally captured my attention: IBM’s supercomputer, dubbed Watson, took on two Jeopardy champions (Ken Jennings and Brad Rutter). Watson is packing some serious hardware:

“The 360 Power7 chips that make up Watson’s brain represent IBM’s best and brightest processor technology. Each Power7 is capable of over 500 GB/second of aggregate bandwidth, making it particularly adept at manipulating data at high speeds. FLOPS-wise, a 3.55 GHz Power7 delivers 218 Linpack gigaflops. For comparison, the POWER2 SC processor, which was the chip that powered cyber-chessmaster Deep Blue, managed a paltry 0.48 gigaflops, with the whole machine delivering a mere 11.4 Linpack gigaflops.”via HPCwire

So how did it go? In short, Watson got off to a commanding lead and was crushing it early on…until the humans adapted. You see, Watson is extremely accurate when it comes to coming up with the right question to fit the answer to the clue. There were a couple of flubs, but for the most part I’d say Watson was as good or better than the human champions. Where Watson truly shone though was reaction time. You could just tell watching the humans madly pressing the buzzer that Watson had them beat when it came to triggering the buzzer when it knew the answer. I noticed something though about halfway through: I think that the humans started buzzing in without knowing the answer.

This is pure speculation, but to me it looked like the two human champs switched to triggering the buzzer before the clue was even partly finished – I think they both realized that if they waited until they heard the full clue, Watson would continue to beat them. By the end of the game Rutter was at $5000, Watson was at $5000, and Jennings was at $2000. This is a far cry from the first 5 minutes where Watson was snagging all the questions.

I don’t know the mechanics of Jeopardy very well, but it looks like the contestant can buzz in at any time after the clue has started to be read aloud. It’s a risk buzzing in on something that you might not know the answer to, but it’s a call that a human can make on the fly – and one that a machine would be hard-pressed to make.

One of the things they didn’t explain fully was how Watson go the clue: they said it was “delivered as a text file”, but what does that mean exactly? Is there someone pressing a SUBMIT key on a keyboard as Alex Trebek finishes the clue? No, there would be too much latency with that approach. Does Watson get permission to read a text file as Trebek finished the question? That seems equally problematic – it would have to be machine driven somehow. Voice recognition would seem to be the only fair way to tackle this problem, but if Watson mis-recognized a word, it would throw the whole game off. This is something I hope they explain more about later on.

This was some fascinating TV! I’m looking forward to watching the next two episodes.

UPDATE: This article says that Watson is “fed the answer in text form at the same time the answer panel appears to the two human players.” That explains Watson’s edge in buzzing in – it can parse the text file faster than a human being can read the clue. The only way for the humans to win then is to buzz in before they read the clue. Gutsy!