>Ironically, the audience that values all that structure the most is now LLMs.
LLMs are not people and they don't have values.
You're Not a Better Engineer Because You Type Git Commands by Hand
61–70 of 157 posts
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#62I am still skeptical of ai running everything, given how much it changes and quickly, I’ve not quite given over all control. And I try and use it to learn more about things normally I wouldn’t have time for.
The goal of writing the git messages is to slow down and prevent a worst case scenario where work is lost. Given how powerful git is I think giving control over is like doing a sure fire migration without a backup in the way that it can lead to easily preventable problems that are difficult to fix afterwards, it’s just a bad paradigm.
I can appreciate some parts of this, like keeping a painfully detailed record of the changes written by ai, I have this too, but it is separate for the content meant for actual human eyes.
Like others here I find a hard time finding specific evidence or reasons for some of op’s thoughts, but in general it just seems like a recipe for problems when you’re too trusting with ai with all the processes
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#63What 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.
You’re mistaking how with what. We’re talking about „how” here
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#64All 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…
[dead]
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#65All 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…
There's truth in this, git is probably the least of anyone's worries when it comes to understanding your code if you're pulling in any external dependencies in your codebase. For a typical web app these days, you're hundreds of thousands of lines deep in code written by someone else on day 0.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#66Earlier quoted context omitted.
A farmer producing meat is a better farmer than me even if I hire my own farmer. If we invent a meta-farmer profession (for those who hired a farmer) I will be great meta-farmer, but still suck as a farmer
But I don't want farmers, I want meat
I don't think that's the point. The point is that if you outsource thinking to a machine, you will lose your ability to think and reason on your own, and overtime become a worse engineer. Maybe the software ai writes will be fine, idk... But eventually, you will be an objectively worse engineer than someone that doesn't need a machine to think and write for them.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#67Maybe I'm alone in this, but I've always found the git GUIs more confusing than just typing out the commands. They never seem to map well to how I work.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#68What 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!
I imagine most people don't give a damn about others' workflows. But they're not posting about it, because they don't give a damn.
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#69Earlier quoted context omitted.
A farmer producing meat is a better farmer than me even if I hire my own farmer. If we invent a meta-farmer profession (for those who hired a farmer) I will be great meta-farmer, but still suck as a farmer
But I don't want farmers, I want meat
Sure you don’t need a farmer factory ?
Re: You're Not a Better Engineer Because You Type Git Commands by Hand
#70I don't get these kinds of posts. Zero how-to, zero share about the tradeoffs the author took.
It's just a random internet dude telling us how he thinks other people should feel about their work.