The Timeless Way of Building A Book by Christopher Alexander www.patternlanguage.com Mind of no mindThe quality without a nameAn objective matterBitternessThe most precious thing we ever have+27 More Some emptiness in usDeliberate actsNo kindpatternsof.designA Pattern LanguageNon-architectsThe Side View #17: Susan Ingham & Chris AndrewsThe usages of life architecturemakingbuildingurbanismbeautyconstructionzen
A Pattern Language A Book by Christopher Alexander, Murray Silverstein & Sara Ishikawa www.goodreads.com Its place in the web of nature9. Scattered Work21. Four-Story Limit51. Green Streets53. Main Gateways+27 More Deliberate actspatternsof.design125 Best Architecture BooksThe Timeless Way of BuildingThe design systems between usCollaborative Information Architecture at Scale architectureurbanismlifeconstruction
A City Is Not a Tree An Essay by Christopher Alexander www.patternlanguage.com Strands of lifeImpending destructionThe right overlapThe difficulty of designing complexityPolitical chains of influence+8 More Trees and graphsThe dishonest mask of pretended orderThe problem with treesBoth practical and aesthetic concerns citiesurbanismdesignarchitecturemath
Notes on the Synthesis of Form A Book by Christopher Alexander www.hup.harvard.edu I could do better than thatThis small internal quaverTheir wrongness is somehow more immediate mathdesignarchitectureformproblems
The Battle for the Life and Beauty of the Earth A Book by Christopher Alexander www.goodreads.com Two generating systemsTwo types of building productionSystem ASystem BThis has harmed modern society greatly+24 More What the prototype tells youOn the "Building" of Software and WebsitesBack to the Drawing BoardReading the landscape architectureurbanismbeautyconstruction
The Nature of Order A Book by Christopher Alexander www.natureoforder.com Levels of ScaleStrong CentersBoundariesAlternating RepetitionPositive Space+10 More Strength from both mass and form architectureurbanismgoodnessbeauty
Contrasting Concepts of Harmony in Architecture A Dialogue by Christopher Alexander & Peter Eisenman www.katarxis3.com The realm of feelingPanicThe pitched roofThe trick of little machinesMerely a building+2 More
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