Here’s the new hotness! Time Track now uses a single data file so it won’t junk up your hard drive with lots of dirty files on each run. It stores data for multiple projects including their time logs and total run times in a single file. I even got to use a hash for the very first time!
Adam helped me a lot with this refactoring because, honestly, I still suck and he’s the shit at refactoring, considering that’s what he does all day long (all night long too)! If you try to run the code make sure to enter the same project name on each iteration or you’ll just be adding times to new projects. The next step is to give the user an option to select from a project that’s already been created, but for now in order to get that effect you just have to type in the same project name each time. 
Monday, 8. December 2008
Random thought: You might just link to your GitHub repo at the bottom of all your Time Track posts. Especially as your code gets longer and more complex, it will be hard for readers (or, well, me, at any rate) to read the whole thing in a meaningful way.
Then, if there’s some specific section or method or whatever that you wanted to highlight, you can still use gist to show it off.
Monday, 8. December 2008
Ben, thanks for the fantastic advice!
I’ll be sure to do that since yes, displaying all the code each time can be overwhelming!