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 heart of systems engineering While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes. Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all. I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn What the problem isComplete and consistent requirements