You’ve seen it happen. You click on a GitHub link for a new, exciting project—say, a graphical desktop for the ZX Spectrum. You’re expecting a love letter to the 1980s. You’re ready to feel that warm rush of nostalgia for a machine you grew up hacking on. Instead, you’re hit with a wall of text that feels like a corporate press release. It’s polished. It’s comprehensive. And it is entirely, unmistakably fake.
Recently, a developer released zxdesk, a genuinely cool graphical desktop environment for the ZX Spectrum. By all accounts, the code is legitimate. It’s a technical marvel to squeeze this kind of performance out of vintage hardware. But the community didn’t celebrate. They revolted. Why? Because the README was written by Claude. In retro-computing, the code isn’t the product. The human story is.
One commenter nailed the exact problem: “It’s Claude’s earnestness that’s so disingenuous in this kind of write up. This voice Claude has where it believes the work is important and deserves to be taken seriously.” That’s the rub. When an AI tells you a project is a “labor of love,” it doesn’t feel like pride. It feels like a lie.
Think back to the 1980s. Another commenter shared their own memory: “Wow I did so many of those when i was 12 or around that age. Mostly I tried copying the Amiga Workbench on my +2A… Obviously at that age my knowledge of coding and window managers wasn’t exactly deep.” That is the soul of retro-computing. It’s the story of a 12-year-old staring at a screen, fighting with limited memory, driven by pure, unadulterated obsession. You can’t generate that with a prompt. You have to live it.
When you outsource your passion to a language model, you void the emotional warranty of your work. The tension here is brutal. We want to love a tribute to our childhood machines, but we feel unsettled when an AI voice claims importance on our behalf. The ZX desktop project triggers a deep nostalgia for a handmade era, only to crash into the present-day reality of AI-generated slop.
This isn’t just about retro computing. This is the new authenticity threshold for anyone building and sharing work online. AI tools are completely tolerated for implementation. Use them to write your boilerplate, optimize your loops, or debug your syntax. But the moment you let AI narrate the why of your project, you lose the audience. We tolerate AI for the heavy lifting, but we demand human hands for the heart.
If you build something, tell us about it yourself. Tell us about the late nights, the bugs that drove you crazy, the moment it finally clicked. If you can’t be bothered to write your own README, why should we be bothered to read your code? Don’t let a chatbot steal your voice. The community is judging your relationship to the work, and right now, Claude is a terrible spokesperson for your soul.
FAQ
Q: If the code is good, why does it matter if AI wrote the documentation?
A: Because in niche communities, the documentation is the narrative. If you can't articulate your own passion, the project is just sterile code. The human context is the whole point.
Q: So I shouldn't use AI for anything?
A: Use AI for implementation, not narration. Let it write the tedious boilerplate, but you must write the 'why'. If a machine explains your motivation, the motivation is dead.
Q: Isn't complaining about AI READMEs just gatekeeping?
A: No, it's demanding truth. An AI pretending to be 'earnest' about a retro project is a lie. We don't want polished corporate speak; we want raw, human imperfection.