Hacker News Reader

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.

Reply on news.ycombinator.com