Git Etiquette: Make your coworkers happy, be ready for CD and grow as a developer!

Let me show you on a real-life example why the way you use git makes a difference. This is not your standard git tutorial video. In fact I won't be using the git command line tool once. Instead this is about the mindset behind using git. How should you structure your commits? What makes a good commit? What is a good commit message? And most importantly: Why should I care? I'll try to explain to you why I believe for someone to be considered a senior developer they must be able to make great commits!

[@ianpan0102]

Nice Video! May I know what **Window Manager** you are using on macOS?

[@norm1124]

Do you have a script to reproduce your lovely Shell Look & Feel?
Thanks for the great videos.

[@NavyaTeja7]

Yes, of course I would like to see some react videos....may be like....one on redux, one on duck pattern something like this.

[@FalconFetus8]

So you want me to make small, frequent commits, AND write a long motivation for each one? Sorry, but if I did that I'd be spending more time writing commit messages than changing code.

[@kubucation]

It's less about the length of the motivation than about stopping for a second at commit time and thinking "Did I change anything that's not immediately clear and would benefit from additional explanation?". Writing that down in one sentence is absolutely fine and won't take more than 30s. So let's say you frequently commit, even at the rate of 10 per day, that's 300s or 5min. I don't think a "loss" of 5min per workday will make a big difference in productivity.