This blog contains interesting bits that cross my daily intake of information. While most successful blogs focus on a singular topic, I make no such promises. I promise only content that I either care about or find value in sharing.

Elsewhere

 

Poking the Box

All great programmers learn the same way. They poke the box. They code something and see what the computer does. They change it and see what the computer does. They repeat the process again and again until they figure out how the box works.

Godin, Seth (2011-03-01). Poke the Box (p. 10). The Domino Project. Kindle Edition.

Tools needed for success

More gold from Seth. The best AP teachers push some of these, but our nation needs more challenges with an explanation of how it is relevant.

I can’t wait to be a father for this reason - to be a teacher.

http://www.43folders.com/2011/04/22/cranking

This type of writing is inspiring. The weaving of details in and out to make a story come alive. The type of writing that leaves you disappointed at the end when you run out of words to read.

I’m afraid there isn’t one. I’m still naive enough to think that if I build a great product then everything else will take care of itself.

Souls

It’s so easy to get hung up on the itinerary, the features and the specs, but that’s not real, it’s actually pretty fuzzy stuff. The concrete impact of our lives and our work is the mark you make on other people. It might be a product you make or the way you look someone in the eye. It might be a powerful experience you have on a trip with your dad, or the way you keep a promise.

The experiences you create are the moments that define you. We’ll miss you when you’re gone, because we will always remember the mark you made on us.

There’s a sign on most squash courts encouraging players to wear only sneakers with non-marking soles. I’m not sure there’s such a thing. If you’re going to do anything worthy, you’re going to leave a mark.

Herding Racehorses, Racing Sheep

Process Improvement requires People Improvement

Hiring is Obsolete

People don’t buy version 1.0 of a product for a reason. I’m a big believer in continuously iterating until you make something excellent:

And then of course, big companies are bad at product development because they’re bad at everything. Everything happens slower in big companies than small ones, and product development is something that has to happen fast, because you have to go through a lot of iterations to get something good.

Played 0 times

Fantastic insights on The Talk Show with Dan Benjamin, John Gruber, and special guests Marco Arment and Craig Hockenberry. Some favorite points I noted down:

  • An App Store is like the checkout line at the supermarket. When the prices are low, there are a lot of impulse buys.
  • An App Store provides a friction-free purchasing experience.
  • For years, people working in the Windows XP enterprise have been taught not to install software. Having a trusted purchase, install, and use experience is very important to application developers.
  • The Mac App Store is similar to something like MacHeist, which bundles apps at a lower price to make up the profit in volume.
  • The Apple App Store contains 45 million credit cards (which, when combined with a friction free experience is great for developers).
  • The Mac App Store is not for current OS X developers. It’s designed for iOS App developers who are used to using the App Store to handle all of the painful logistics of selling products (payment gateways, etc.) to expand the trusted application purchase experience to consumers.

Re: Apple’s responsibility as a superpower

I couldn’t disagree more with @dhh on this one

Like 37Signals, Apple is an opinionated company and it reflects in their products. As many readers have remarked, 37S preaches this from their books, classes, conference appearances, and blog and make a pretty penny doing so. Apple takes risks and the public and blogosphere usually show animosity when the company takes sides on an issue.

With regard to Adobe and Flash, Apple made the decision to remove a single Adobe offering from their platform for a couple of likely reasons (1) the existing Flash player likely didn’t work on iOS (it doesn’t fully work on any phones yet), and (2) Flash will eat your battery and cause heat issues (ever hear the fan rev up when you’re watching a video – A mobile phone or tablet doesn’t have space for large fans and heat sinks). Apple is a company that takes a problem and solves it in a different way – whether you like it or not is your personal opinion. Take for example the removable battery problem. The core issue is that a battery doesn’t last long enough. What did Apple do to solve the problem? They made their electronics smaller so that a battery could encompass the majority of the device. The historic answer to the problem is to sell extra batteries to the consumer so they can swap them out. Now consumers have more charging logistics to deal with (can’t we have devices for grown-ups?). It’s an opinionated trade-off, and I feel strongly that people are happy in the long-term with long-lasting batteries. The same concepts apply for Flash – the core issue is to watch videos. How it’s done doesn’t matter to the user at large. Sure, some restaurants love to use Flash to show their delicious food with animations, but again, there is a modern solution for that – CSS3 Animations. Like the statistics show, web technologies are evolving at an incredibly rapid pace because of this singular decision and we all benefiting from it. Now we have highly optimized browsers and Microsoft has been forced to care.

One should be careful interpreting competition as unreasonable fighting. Motorola, HTC , Apple, and many other device manufacturers are simply doing what needs to be done to play defense in a the broken system of U.S. patents and position themselves to succeed.

With regard to Java, it’s on the outs regardless of whether Apple decides to spend a ton of time making platform applications look good on their OS (something Java was never good at). There is a reason many new languages (Scala, Groovy, Clojure, JRuby) are gaining popularity on the JVM – the cross platform nature of the JVM is great, but the Java language itself is dated and mired in its inability to innovate. I think 37S has proven this point in its use of Rails over Java.

I have no fear for the future when a company takes a core issue, is dissatisfied with the available solutions, and designs something that they believe is better. Isn’t this how 37Signals designs? Say “No” to the customer? Break it down to the fundamentals? Remove the cruft that adds no value?