I loved this concept. I understand that practically we generally first write the whole code and then think about commits. By my manager always says "Coding is t

I loved this concept. I understand that practically we generally first write the whole code and then think about commits. By my manager always says "Coding is the last and easiest part of the job. Hard and creamy part of the job is to think about solutions and choose the best one among them." And this approach (given in dev.to) of thinking of the commit messages before actually coding gives a framework to that thought. That means before hand one is clear what to do (definitely during actual implementation we will find some extra nit-picks here and there and will add some extra code). So with this style one can follow the style :- Jot down the requirement/problem ==> Think of all solutions for the problem ==> Evaluate solutions ==> Choose best one ==> Jot down commit messages before hand ==> Implement solution ==> Use "git add -p" to separate logical units of your commit as per your commit messages already prepared ==> Tada !!