emptiness
Occupied by a void
Roland Barthes wrote that the centre of Tokyo is occupied by a void...it is a quiet forest that lies at Tokyo's heart.
...The centre of Tokyo is certainly a void, but one that is protected by a circular train line, the Yamanote, which forms a 40-km (25-mile) loop around it. It seems to me that this ring of steel emphasizes the importance of the void, and the depth of its significance.
Names vs. The Nothing
This is the first site along the tour. In here we have a void. I remember the building that used to stand here, it was painted blue. Passing through it, you can imagine how us, as ghosts – should the building be standing here – would have to actually be invisible to pass through these walls and now it’s the reverse. The building is the ghost and we’re passing through these walls.
Erased de Kooning Drawing
Once, Robert Rauschenberg erased most of a drawing by Willem de Kooning, and then named it Erased de Kooning Drawing.
I am in no way certain what this is connected to either, but I suspect it is connected to more than I once believed it to be connected to.
Most important of all are the pauses
Japanese music is above all a music of reticence, of atmosphere. When recorded, or amplified by a loudspeaker, the greater part of its charm is lost. In conversation, too, we prefer the soft voice, the understatement. Most important of all are the pauses. Yet the phonograph and radio render these moments of silence utterly lifeless. And so we distort the arts themselves to curry favor for them with the machines.
Empty rooms
A Quote by Bruce NaumanI don't think empty rooms are ever really empty. I think we subconsciously put our emotions into them.
The Fidelity Curve
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 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
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.