> there should be a comment in the code explaining the thought process Totally agree. Unofortunately, a descriptive git commit the best you can require without

> there should be a comment in the code explaining the thought process Totally agree. Unofortunately, a descriptive git commit the best you can require without starting a religious war in the team. You won't believe how many developers zealously subscribe to the "no comments needed - good code is self-explanatory" crap. Or throw in the "comments will quickly become outdated" excuse.