I used AI to get a summary of this post, because in 2026, if you are not delegating this kind of reading overhead to AI, you are burning money. And, more importantly, you are ruining your life.
You're Not a Better Engineer Because You Type Git Commands by Hand
51–60 of 157 posts
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#52So on one hand it states: Delivery is becoming a sequence of checks, not a ritual The same thing happens when it is time to deliver. First, I invoke my /definition-of-done skill. It checks whether the implementation covers what was stated in the PR and in the plan. It checks tests and the other validations I care about. It tells me when something looks unusual, broken, or missing. When everything looks good, I invoke…
> Obviously the author has irreversibly became AI-pilled and the day API costs balloon or APIs are down, what work will the author do?
I am old enough to remember having these thoughts when documentation for things moved from books to being online. I thought looking things up in the internet was a recipe for failure, because the internet was new and unstable and changing, and what happens if you run out of your 10 hours a month of being online, or if someone in your house picks up the phone and you are disconnected?
Clearly those people were internet pilled, and the day the internet costs ballooned or was down, what would they do?
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#53Eh, agents commits are always too verbose. I don't need a 3 paragraph mini novel. Design can go in a design docs folder, project info goes in the issue tracker. The commit should be a short summary <1 paragraph for quick context
Just put your last sentence in your AGENTS.md then
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#54What 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.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#55All 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…
i've got 4 AI read machines; the smallest will be 72GB; the largest 128GB; they're not wunderkind, but they're all running local models.
We're definitely entering a different set of skills and we're costing on our abilities to use these systems raw, and when we start using them via AI, we're losing that raw context.
But when the gains allow us to flesh out where we've never done so, how to say no?
I never spent time on either docs or tests, but since guiding the AI requires several slices through the same logic/architecture/bug footprints, my work flow has to include looking at and maintaining all three.
If I didn't, the AI would be much worse than me doing it myself. Which means at the very least, whoever comes afte rme will have the same hardware and models and maintain the same level of support.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#56If 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.
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 generated content will look like the content here. By fucking definition.
---
Instead we get a bunch of pseudo-intellectual, hokey about how "my AI radar is perfect!" and "I can always spot it because of [insert bullshit about detecting style that's semantically the same as the pre-existing stuff]".
It's just... exhausting.
Yes - there is a lot of AI content on here. Just like there were a bunch of (and still are) under whelming marketing articles on here. Just like there's STILL a bunch of interesting and engaging articles (some of them even written by AI!).
Just vote based on the content and move on with your lives.
People out here wasting time and energy on trying to burn witches. If you want a "sure-fire" AI free experience... Go talk to a real person, in person. Otherwise...
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#57AI discussions these days remind me of college when I agreed to "debate" some Christians. You can assign the camps however you want to assume. But the point is that there is not going to be a lot of constructive discussion.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#58Hey Claude, Check if Claude 2, Claude 3 and Claude 4 are done yet, then merge their changes.
Hey cron, keep reminding Claude to do that while I drink.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#59Eh, agents commits are always too verbose. I don't need a 3 paragraph mini novel. Design can go in a design docs folder, project info goes in the issue tracker. The commit should be a short summary <1 paragraph for quick context
Codex is the opposite problem. If you don't aggressively prompt it, and let it write commit messages it will literally just do one incomprehensible line.
Claude will write a novel, sign it with its signature like it's a person, and fill it full of advertisement language and marketing text.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#60All 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…
How do you justify it against all the other abstractions you've accepted and no longer know how to do (or never learned in the first place). Why are the current set of manual steps the right level to be permanently aware of?
Because the abstractions of old still required you to read man pages and learn stuff.
And manual steps are good. At least you know what is happening.
The old Unix philosophy. Simple tools that combined become powerful.
If you use _anything_ in production, you better make sure you understand the stack.