3 ms·
> Keep a record of "stupid errors that took me more than 1 hour to solve" I’ve been doing this for the last three years, but electronically, and it’s amazing.
by physicles 7y ago
> Keep a record of "stupid errors that took me more than 1 hour to solve"
I’ve been doing this for the last three years, but electronically, and it’s amazing. In my home folder there’s a giant text file that’s like my personal log file. It gets a new line at least once an hour, when cron pops up a box and I type in what I’m working on. And for those times when I’m working on stuff that’s perplexing, I write to it as a stream of consciousness — “tried this, didn’t work” “wonder if it could be due to xyz” “yep, that was it.”
I’ve used it a few dozen times to either look up how I solved a weird problem, or why I decided to do something a certain way. I’ve even built pie charts of how I spent my time in the last quarter by sampling it Monte Carlo style.
- stormthebeach 7y agoDo you have this cron script hosted anywhere?
- AnimalMuppet 7y agoI keep a log of "stuff I had to look up how to do". Mine isn't "stupid errors" so much as stuff like "what are the flags to get the compiler to show you the assembly code it produces".
- unimpressive 7y agoReminds me of: http://messymatters.com/tagtime/ http://messymatters.com/tagtime/ Which is a pretty well formed solution in this vein, unfortunately written in Perl.
- dsmithn 7y agoany experience with newtagtime.com ?