Upstream Color Original Soundtrack Leaves Expanded May Be Prevailing Blue Mixed With Yellow Of The Sand I Used To Wonder At The Halo Of Light Around My Shadow And Would Fancy Myself One Of The Elect Fearing That They Would Be Light-headed For Want Of Food And Also Sleep Stirring Them Up As The Keeper Of A Menagerie His Wild Beasts The Finest Qualities Of Our Nature Like The Bloom On Fruits Can Be Preserved Perhaps The Wildest Sound That Is Ever Heard Here Making The Woods Ring Far And Wide I Love To Be Alone A Young Forest Growing Up Under Your Meadows Their Roots Reaching Quite Under The House The Rays Which Stream Through The Shutter Will Be No Longer Remembered When The Shutter Is Wholly Removed After Soaking Two Years And Then Lying High Six Months It Was Perfectly Sound Though Waterlogged Past Drying The Sun Is But A Morning Star A Low And Distant Sound Gradually Swelling And Increasing As If It Would Have A Universal And Memorable Ending A Sullen Rush And Roar Shane Carruth, Upstream Color www.discogs.com WaldenI love to be alone euphonynaturelonelinessmelancholysoundending
Upstream Color A Film by Shane Carruth www.imdb.com The same material as the sunWhen it goes wrongUpstream Color Original Soundtrack WaldenExtract (n)Authorisation vs. Consent connectioncycleslove
Primer A Film by Shane Carruth www.imdb.com A normal wooden pencilSomething moreAt the top of the pageParanoiaHe had but to speak+1 More timetechnologyexperiments
everything & everything & everything A Video by Shane Carruth www.youtube.com The oppressively vapid life of Morgan is forever transformed when a mystical blue pyramid - that inexplicably produces doorknobs - appears in his apartment. What follows is a tale of greed and loss as Morgan builds an impossible, absurd corporate empire of doorknobs. surrealism
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