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
Figma's Engineering Values: Craftsmanship An Article www.figma.com Craftsmanship is about thoughtfulness and care in the work we do. It means being deliberate about what we build and how possible it will be to maintain and extend in the future. A solution that will require revisiting in a month — because it’s not scaling, because it has a ton of bugs, because it doesn’t support all the use cases it needs to — is not useful to us and ultimately will generate pain for our users. What we trade off by living this value is (sometimes) day-to-day speed. It’s easy to imagine an engineering team that emphasizes moving fast over keeping things stable and bug-free -- like a team building a product that isn’t responsible for important user data and doesn’t support anyone’s livelihood. But given the role the Figma product plays in the lives of our users, we feel it’s worth it to ensure we hold a high quality bar for them. And in the long run, being thoughtful about how we build often reduces the complexity of ongoing development and new features regardless. craftsoftwarequality