I’ve been trying a number of techniques to reduce distractions and give myself larger blocks of time to actually create. My biggest concern is making sure I’m not blocking a colleague if they are waiting on a response from me.

I love posts like this.

We’ve talked a ton about different approaches to building for a Retina web at Crowd Favorite. We’re experimenting a bit with different approaches in our own site redesign.

I’m not in Shawn’s league as a photographer, but I miss playing at it. If only there was more time… this kit sounds intriguing.

I pretty much concur with Rafe on the use of comments and documentation. Ideally you have:

• an architecture outline/overview – this helps you understand how decisions are approached
• a few code comments – these help bring clarity to any code that isn’t obvious
• developer journals – where notes, ideas, casual decisions, code experiments and other odds and ends get captured

I think developer journals are underrated and I’m working to fix that.

If you are merely a broker for the content you provide, it’s easy for your service to lose signifigant value through something like this (while a rival gains value). Interestingly, Netflix seems to be taking steps to mitigate this. I don’t expect Amazon to follow suit into the content creation space though.

I had a soundtrack of Soul Man playing in my head as I read this. You should too.