The Illustrated Primer

Tag: best practices

Just Say No to Features

To hit the market early and within budget, your feature development strategy must focus on creating the bare essential functionality. So in this vein, you should make it prove itself to be a “worthy survivor”. Your features need to be tough, resilient, and lean. I have come to embrace the U.S Navy SEAL’s “hell week” screening approach before letting any one of them into my development cycle.

Read More »

To Make Errors is Human, to Handle Them is Divine

Its not enough to capture and display errors. Real quality of service goes beyond just acknowledging your application’s faults. My rule of thumb is that there is no such thing as an “informative error message”. A good error is one that has been eliminated through error-handling code and product design.

Read More »