I’m gonna be completely honest. I don’t truly get all the inner working of git. I’m a senior DevOps Engineer and been using git for a decade, but is git is simular to sed or awk for me. I know how to do what I want really well but when shit goes wrong, I’m flying by the seat of my pants.

A lot of times, I just know what to do to fix things because it’s rote memory with substitutions. But if you needed me to explain upstreams and rebases in actual detail, I’d be in trouble. But it rarely becomes an actual problem to the level where I’ll dedicate time to learning all the advanced stuff.

That said, I’ve learnt that most senior people also just pretend they get it all but instead are just relying on rote memorization and basic concepts. Anyone else here in the same camp of being a fraud with git?

In defense of those startups, I’m sure most of are doing it because theyve got organizational PTSD from beeing places be too fucked to be able to update their architecture rather than just overeagerness.

Probably some truth there. It’s probably a bit of feeling defensive as well

Sorry if I was too froggy

Decision paralysis is real even for stupid things. Like, “what are the implications if I pick the wrong instance?” Was something that made me put off finishing signing up for mastodon and I’m not embarrassed to admit it. Acting like it’s trivial isn’t helpful to anyone even if it was trivial or you