The drift The Situationists were also practitioners of a special urban-analytic walking style, the dérive—the “drift”—which Debord described as “a technique of transient passage through varied ambiences. The dérive entails playful-constructive behavior and awareness of psychogeographical effects; which completely distinguishes it from the classical notions of the journey and the stroll.” “In a dérive,” Debord deadpans, “one or more persons during a certain period drop their usual motives for movement and action, their relations, their work and leisure activities, and let themselves be drawn by the attractions of the terrain and the encounters they find there." The dérive joins the free association of surrealism, the LSD of hippiedom, and cinematic montage as tactics for overcoming the fixity of received ideas of order and logic. By putting progress through the city into a state of constant indeterminacy, it represents a schooled “style” of being lost. Michael Sorkin, 20 Minutes in Manhattan PsychogeographyRaindrops leaving an erratic trail psychologymovement
The axis of movement Moving in the city means constantly changing the axis of movement. In general, lateral movement is confined to a single plane, what’s called grade, the ground level. Because circulation in multistory buildings is fundamentally one way—which is to say from the bottom up—the condition at the top is invariably different from that at the bottom. Rooftop circulation is the domain of Fantômas, of cat burglars and fleeing criminals, of lovers, and of those acrobatic enough to negotiate the gaps between buildings. Michael Sorkin, 20 Minutes in Manhattan A Burglar's Guide to the City movement
Beyond Artboards An Essay by Chuánqí Sun medium.com The Pursuit of Lossless Design-Development Handoffs. Can't developers just see?We are the ones who paved the pathUntil we get there processinterfacesdesign
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. Start drawing, then put the box around it
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. gridless.designChanging Our Development Mindset
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. html