git merge "conflicts"

(not really an issue, but still a waste of time and concentration, when every now and then, using more than one branch, small edits, merge, and rebase, git diff complains about "conflicts" that are obvious to solve for a human but still not for a machine, despite the hype about the age of AI, coding co-pilots and the like...)

It's obvious to you, a human (hopefully), but not so much to a machine. There's git rerere that kind of mitigates that.

I enjoy the whitespace conflicts most.

It's a bloody empty line vs a single space, why.... can't you solve this for me, but can tell the difference between thousands of lines in a single file and ignore white space in diffs, but no, we can't auto merge a single space because hot damn that's way to complex.

The problem is that sometimes its obvious because you know something the machine does not, in which case no AI would be able to solve it.

And adding the “meta data” required for the machine to know what to do would require some new syntax and standardization.

And while AI can seem like magic, its not, it requires training which gets more snd more complex as thing get more abstract.

So is this a waste of life ?

Is programming a waste of life ? Is learning a waste of life?

Granted even exercise is like running in a hamster wheel and most people are
More
Consumptive than productive