A Hacker News post published on June 7, 2026 has quietly surfaced a question that cuts to the heart of where software development stands today: who is still writing code without AI assistance, and what's holding them back? The thread, which currently sits at a low engagement score of just 2, represents one of those rare moments where someone in the community is willing to ask the uncomfortable question that many developers privately ponder but rarely vocalize. The original poster describes themselves as someone who loves coding and has used vim exclusively for approximately ten years—making them part of an increasingly small cohort of power users who mastered modal editing before AI was even a twinkle in a GPU cluster's eye. Yet despite this traditionalist background, the poster confesses they've fully embraced modern AI coding tools, having cycled through GitHub Copilot, Anthropic's Claude Code, and OpenAI's Codex. "I feel it's become as common-place as autocomplete, or intellisense," the poster wrote. "Though I remember people used to hate those too." This comparison frames AI coding assistants not as a revolutionary departure from existing development workflows but rather as an evolution of tools developers already accepted years ago—IntelliSense just got better, more context-aware, and capable of generating entire functions instead of mere autocompletions. The poster offers their own perspective on what these tools actually represent in practice: "AI is like the modern day intellisense + docs targeted for exactly what you're doing, always (maybe that + an intern that never sleeps)." This framing strips away much of the hype surrounding AI coding tools and reduces them to something pragmatic—a tireless junior developer who has memorized the entire documentation corpus and can apply it instantaneously.

The Silence Around Going Cold Turkey

What's notable about this thread isn't what was said but what's conspicuously absent. With a score of just 2, the post hasn't generated significant engagement—suggesting either that the community has moved past the debate entirely (AI tools have won and there's nothing left to discuss) or that those who resist AI assistance are simply not participating in public discourse about it anymore. The question touches on something deeper than workflow preferences. For many developers, coding without AI represents a form of craft identity—the belief that the ability to produce working software from pure thought is itself valuable, separate from any business outcome. There's an old-school hacker ethos embedded in shipping code that you wrote yourself, line by line, with your own neurons firing in sequence. The thread's low engagement suggests that the resisters may have already self-selected out of platforms like Hacker News, retreating to corners of the internet where their preferences are validated, or simply accepting that mainstream development culture has moved on without them. Either way, this HN post serves as a quiet marker of an inflection point—the moment when asking "who still codes without AI?" became a genuine question rather than a rhetorical one.

Key Takeaways

  • Longtime vim users (10+ years) are not immune to adopting AI coding tools despite traditionalist backgrounds
  • The framing of AI as "fancy autocomplete" may be the key to its widespread adoption—it's not revolutionary, it's iterative
  • Low engagement on resistance-focused threads suggests either victory or retreat for non-AI developers
  • The developer community's self-selection patterns may mean we no longer hear from those who opt out

The Bottom Line

This HN thread won't trend, but it documents something important: the moment when asking "who still refuses AI?" became a sincere inquiry rather than provocation. Whether that's progress or loss depends on whether you think shipping software faster matters more than maintaining the craft traditions that built this industry in the first place.