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.
Beyond Artboards
The Pursuit of Lossless Design-Development Handoffs.
Can't developers just see?
We designers love artboards. From rough UI sketches to high fidelity mockups, we see ourselves as visual artists expressing ideas on artboards that have a pre-defined width and height. To start a new project, we declare the size of the artboard in the first step.
What about responsive design? Not a problem! We diligently design on three artboards — one for mobile, one for tablet, and one for desktop — with content elegantly adapting, scaling, reflowing, reordering, and reprioritizing. We proudly hand off the artboards to developers while patting ourselves on the back: this is how responsive design should be done.
After weeks of arduous engineering, the product finally comes out. We find, to our great dismay, that some copy is hanging off the grid, the focal point of the hero image has been cropped out, the font sizes don’t even come close to the type ramp. What went wrong? Can’t the developers just see everything on all those artboards?
Nope.
We are the ones who paved the path
No matter how many screen sizes our artboards account for, some user’s browser will break loose from our prescription. With users resizing, rotating, and zooming the screen, new devices stretching, squashing, curving, and cutting (e.g. the speaker area in iPhone X) the screen, the sizes become infinite. Good luck making an artboard for each one of them.
Artboards are a lossy format. Using artboards in a handoff is a lossy process. When we pitch a finite number of plans against an infinite number of situations. We inevitably get in-betweens. Once there are in-betweens, there are unknowns. Once there are unknowns there is guesswork. Once there is guesswork, there are surprises. Engineers take the path of least resistance. We are ones who paved the path.
Until we get there
- As a designer, learn writing HTML, or better still, semantic HTML. If coding up the entire design is too hard, try coding up one component at a time, and not worrying about CSS. The HTML alone will prove invaluable for developers to understand the content structure. In addition, you are forced to optimize the information architecture as you work out the code from content.
- If coding by yourself is out of the question, pair up with the engineer who will receive the design. Work closely with him or her to prototype the design, validate responsive behaviors, and obtain feedback on the feasibility. Don’t call it an iteration until the design has seen played with in code.
- As a manager for large enterprise, co-locate your designers and developers, encourage interdisciplinary learning, understand that each minute spent on coding before the handoff translates to ten minutes saved from changing and fixing issues after the handoff.
- As a stakeholder in the handoff meeting, give the designer a thumbs-up when he or she demos live code running in browsers in place of mockups on artboards. That’s a design champion you are looking at.