Ask HN: Where is our profession (programmer) going?

Programmers are asking if the job is turning into babysitting chatbots

TLDR: A programmer sparked debate after saying one company seemed to let an AI chatbot handle nearly the entire software-making process. Commenters were split between seeing a powerful new tool and warning that people are gambling their jobs and businesses on something they still don’t fully trust.

A founder dropped into Hacker News with a full-on career crisis after visiting a 15-person software company and seeing workers apparently letting Claude, an artificial intelligence assistant, do almost everything: write the code, explain the code, review the code, and even help define the problem. The vibe was less “careful craft” and more five chatbot windows open and vibes-based decision making. That set off a classic Hacker News pile-on, with commenters split between awe, panic, and dark comedy.

The loudest critics basically said: this works until it very much doesn’t. One freelancer warned that companies are becoming dangerously dependent on a tool that could get more expensive or restricted later. Another commenter went full poetic doom, mourning the loss of the old idea of computers as precise, dependable machines and joking that today’s systems might give you “a butterfly” when you asked for a paperclip. Others were stunned anyone would trust their business to tools they still catch making obvious mistakes.

But it wasn’t all anti-AI rage. A few people argued the real magic isn’t the chatbot, it’s the human using it. In that view, skilled developers are still the brains of the operation; the tool just makes them faster. One commenter summed it up like a movie trailer: the race is still on, just not on foot anymore. Translation: the job may not be dead, but the rules are getting rewritten in real time, and the comments section is absolutely not calm about it.

Key Points

  • The author previously ran a three-person software company for about four years and recently visited a friend’s 15-person company.
  • The author says they are already a heavy Claude user but were surprised by the extent of Claude-centered development practices they observed.
  • The post describes code no longer serving as the main source of truth, with Claude being used to generate and explain code.
  • The author reports that human code review and deep human understanding of problems appeared to be reduced or replaced by Claude usage.
  • The author asks whether this observed workflow is representative of other companies and questions where the programming profession is heading.

Hottest takes

"when asked to produce a paperclip, may instead produce a butterfly" — luckman212
"This works, until it doesn’t" — al_borland
"We’re still running the race, but it’s just not on foot anymore" — uproarchat
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.