3 ms·
assuming there's code involved, you may be able to jog your memory some simply by reviewing the commit logs and commits themselves. It's a hard balance to find
by mgkimsal 15y ago
assuming there's code involved, you may be able to jog your memory some simply by reviewing the commit logs and commits themselves.
It's a hard balance to find - documenting what you're doing with enough detail to help justify your expenses, while at the same time not losing the flow of the moment to actually get stuff done. I can often lose a couple hours of time working on an item - tracking down bugs in other peoples' code is really time consuming, and I'd rather get it right than get it logged, to coin a phrase.
- aantix 15y agoI've written a gem that cross references your computer activity auto-logged with TimeSink ( http://manytricks.com/timesink/ http://manytricks.com/timesink/ ) with your git commits, and generates a line item pdf invoice. https://github.com/aantix/big_bucks_no_whammies https://github.com/aantix/big_bucks_no_whammies Here's a sample invoice : https://github.com/aantix/big_bucks_no_whammies/blob/master/sample_report.pdf?raw=true https://github.com/aantix/big_bucks_no_whammies/blob/master/...