crime
Traced in the summer skies
Yes, it was the hour when, a long time ago, I was perfectly content. What awaited me back then was always a night of easy, dreamless sleep. And yet something had changed, since it was back to my cell that I went to wait for the next day…as if familiar paths traced in summer skies could lead as easily to prison as to the sleep of the innocent.
Putting the streets to use
Tad Friend writes, if you build “nine hundred miles of sinuous highway and twenty-one thousand miles of tangled surface streets” in one city alone, then you’re going to find at least a few people who want to put those streets to use. This suggests that every city blooms with the kinds of crime most appropriate to its form.
Every heist is a counterdesign
Heists obsess people because of what they reveal about architecture’s peculiar power: the design of new ways of moving through the world. Every heist is thus just a counterdesign—a response to the original architect.
To commune with the space
...having realized long ago that the best way to commune with an architectural space was by breaking into it.
Bandits
A FilmA Burglar's Guide to the City
A Book by Geoff ManaughAuthorisation vs. Consent
An Article by Terence EdenI recently read this interesting, and distressing, story of a man who was drugged and robbed. A form of crime which has been going on for centuries. But the 21st Century twist is that the thieves forced him to transfer large sums of money via his phone's banking apps.
While under the influence, the victim used his usernames, passwords, PINs, and biometrics to send money to the criminal's accounts.
Is there a "technological" way to stop this? His banks initially refused to refund the stolen money. Only once the press stepped in did they relent. One bank, Revolut, said:
This was an unusual case where the payments were authorised by the customer but, as is now clear, without his consent.
Picking locks with audio technology
An ArticleThe series of audible, metallic clicks made as a key penetrates a lock can now be deciphered by signal processing software to reveal the precise shape of the sequence of ridges on the key's shaft. Knowing this, a working copy of it can then be 3D printed.
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.