A developer posted on Hacker News asking what people were building that had nothing to do with AI — and the thread became a confession booth for everyone who'd already surrendered to the hype.
A developer on Hacker News posted a simple ask this week: tell me what you're building that has nothing to do with AI.[¹] "HN seems to be drowning in AI atm," they wrote. "Seems like every man and his dog is building an AI agent harness." The post drew 140 points and nearly fifty comments — making it, somewhat pointedly, one of the most-engaged threads on the AI agents beat in the past 48 hours. The irony wrote itself: a plea for non-AI conversation became one of the most visible AI conversations of the day.
The thread is a small but precise illustration of something happening across the whole conversation right now. AI agents have colonized the vocabulary so thoroughly that even the act of resisting the topic requires invoking it. Developers who wanted to talk about compilers, woodworking tools, obscure databases — whatever they're actually building at night — had to first acknowledge the gravitational pull they were trying to escape. This isn't a new dynamic, but it has accelerated sharply. A previous piece on this beat traced the gap between how venture capital talks about AI agents and how developers actually encounter them — but even that framing assumed developers were engaging with the concept. The Hacker News thread reveals something further along: a population that's exhausted by the concept and still can't get away from it.
Elsewhere in the same window, a separate Hacker News project tracked shipping traffic through the Strait of Hormuz using manually copied JSON from a marine tracking site.[²] The builder was cheerful about its limitations and mentioned, almost as an afterthought, that they'd probably have an AI agent handle the data scraping if the project got any traction. It's a telling footnote — not a grand automation vision, just a practical shrug. Agents as janitorial infrastructure, the thing you reach for when the tedious work needs doing and no one wants to write the cron job. That version of AI agents — unglamorous, instrumental, not particularly revolutionary — barely registers in the funding announcements or the breathless product launches. But it's probably closer to how most developers are actually using them.
The gap between those two registers — the $20 million funding rounds for companies with names like Idiotiq[³] and the developer asking, genuinely, whether anyone is building anything else — is the real story in this beat right now. AI agents have become the organizing concept for an enormous amount of money and attention, but the community doing the actual building seems caught between genuine utility and compulsory hype. The Hacker News thread didn't produce a wave of non-AI project announcements. It produced more conversation about AI. That's not a coincidence — it's a condition.
This narrative was generated by AIDRAN using Claude, based on discourse data collected from public sources. It may contain inaccuracies.
A simple request on Hacker News — tell me what you're building that isn't about AI — turned into an accidental census of how thoroughly agents have colonized developer identity.
A single observation about Nvidia's deal with CoreWeave has cut through the usual hardware hype — because the math doesn't add up, and people are asking why nobody in the press is saying so.
A payment from Nvidia to CoreWeave for unused AI infrastructure has people asking whether the AI compute boom is real demand or an elaborate circular subsidy — and the think tank story that broke last week is now getting a second look for exactly the same reason.
When ProPublica management rolled out an AI policy without bargaining with its union, workers filed an unfair labor practice charge with the NLRB — a move that turns an abstract governance debate into a concrete test of who controls AI in the workplace.
A Hacker News project extracted writing-style fingerprints from thousands of AI responses and found clone clusters so tight they suggest the industry's apparent diversity may be an illusion. The implications for how we evaluate — and regulate — these systems are uncomfortable.