You're Not a Better Engineer Because You Type Git Commands by Hand

Coders are feuding over AI doing the boring bits while humans keep the blame

TLDR: A longtime programmer says AI now handles the annoying writing and organizing work around coding, saving huge amounts of time. Commenters are split: some love the shortcut, while others say those notes are part of taking responsibility and proving you actually understand what you changed.

A veteran programmer just dropped a spicy confession: after nearly three decades of coding, he’s happily letting artificial intelligence handle the fiddly, boring chores—writing commit notes, pull request summaries, code comments, naming files, and all the tiny bits of cleanup that usually drain hours from a workday. His argument is simple: these tasks matter, but most people hate doing them, do them badly, or skip them entirely. AI, he says, is more consistent, less moody, and weirdly good at keeping a project neat enough for both humans and bots to understand.

But the comment section? Absolutely not ready to clap politely. One of the loudest reactions was basically: if you couldn’t be bothered to write it yourself, why should anyone bother reading it? That became the emotional center of the debate. Critics argued these little notes aren’t just paperwork—they’re proof you understood what you changed and are willing to stand behind it. Others warned this feels like the old argument over point-and-click tools versus learning the hard way: convenient until something breaks and you need a wizard to save you.

There was also a more subtle burn: even people who agreed the post was thoughtful said handing writing over to AI won’t make you a better writer. Ouch. The mood was less “AI will save us” and more “cool shortcut, but don’t pretend it makes you noble.” In other words, the real drama isn’t whether robots can write the notes—it’s whether humans are quietly outsourcing responsibility along with the busywork.

Key Points

  • The author says AI agents now perform repetitive engineering tasks including commit messages, PR descriptions, comments, naming conventions, Git hygiene, issue tracking, and release workflows.
  • The article states that writing and reviewing good commit messages and pull request descriptions historically consumed substantial developer time.
  • The author describes maintaining detailed code comment and file-header standards, and says AI now automates much of that upkeep.
  • The article argues that repository structure and explicit context help LLM-based tools interpret intent and identify inconsistencies.
  • The author says AI improves consistency in naming files, classes, functions, and modules across long-lived projects.

Hottest takes

"If you can't be bothered to write it, why should I bother reading it?" — cratermoon
"Those are probably best at least edited/tuned by humans. Because they're meant to be read by humans." — cmrdporcupine
"You won't become a better writer letting AI do it for you." — mpalmer
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.