You are outsourcing your life to AI?
Good for you, but don't be so pretentious, please.
You're Not a Better Engineer Because You Type Git Commands by Hand
11–20 of 157 posts
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#12[dead]
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#13Ew at the bit about letting AI write your commit messages. Don’t bother - if you didn’t take the time to write it why should anyone take the time to read it. I’ll just ask my AI to extract the intent from the actual code if I need it.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#14Picking on a particular nit here, but I think it is indicative of the broader flaw with this argument:
To rename `PostgreSQLClient`, I press F2 and type the new name, and I'm done.
I don't have to wait for an agent to "perform the refactor, update references, run the tests, fix the missing pieces, and mark the relevant checkboxes in the ticket" (btw, what checkboxes..?)
I press a key, type my change, and I'm done.
Wasting time waiting for tokens is also wasting time.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#15[deleted]
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#16TBH writing shell scripts (and automation tools generally) is the grunt work I most love it for. Git commits and PR descriptions? Those are probably best at least edited/tuned by humans. Because they're meant to be read by humans.
Our commit messages have become useless since we adopted a shared agent skill for making commits.
The LLM tends to fill the messages with irrelevant details while still failing to mention what the change actually does.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#17I see a flamebait title, I click flag. Simple as.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#18Just from the title I didn't even realize this would be a post about AI. I thought it was going to be about using Git in your IDE or other git UI tooling.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#19> In 2026, if you are not delegating this kind of engineering overhead to AI, you are burning money. And, more importantly, you are burning your life.
AI use can be a divisive topic among developers but I generally believe it is a useful tool. That said, please don’t broadly advise people on what’s best for their life. It will only make people push away from AI more.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#20I find I keep the git add to the be one thing I keep track of (in production services, if not throw-away or non-prod visualization vibe coded things). I've never even used git add . - I git diff each file one by one, and git add them in one by one. It's needed to prevent my own errors, and it's needed to keep some model of what the AI is doing in my mind. Now, I myself don't do much commenting in line; I tended to rely on good names, good function comments, good module descriptions as comments at the top of a file; for the flow, I would log a lot and hopefully the failure/success logs made the thinking clear for what is going on and why. But I let the AI keep all its comments, till they crowd out the code at least.
Replying to a comment below (on shell scripts), I use it for shell scripts, python "get this data and slice it in these ways" and elisp, all the time. 30 seconds to get and answer instead of 30 minutes. Being able to do them in 30 minutes took a lot of skill and practice, but the pleasure of finishing that for an ad hoc thing when I really just want the data output is something I can give up.