Misinterpretation as inspiration A lot of people think dreams and drugs involve some magical inspiration. I think otherwise. I rarely get inspired by dreams or drugs, but I have my own secret source of inspiration: mishearing other people. Somebody says something, I misinterpret it, and the misinterpretation is quite interesting – more interesting than anything I would have come up with on my own if asked to generate an interesting idea. Maybe it’s a clever joke or turn of phrase. Maybe it’s a neat idea. Sometimes I misunderstand people’s entire positions, and end up with positions much more interesting than the ones they were trying to push. Scott Alexander, Negative Creativity slatestarcodex.com Mondegreen mistakesinterestdrugsdreamscreativitymondegreens
Poetic drugs In the final chapters Bachelard lets slip (a confession really) how if he "were a psychiatrist," he would recommend a poem by Baudelaire to treat "anguish." His squabble then is not with the purpose but rather the approach of a still-young profession. And of course, why not treat the power of great poems as something akin to "virtual 'drugs'"? Mark Z. Danielewski, The Poetics of Space psychologypoetrypaindrugs
Doubling Obetrolling didn't make me self-conscious. But it did make me much more self-aware. If I was in a room, and had taken an Obetrol or two with a glass of water and they'd taken effect, I was now not only in the room, but I was aware that I was in the room. In fact, I remember I would often think, or say to myself, quietly but very clearly, 'I am in this room.' It's difficult to explain this. At the time, I called it 'doubling', but I'm still not entirely sure what I meant by this, nor why it seemed so profound and cool to not only be in a room but be totally aware that I was in the room. David Foster Wallace, The Pale King drugsattention
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.