3 ms·
Same, devs overthink it. Others obsess over history, but personally didn’t find it worth the effort. We look back maybe twice a year, typically fixing issues
by mixmastamyk 3y ago
Same, devs overthink it.
Others obsess over history, but personally didn’t find it worth the effort. We look back maybe twice a year, typically fixing issues moving forward.
- devjab 3y agoI guess it does depend on the size of your commits. Ours being relatively small (one work item) we still have the history, while devs getting the freedom to not have to make every commit meaningful.
- sureglymop 3y agoWhat's helped me much more lately is undotree for vim [1]. It basically logs every single time a file is saved. Its much more useful because commits have to be made by humans and they may not do it often (and usually there is an incentive for "clean or working commits"). There have been many times where I went back to copy something from the undotree. [1]: https://github.com/mbbill/undotree https://github.com/mbbill/undotree