The getaway to end all getaways Any attempt to track down the perfect getaway is made all the more complex because almost everything we know about burglary—including how they did (or did not) get away—comes from the burglars we’ve caught. As sociologist R. I. Mawby pithily phrases this dilemma, “Known burglars are unrepresentative of burglars in general.” Great methodological despair is hidden in such a comment. Studying burglary is thus a strangely Heisenbergian undertaking, riddled with uncertainty and distorted by moving data points. The getaway to end all getaways—the one that leaves us all scratching our heads—to no small extent remains impossible to study. Geoff Manaugh, A Burglar's Guide to the City failure
The Evolution of Useful Things A Book by Henry Petroski Here, then, is the central idea: the form of made things is always subject to change in response to their real or perceived shortcomings, their failures to function properly. This principle governs all invention, innovation, ingenuity. Spike and sponShaped and reshapedForm follows failureTheir wrongness is somehow more immediateA small corner of the world of things+23 More The evolution of devices formfunctioninventionprogressfailure
My Anti-Resumé An Article by Monica Byrne monicacatherine.com A couple years ago I was having dinner with a playwright, Bekah Brunstetter, and her director David Shmidt Chapman. We talked about how rejection is just part of the landscape for all beginning artists, no matter how talented or hardworking they might be or how successful they might appear. David said he’d love to publish his “anti-résumé” someday—a list of all the things he didn’t get. Spreadsheet Portfolios for UX Designers workfailure
The value-destroying effect of arbitrary date pressure on code An Article by Gandalf Hudlow iism.org The mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™! What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™. Driving engineers to an arbitrary date is a value destroying mistake agileplanningqualitydiscovery