You find reasons to keep living Life is suffering. It is hard. The world is cursed. But still, you find reasons to keep living. Hayao Miyazaki, Princess Mononoke Prometheus sufferinghopelife
The modern infrastructural ideal The form and possibility of the "modern infrastructural ideal" is increasingly under threat, as cracks (sometimes literal ones) show up in our bridges, our highways, our airports, and the nets of our social welfare systems. For these and other reasons, broken world thinking asserts that breakdown, dissolution, and change, rather than innovation, development, or design as conventionally practices and thought about are the key themes and problems facing new media and technology scholarship today. Attached to this, however, comes a second and more hopeful approach: namely, a deep wonder and appreciation for the ongoing activities by which stability (such as it is) is maintained, the subtle arts of repair by which rich and robust lives are sustained against the weight of centrifugal odds, and how sociotechnical forms and infrastructures, large and small, get not only broken but restored, one not-so-metaphoric brick at a time. Steven J. Jackson, Rethinking Repair How Buildings Learn infrastructurehope
500 Days of Summer A Film by Marc Webb, Scott Neustadter & Michael H. Weber www.imdb.com I think you should look againIt just wasn't me you were right about lovemelancholyhope
Finding nourishment vs. identifying poison An Article by Austin Kleon & Olivia Laing austinkleon.com A useful analogy for what [Sedgwick] calls ‘reparative reading’ is to be fundamentally more invested in finding nourishment than identifying poison. This doesn’t mean being naive or undeceived, unaware of crisis or undamaged by oppression. What it does mean is being driven to find or invent something new and sustaining out of inimical environments. I would like to adopt that line as a mission statement: “To be fundamentally more invested in finding nourishment rather than identify poison.” Because you can identify all the poison you want, but if you don’t find nourishment, you’ll starve to death. Poison sniffers hopereadinggoodness
A little act of hope A Fragment by Jeremy Keith adactio.com As I scroll down my “on this day” page, I come across more and more dead links that have been snapped off from the fabric of the web. If I stop and think about it, it can get quite dispiriting. Why bother making hyperlinks at all? It’s only a matter of time until those links break. In a sense, every hyperlink on the World Wide Web is little act of hope. Even though I know that when I link to something, it probably won’t last, I still harbour that hope. If hyperlinks are built on hope, and the web is made of hyperlinks, then in a way, the World Wide Web is quite literally made out of hope. I like that. And thus the heart will break hypermediahope
The Fidelity Curve An Article by Ryan Singer m.signalvnoise.com How do we choose which level of fidelity is appropriate for a project? I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing. I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing. Four levels of fidelityTime to build versus confidence gained prototypesinterfaces
Four levels of fidelity Suppose we have four levels of fidelity… Rough sketch (on paper or an iPad) Static mock-up (eg. Photoshop or Sketch) Interactive mock-up (eg. Framer, InVision) Working code prototype (HTML/CSS, iOS views) Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained Show image 0 Show image 1 Show image 2 Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it. Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.