Right now, the Pebble takes the lead over Android Wear, but it’s likely that far better things are right around the corner, and the smart move might just be to wait for those.

I’m not wearing my Pebble all of the time because of the way it looks. But when I don’t wear it, I’m missing notifications (I don’t feel my phone buzz when I’m wearing shorts instead of jeans). The iWatch can’t get here fast enough.

A great set of tips from the folks at Etsy about how to manage your calendar.

I can’t agree with this strongly enough:

When you die, it does not mean that you lose to cancer. You beat cancer by how you live, why you live, and in the manner in which you live.

A wonderful speech. I cried.

Also check out his follow-up post.

You can purchase Achieving Zen With Auto Layout today and get access to a PDF of the current state of the book, as well as a private GitHub repository where I am writing and storing all the sample code as I go. So far this has proven to be a wonderful way to write, because buyers of the book are able to provide direct feedback to me about the book so I can iron out any confusion or missing things I may not have thought of during my first draft.

I had a chance to talk with Justin about this approach the other day. I love it. I expect this type of interactive approach to creating technical books become more and more popular.

I bought the in-app purchase for Overcast and I’m linking to Marco’s post to support him because I enjoy the ATP podcast he runs along with Casey Liss and John Siracusa.

However, Overcast wasn’t a fit for me. I found the navigation to be awkward and the per-podcast playback settings nearly impossible to find (hint, click on the podcast logo on the left side of the player controls along the bottom of the screen to bring up the episode screen, then the playback settings for the podcast can be adjusted using the button/link in the bottom right corner). I’m sticking with Castro for now, but will be keeping an eye on Overcast.

I’m also not a huge fan of his approach to become an intermediary between the podcast providers and me. The Overcast service checks podcast feeds, and the Overcast client talks to the service – this is basically the model that Google Reader made popular for RSS feeds. I do understand how this can make checking for feeds more efficient on the client, but it introduces a single point of failure.

I’m not at the point where I’m willing to spend that much on headphones, but I’m glad others are doing the legwork for me.

I agree with most of this, but I get a lot of utility from seeing notifications on my wrist. Note that I already severely limit what notifications I receive, so when my wrist buzzes, it’s pretty much always for something I care about.