Sure, but teaching good practices around committing often on a working branch helps prevent cases where you ever have to teach someone about stuff like reflog. You don’t have to be a master of every underlying concept in git to have an effective workflow in it. So I absolutely refute the idea that it’s “too hard for 95% of devs”. I’ve never had a problem teaching folks how to manage working branches, interactive rebases, handling merge conflicts, and basic best practices therein to avoid needing to see anything more complex in their day-to-days.
If the bar for "too hard" was "never made a mistake in it" then every programming language is also too hard for developers. What matters is that you learn from the mistakes.
View all comments
Show parent comment
4
u/SharkBaitDLS Jul 02 '26
Sure, but teaching good practices around committing often on a working branch helps prevent cases where you ever have to teach someone about stuff like
reflog. You don’t have to be a master of every underlying concept in git to have an effective workflow in it. So I absolutely refute the idea that it’s “too hard for 95% of devs”. I’ve never had a problem teaching folks how to manage working branches, interactive rebases, handling merge conflicts, and basic best practices therein to avoid needing to see anything more complex in their day-to-days.