Hacker News Reader

Hacker News

Comment by osigurdson | Hacker News Reader

Full thread

osigurdson

I'm so used to whatever flawed abstractions I have in my head that I fear learning the truth could be detrimental.

View on HN

This, but I compartmentalize.

If I own the project then my heresies are dogma.

If you own the project I allow your heresies to be dogma.

This is a phenomenal outlook, actually. Joining and working with other projects is then like attending an interfaith group comprised entirely of heretics arguing about the right way to disagree.

Since reality doesn't care about this, wrong dogma can still bite you if it's not real even if non other people are involved

not if 'never rebase, it is a trick of the devil' is part of the Dogma and adhered to.

I'm being a little silly; but a team I worked on moved from P4 -> Git. It was an older develoepr base, so they wrote 1:1 translation wrappers for most P4 commands to git, and forced all developers to use them. Banning Rebase (in private branches, not even main) was one of the requirements to not break the wrappers.

While the idea of writing such wrappers is pretty nice, they still missed out. Rebasing is incredibly useful.

My general consensus on the practice is that it prevents the developers from learning Git. Short-term gain for long-term ignorance. I'm much more a fan of "Learn the tool upfront and reap the benefits", don't handicap the organization from the start.

Interesting, one of my personal dogmas is "never merge, always rebase".

I can't handle my branches bifurcating into the past.

If only you could rm -rF && git clone your mind.

"Empty your cup", as they say.

Just this morning, I spent over an hour trying to fix things after I made a git mistake. I ended up having to check out a fresh copy and manually reapply my changes.

This sort of thing is why I both fear and hate git.

I'll have to check this game out. My flawed abstractions clearly cause me issues. Maybe it could help.

Reply on news.ycombinator.com