The Programmer Identity Crisis

> One could only wonder why they became a programmer in the first place, given their seeming disinterest in coding.

To solve problems. Coding is the means to an end, not the end itself.

> careful configuration of our editor, tinkering with dot files, and dev environments

That may be fun for you, but it doesn’t add value. It’s accidental complexity that I am happy to delegate.

Configuring editors, dot files, and dev environments consistently adds value by giving you familiarity with your working environment, honing your skills with your tools, and creating a more productive space tailored to your needs.

Who else becomes the go to person for modifying build scripts?

The amount of people I know who have no idea how to work with Git after decades in the field using it is pretty amazing. It's not helpful for everyone else when you're the one they're delegating their merge conflict bullshit too cause they've never bothered to learn anything about the tools they're using.

Have you considered that the problem is with Git and not the users?

How dumbed down does everything need to be? Git has warts for sure, but this whole ideas guy no actual understanding of anything is how you get trainwrecks. There is no free lunch, and you're going to pay one way or another for not understanding the tools of the craft, and that not everything can be ridiculously simple.

But it's not that people don't grasp the concept of merge conflicts, it's just that the UX of git is bad.