Yeah, one of my co-workers just plays video games while his bot works away. That’s not my way, but imo, that’s a much better trade than trying to spin between 5 different tasks and toiling harder than you ever did when you had to do it “manually.”

If they want fast and cheap they can have it, but don’t work yourself into a burnout trying to make the output totally slop free.

I can relate, but there are still oases of sanity out there. Very hard to find anywhere profit motive is worshiped over common sense, though.

This is the way. It’s how we got our CTO to stop sshing into pods to yolo his ideas.

I’m lucky enough to work somewhere that doesn’t dictate what tools I have to use. I don’t use it for code, because that’s just not fun for me. But I will use it once in a while when web search just totally fails me, but I know the answer is Out There (in the weights of scraped corpus).

I’m fighting back, I guess, mostly just by showing that it’s easy and enjoyable to do things without checking in with Sam Altman first. ;p

Yeah, I was complaining to a friend about how everything I like seems to be getting worse, and they basically said what you said: try to be zen about it, this is just a continuum of the same race to maximise profit that’s been going on before we were born. You just try your best to be a good person who cares about other people, and try not to sweat what you can’t control.

On my free time I don’t currently write code, non-technical hobbies and maintaining the homelab I conjured eat it up.

I should get more non-technical hobbies, especially physical ones… But I’ll be literally sat at my wfh desk typing for work, looking forward to after 17h when I can switch the kvm to writing code for pleasure lol. I do really like programming though. Somehow still not sick of it after all these years.

The man page sheds a bit of light, but basically it the stuff on top of the core git functionality.

LOW-LEVEL COMMANDS (PLUMBING)
       Although Git includes its own porcelain layer, its low-level commands are sufficient to support development of alternative
       porcelains. Developers of such porcelains might start by reading about git-update-index(1) and git-read-tree(1).

       The interface (input, output, set of options and the semantics) to these low-level commands are meant to be a lot more stable
       than Porcelain level commands, because these commands are primarily for scripted use. The interface to Porcelain commands on the
       other hand are subject to change in order to improve the end user experience.

Related, but not to be confused with the --porcelain option available for some git commands. Eg, from the man page for git status:

       --porcelain[=<version>]
           Give the output in an easy-to-parse format for scripts. This is similar to the short output, but will remain stable across
           Git versions and regardless of user configuration. See below for details.

Like it says, if you’re doing any kind of scripting this will remove weird escape codes to make parsing the output easier.

Oh yeah, totally.

Headcrab?

Beauty beyond compare

bnone

Yeah, we say bone not bany, what gives…