construction
Stacking the rails
Stage sets for the eye
With the loss of tactility, measures and details crafted for the human body – and particularly for the hand – architectural structures become repulsively flat, sharp-edged, immaterial and unreal. The detachment of construction from the realities of matter and craft further turns architecture into stage sets for the eye, into a scenography devoid of the authenticity of matter and construction. The sense of 'aura', the authority of presence, that Walter Benjamin regards as a necessary quality for an authentic piece of art, has been lost.
To build a folly
To build a folly is essentially to do something a second time, something at an inopportune moment. That something is always the memory of something forgotten, about which we can paradoxically say "There it is again."
Follies were misunderstood, purposeless constructions. They were often only small, extravagant gestures in a garden, easily whisking off the imagination to distant lands, a sort of time capsule built to awaken the memory and induce surprise in passers-by. They marked locations, organized secondary paths in a park, or simply predicted the arrival of better times—a demarcation, a sacred spot, a mysterious trail, a hill whose tragic rocky nature begged for a tower, a party, or the arrival of summer.
Errors & Crimes
"A builder who hides any part of the building frame, abandons the only permissible and, at the same time, the most beautiful embellishment of architecture. The one that hides a loadbearing column makes an error. The one who builds a false column commits a crime."
— Auguste Perret
The Timeless Way of Building
A Book by Christopher Alexander- Mind of no mind
- The quality without a name
- An objective matter
- Bitterness
- The most precious thing we ever have
A Pattern Language
- Its place in the web of nature
- 9. Scattered Work
- 21. Four-Story Limit
- 51. Green Streets
- 53. Main Gateways
The Battle for the Life and Beauty of the Earth
A Book by Christopher Alexander- Two generating systems
- Two types of building production
- System A
- System B
- This has harmed modern society greatly
On the "Building" of Software and Websites
An Essay by Dorian TaylorI’m beginning to suspect that software, and more conspicuously the Web, is fundamentally the wrong shape for the archetype of the construction project.
The small web is beautiful
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?
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.
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”.
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.