If you can't be bothered to write it, why should I bother reading it?
Hmm, if you read his previous blog posts pre-ai the tone is not much different. I hate the idea that this dude may just sound like AI at this point by accident.
[dead]
You're Not a Better Engineer Because You Type Git Commands by Hand
111–120 of 157 posts
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#112Earlier quoted context omitted.
Hmm, if you read his previous blog posts pre-ai the tone is not much different. I hate the idea that this dude may just sound like AI at this point by accident.
It somewhat boggles my mind that there are an incredible number of persistent, useless, and annoying comments on here every day accusing any and every article of being AI slop. AI is a machine that generates content that is supposed to be statistically identical to the content that it was trained on, and it's trained on the content posted here. The content here will look like AI generated content, and the AI generate…
[dead]
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#113All above comes at a cost of author slowly starting to understand less and less code in their own projects. Then in other projects as well. After the initial boost is over they will have to pay money just to stay afloat because they have already outsourced their thinking. I’m not anti AI, but I’m very worried about this bragging “you are not better engineer if you do things yourself”. Yes, you are, it all comes in sm…
Maybe it does make you a better engineer because when you look back on a commit that you were rushed on, you don't see a commit message of "Fixed it".
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#114it's tough for people here to admit, but AI is good at summarizing and that includes commit messages and PR fields but that does NOT mean you get to skip understanding the code & whipping the AI in line during implementation my preferred workflow: - think hard about the problem before touching the keyboard - back and forth with the AI, swatting down bad implementation ideas and poking holes - settle on a detailed imp…
This is what I do mainly. I spend more time designing the solution, iterating by hand when it matters and anything that should be automated, let it be.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#115All above comes at a cost of author slowly starting to understand less and less code in their own projects. Then in other projects as well. After the initial boost is over they will have to pay money just to stay afloat because they have already outsourced their thinking. I’m not anti AI, but I’m very worried about this bragging “you are not better engineer if you do things yourself”. Yes, you are, it all comes in sm…
The author had 27 years of experience but still found "babysitting git" was painful.
I couldn't remember what's the last time git got in my way. I guess such benefit from AI is probably very specific to their setup. I don't know, maybe the author had some really complex workflow or used some super advanced git features.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#116Refactoring stuff has been easy for a long time.
Moving git commits or stuff that's not yet committed to another branch is not that difficult as well.
Sure, with AI you don't need to know how to do it. I works argue though that refactoring is faster and easier than having the AI doing it for you.
Commit messages, yes, that's much easier with AI.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#117All above comes at a cost of author slowly starting to understand less and less code in their own projects. Then in other projects as well. After the initial boost is over they will have to pay money just to stay afloat because they have already outsourced their thinking. I’m not anti AI, but I’m very worried about this bragging “you are not better engineer if you do things yourself”. Yes, you are, it all comes in sm…
The author had 27 years of experience but still found "babysitting git" was painful. I couldn't remember what's the last time git got in my way. I guess such benefit from AI is probably very specific to their setup. I don't know, maybe the author had some really complex workflow or used some super advanced git features.
I have only about 17 years of experience and I consider myself a moderately advanced git user — I do interactive rebases with squashes, rewords or reordering and I do chunk manipulation per commit all the time. Or at least I used to.
Now I just type into the LLM what I want it do with git and it does it for me, much much quicker. I did not find "babysitting" git painful before, but I today I do feel like doing it manually is a just huge waste of time. A $20 LLM subscription could do this shit for me just as well or better while I spent my time doing more fun and interesting things.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#118All above comes at a cost of author slowly starting to understand less and less code in their own projects. Then in other projects as well. After the initial boost is over they will have to pay money just to stay afloat because they have already outsourced their thinking. I’m not anti AI, but I’m very worried about this bragging “you are not better engineer if you do things yourself”. Yes, you are, it all comes in sm…
The author had 27 years of experience but still found "babysitting git" was painful. I couldn't remember what's the last time git got in my way. I guess such benefit from AI is probably very specific to their setup. I don't know, maybe the author had some really complex workflow or used some super advanced git features.
Don’t beat me, I’m getting old. Even Git is starting to feel like unnecessary cardio.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#119What is with all these people that are so interested in other people's workflow to the point of writing weirdly aggressive manifestos like this. "If you don't do it like me, you're wrong!" I would like to be the first person to state that I don't give a damn about your workflow . Do whatever you want!
Sure, do whatever you want on your own projects. But on a team, I expect people to follow some basic decorum on standards for commit messages and code reviews. That was hard to enforce and get before (GitHub encourages bad practices) but it's bloody impossible now.
I actually think it's much easier now when most contributions are LLM-assisted or LLM-authored.
Like, at my job we went from wild-west everyone uses their own commit message style to very nice uniformed one now when everyone's using Claude Code following the style enforced by AGENTS.md/CLAUDE.md
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#120Force yourself to use git with the command line for as long as it takes to not confuse you with day to day operations. Then choose whatever interface you want to make your life easier.