Senior engineers are paid to get stuff done on time while following good practices, and be proactive and communicative (and not end up on Twitter for the entire

Senior engineers are paid to get stuff done on time while following good practices, and be proactive and communicative (and not end up on Twitter for the entire day because they couldn't figure out one project requirement by themselves, as many juniors do). Compared to a junior engineer, they have to get thrice more things right at the same time. Knowing a tool inside out can help with this, but it's not a requirement at all. It's just one of the, a-hem, tools in their box with which they can achieve efficiency. I am like many others in this thread. I don't care about GIT's "beautiful data model" one bit. I learned with time which commands are dangerous and I do due diligence to make triple sure I don't trip on them. With 2 exceptions for the last 10+ years (each took me half a day to fix) this has worked perfectly. It's quite OK to stick to what you know is safe and works well (and what pre-conditions have to be met so it works well). At this point if a customer comes around and asks me to use advanced GIT features I'll just bill them triple while telling them exactly why. I deliver, and at least 80% of the time I deliver on time, and 95% of the time with good practices and due diligence attached. How I use GIT is my business. I've been contacted by the next contractors no small amount of times and have eaten praise for how easy to track my project's change / commit history has been, too.