557 karma · joined November 10, 2009
I've also posted some of the scripts on github like this one to parse out iMessage/sms logs from an iphone backup. https://gist.github.com/jehiah/4437883
Is there an official way of measuring beard length?
My rough approach to post processing this data was to group by 6 minute intervals, and to drop any records where the computer was inactive for more than 120 seconds.
I've highlighted some last.fm data in a few of my previous annual reports, but it didn't make it this year (I Wasn't quite into new music enough recently for it to be interesting to me).
https://gist.github.com/4477040 is the cron script I use on a 10 min interval.
There might be other ways to do this now days, but i've used this successfully for a few years.
glad you enjoyed the report.
The transition from Carte Blanche to Burbon Coffee in the middle of the year is when @bitly's office moved, and my coffee habit followed.
The motivation for me is a way to learn about my year (not directly to change my actions), and part a fun exercise to get better at data processing, javascript, and UI Interaction/charting. I like the hard deadline that a personal annual report creates naturally (ie: it's no good if i release it in june).
Some of the other scripts just download data from foursquare's API, and post processing transaction download from Mint. Hopefully I'll have time to clean and post those scripts.
for the computer activity i took a snapshot every 30seconds of what program was active, and how long my laptop was active.
In the mean time, installing Go is pretty easy (you can use brew, or the official OSX package (assuming you are on OSX) http://golang.org/doc/install) and we've tried to leave clear steps for building NSQ here https://github.com/bitly/nsq/blob/master/INSTALLING.md (there really are very few dependencies other than go itself)
In terms of manual de-duping, we strive internally for idempotent message processing so it's fairly irrelevant, but to handle cases where it matters, all of our messages have unique id's added to them outside of NSQ.
The actual cases where messages are handled multiple times is limited to when a client disappeared during message processing (a hard restart) or it passed the allowable time window to respond and was given to another client.
If there are any specific numbers you are curious about, please ask.