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
The Fidelity Curve An Article by Ryan Singer m.signalvnoise.com 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 fidelityTime to build versus confidence gained prototypesinterfaces
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 Show image 0 Show image 1 Show image 2 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.