Well the good thing about last week is that I helped my company get through their hurdles of getting their backend to work with their mobile apps. Though it's in the weekends, but hey it gets me paid.

I just hope that the PM would cut me some slack for not doing git commits properly. After all, we're not big in terms of company size, and if the PM is so anal about it, we can't move fast enough. As long as the PRs are reviewed and made sure that the web app works, nothing else matters.

@TheDane it's not hard. But when you're too focused on solving a problem and getting web apps to work in the shortest amount of time, how can you move fast?

@TheDane if you have ways, lemme know. I would like to learn and move on.

@TheDane he wants it to be even more granular. It can be done, but I had to move fast.

Sorry, but no. That's as bad as programmers who say they can't take the time to write comments because it prevents them from advancing.
If you don't want to commit your code, it means you don't care whether the fruit of your hard work will be preserved or not.
How hard is it to commit every once in a while? It's one command line! It's the pulling and pushing, and solving conflicts that takes time. Committing locally is for free. Just commit locally about every 30 min and push everything at the end of the day.

Huh? Unless your company has a policy that means committing "properly" is committing every other word you type, or writing a 2000 word essay in a commit log, then I really don't see the problem with committing little and often.

I find it makes me work *faster* generally, and it's a hell of a lot easier to track where it happened if something went wrong.