Nice rundown by Justin. I’m still not using a “digital junk drawer” app – they all seem too laden with navigation to make getting to what I want efficient. I’m content with my NVAlt + Dropbox sync + Mobile apps and an “all text all the time” solution for now.

But some form of regular writing is one of the best ways to give yourself time for reflection and analysis.

This is the main reason I’ve been blogging for the last dozen years. I’ve also found that the benefits extend to coding – writing out what I need to clarifies it for me and helps me identify edge cases and additional things I need to consider. It gives me space to really think about the problem. I use Capsule to journal my coding.

If a cadet did something better than normal, his next attempt at the task would in all likelihood not be as good, whether or not he was praised. In the same way, if he performed unusually badly, his next attempt would probably be better, whether or not he was criticised. The trainer was attaching a causal interpretation to the fluctuations of a random process; simple regression to the mean.

(thanks Micah)

Sage advice from Sandy.

I’ll be here all week.

As a sweeping generalization, I think Americans focus way too much on the small picture instead of the big picture. An application of systems theory makes more sense to me.

Such a great presentation from Mike – I sent this to my team immediately after watching it. This is targeted at designers, but applicable to anyone in a services business or who works in a creative capacity.

This sort of entitlement crap really irks me. No one is making you speak at a conference; it’s a choice. Expenses covered or not is just something you need to factor in when agreeing to be a speaker.