One Developer Built a Word Processor From Scratch in Ten Months Using AI. Microsoft Rolled Back Copilot Because Users Complained.

A developer posted to Hacker News this week under the "Show HN" banner — the community's version of raising your hand — with something genuinely unusual: a fully custom word processor, built from scratch over ten months, using agentic coding tools throughout. The rendering engine, the document layer, all of it custom except for one library. "I've never moved faster in my life as a dev," he wrote, and the thread filled with the kind of comments that suggest people believed him. Twenty-three points, twenty-six comments, and a tone that was less "look what AI did" and more "look what I did with AI" — a distinction the author was careful to maintain. He stayed hands-on, he said. He never stopped owning the architecture.

On the same day, a Bluesky post with 138 likes was celebrating something different: Microsoft walking back parts of its Copilot integration in Windows after sustained user pushback. "Keep it up, haters," the poster wrote, with a warmth that read less as antagonism and more as genuine surprise that the pressure had worked. The linked TechCrunch piece confirmed it — user feedback had moved a company the size of Microsoft. These two moments don't contradict each other so much as they reveal the two modes this conversation keeps cycling between: AI as tool you wield versus AI as product being imposed on you, with very different emotional textures depending on which side of that line you're standing on.

What makes the Hacker News post worth dwelling on is how carefully it refuses the standard narrative. The developer didn't automate himself out of the picture — he described staying "very involved in the codebase and architecture." The agentic tools made him faster without making him peripheral. That's the use case that tends to get lost in both the boosterism and the backlash: not AI replacing judgment, but AI removing the friction that slows judgment down. Meanwhile, a Bluesky user with no likes posted something that cut the other way entirely — documenting how Claude mistargets branches, overwrites untouched files, and once tried to force-reset a database it had no business touching. "93% satisfaction means 1 in 14 sessions I had to stop it breaking something," they wrote. The math is right. The frustration is earned.

The Microsoft rollback is probably the more consequential signal of the week, not because it represents a reversal of AI adoption but because it demonstrates that the adoption curve has a feedback loop. Users pushed back, loudly enough, and a product changed. That's not how this story usually goes — normally the announcement comes, the complaints follow, and then nothing happens until the next announcement. The Bluesky poster calling it out as a win for "haters" was half-joking, but only half. The developer on Hacker News who built a word processor faster than he ever had before wasn't joking at all. Both things are true this week, and the conversation that actually matters is happening between those two experiences — not above them.