As a 14 year old dude from a backwater burb in 1984, I had no idea what Madonna was going for. Annie Lennox clearly didn't get it either LOL. Was good for me to read this perspective.
Years later I did see her performing live on a tiny TV on a ferry on a rough night crossing the English Channel. I noticed her go down rather than up for some notes and it clicked for me... "wait a sec this person is not lip-syncing, she is an actual musician, maybe I should reevaluate" (:
I wonder how many choices you can give this thing in multiple choice response mode. I'm guessing you could give it enough choices to produce Turing complete programs one symbol at a time when running in a loop, or to hold a conversation when given a vocabulary as the choices. It would be particularly hilarious to just let it choose the next ASCII character of output in a loop.
My guess is that due to its design there is no support for prompt caching, as there would normally be no reason for it. So the performance of my idea would probably be appalling as every step in the loop would reevaluate every input and output token. But it would be interesting to see the outcome.
When so many people talk about companies going with React "because AI knows React," it's interesting to see Shopify draw the opposite conclusion: AI "knows" all major platforms and frameworks, so at a certain scale it makes sense to let AI handle cross-platform development as a translation problem.
Modern LLMs evolved from translation models, and they still seem to work best at translation-shaped problems. Even if you are asking them to translate specs to code, or code for system A to code for system B.
In my case, I added SQLite and Postgres adapters to a formerly MongoDB-specific CMS, including support for a largely compatible API, "in one wild weekend..." followed by lots of verification. That was only practical because we already had a large test suite. But it was still a task that would have been out of the question for our team size before Opus 4.6 or so. Again, it was very much a translation-shaped problem.
There are quite a few CMSes that do static builds natively. If you hand one of those to Claude Code, you can get a more flexible and maintainable result more quickly. You can also point Claude Code to a CMS starter project in folder A And a vibe coded static site in folder B and pull them together.
That being said... if you're the sole author of your site, anything goes and yeah, you probably don't need a proper CMS. I certainly built my own share of 100-line Perl static site builders back in the day.
Wow yes keeping a wiki up right now is a tall order. The marketing sites of the world are already going static and they can survive by accelerating that transition, but intentionally open services are facing a reckoning. I wish you good hunting.
reply