112. Entrance Transition Problem: Buildings, and especially houses, with a graceful transition between the street and the inside, are more tranquil than those which open directly off the street. Solution: Make a transition space between the street and the front door. Bring the path which connects street and entrance through this transition space, and mark it with a change of light, a change of sound, a change of direction, a change of surface, a change of level, perhaps by gateways which make a change of enclosure, and above all with a change of view. Christopher Alexander, Murray Silverstein & Sara Ishikawa, A Pattern Language Walking through doorways causes forgetting53. Main GatewaysAt the Green MosqueThe wind's pulling us inOne who has trodden this garden pathA more spiritual place transitionsdoors
The door handle is the handshake of a building Juhani Pallasmaa, The Eyes of the Skin: Architecture and the Senses What is this static modernism? metaphordoorsinteraction
What is this static modernism? Why can't office buildings use doorknobs that are truly knob-like in shape? What is this static modernism that architects of the second tier have imposed on us: steel half-U handles or lathed objects shaped like superdomes, instead of brass, porcelain, or glass knobs? The upstairs doorknobs in the house I grew up in were made of faceted glass. As you extended your fingers to open a door, a cloud of flesh-color would diffuse into the glass from the opposite direction. The knobs were loosely seated in their latch mechanism, and heavy, and the combination of solidity and laxness made for a multiply staged experience as you turned the knob: a smoothness that held intermediary tumbleral fallings-into-position. Few American products recently have been able to capture that same knuckly, orthopedic quality. Nicholson Baker, The Mezzanine The door handle is the handshake of a building modernismdoorstouchobjects
Always start at the doorstep If you are having trouble knowing where to start, always start at the doorstep. Bill Mollison, Introduction to Permaculture doorswisdom
At the Green Mosque In Broussa in Asia Minor, at the Green Mosque, you enter by a little doorway of normal human height; a quite small vestibule produces in you the necessary change of scale so that you may appreciate, as against the dimensions of the street and the spot you come from, the dimensions with which is is intended to impress you. Then you can feel the noble size of the mosque and your eyes can take its measure. You are in a great white marble space filled with light. Beyond you can see a second similar space of the same dimensions, but in half-light and raised on several steps (repetition in a minor key); on each side still a smaller space in subdued light; turning round, you have two very small spaces in shade. From full light to shade, a rhythm. Tiny doors and enormous bays. You are captured, you have lost the sense of the common scale. You are enthralled by a sensorial rhythm (light and volume) and by an able use of scale and measure, into a world of its own which tells you what it set out to tell you. Le Corbusier, Towards a New Architecture 112. Entrance Transition doors
Open doors, open minds I suspect the open mind leads to the open door, and the open door tends to lead to the open mind; they reinforce each other. Richard Hamming, You and Your Research doors
Walking through doorways causes forgetting A Research Paper news.nd.edu Entering or exiting through a doorway serves as an ‘event boundary’ in the mind, which separates episodes of activity and files them away. Recalling the decision or activity that was made in a different room is difficult because it has been compartmentalized. 112. Entrance Transition memoryarchitecturewalkingexitsdoors
The small web is beautiful An Essay by Ben Hoyt benhoyt.com I believe that small websites are compelling aesthetically, but are also important to help us resist selling our souls to large tech companies. In this essay I present a vision for the “small web” as well as the small software and architectures that power it. Why aim small?Features and complexitySolving the problem of software bloatRaw size isn't enough Rediscovering the Small Web wwwmicrosites
Why aim small? Why aim small in this era of fast computers with plenty of RAM? A number of reasons, but the ones that are most important to me are: Fewer moving parts. It’s easier to create more robust systems and to fix things when they do go wrong. Small software is faster. Fewer bits to download and clog your computer’s memory. Reduced power consumption. This is important on a “save the planet” scale, but also on the very local scale of increasing the battery life of your phone and laptop. The light, frugal aesthetic. That’s personal, I know, but as you’ll see, I’m not alone. performancesystemsconservation
Features and complexity Niklaus Wirth of Pascal fame wrote a famous paper in 1995 called A Plea for Lean Software. His take is that “a primary cause for the complexity is that software vendors uncritically adopt almost any feature that users want”, and “when a system’s power is measured by the number of its features, quantity becomes more important than quality”. A Plea for Lean SoftwareSpeed is a featureRequirements proliferation featurescomplexity
Solving the problem of software bloat But instead of just complaining, how do we actually solve this problem? Concretely, I think we need to start doing the following: Care about size: this sounds obvious, but things only change when people think they’re important. Measure: both your executable’s size, and your program’s memory usage. You may want to measure over time, and make it a blocking issue if the measurements grow more than x% in a release. Or you could hold a memory-reduction sprint every so often. Language: choose a language that has a chance. Remove: cut down your feature set. Aim for a small number of high-quality features. My car can’t fly or float, and that’s okay – it drives well. Say no to new features: unless they really fit your philosophy, or add more than they cost over the lifetime of your project. Dependencies: understand the size and complexity of each dependency you pull in. Use only built-in libraries if you can.
Raw size isn't enough A few months ago there was a sequence of posts to Hacker News about various “clubs” you could post your small website on: the 1MB Club, 512KB Club, 250KB Club, and even the 10KB Club. I think those are a fun indicator of renewed interested in minimalism, but I will say that raw size isn’t enough – a 2KB site with no real content isn’t much good, and a page with 512KB of very slow JavaScript is worse than a snappy site with 4MB of well-chosen images. ...[Instead, it's about] an “ethos of small”. It’s caring about the users of your site: that your pages download fast, are easy to read, have interesting content, and don’t load scads of JavaScript for Google or Facebook’s trackers. minimalismcontentsize