March 24, 2026
AI Talk Fatigue: Comment Section Cage Match
Is anybody else bored of talking about AI?
Half the crowd is over AI talk, the other half is over the complainers
TLDR: An engineer says AI talk has drowned out real projects and even led bosses to chase meaningless metrics. The comments split: some are exhausted, others mock the complainers, and a few say the chat is maturing into practical tips — a snapshot of hype vs. value fatigue.
One engineer lit up the timeline with a spicy confession: they’re bored of talking about AI. Yes, they use it daily and admit it turbo‑charged their new job, but the endless chatter has eaten their feeds. Instead of cool builds on Hacker News and Kagi Small Web, it’s repetitive “my AI workflow” threads. They gripe that bosses now chase “use more AI” and track token counts — a pointless throwback to measuring lines of code. Their plea: show the table you built, not the hammer you used. And they know the irony. Same.
The comments turned into a roast and culture war. Siah dropped a two-word mic: “Not me.” Bena clapped back with meta logic: you’re still talking about it. Jvanderbot said “Yes, very much,” adding that teams are out of sync, though chats have shifted from doom about a jobpocalypse and “the singularity” to practical tips. Thrill rolled eyes at “people constantly complaining like they have special insight,” while ternera called AI a clicky buzzword shoved into places it doesn’t belong. Meme watch: “old man yells at cloud,” “hammer cult,” and the cursed metric tokens-per-dev. Verdict: half bored of AI talk, half bored of the boredom — everyone online.
Key Points
- •The author uses AI daily and reports significant productivity gains in a new, complex role.
- •They argue online developer discourse is saturated with AI tooling posts, citing Hacker News and Kagi Small Web.
- •The piece contrasts a prior “Product Engineer” focus on delivering product value with today’s emphasis on AI-assisted coding workflows.
- •Management is portrayed as promoting ‘use more AI’ initiatives and tracking metrics like tokens per developer.
- •The author urges a shift back to sharing outcomes and value delivered rather than focusing on tools, acknowledging the irony of their critique.