Geometry
Isometry
A Website by Nick TrombleyLittle Blank Riding Hood
As a student at Chouinard, Larry Bell also started as a painter. His early canvases features simple shapes rendered in gestural strokes...From there he started eliminating the texture of the strokes, applying opaque color (thin Liquitex paint) to unprimed canvas, masking off shapes to create straight-edged parallelograms. An example of these works is Little Blank Riding Hood, whose top left and bottom right corners are clipped, suggesting an isometric projection of a three-dimensional form.
A rhombic geometry
The logo consists of a rhombic geometry which was inspired by Morioka’s drawing which he brought to the first meeting with Takram. During the process of design development, the team explored many different shapes and motifs other than the rhombic, but in the end came back to the very origin. In fact, the rhombic shape embraces two meanings, “an open single book” and “a single small room”. The first message was the vision team shared through the design process, and the second message was later proposed by Takram in order to make the geometry more connected to the character of the space, which Morioka often emphasised unconsciously.
1/3 House
Rever & Drage Architects.
Pylons
Not all the towers along a transmission line are identical. Look closely at a tower where the line makes a sharp turn and you will likely find it is wider and beefier than other towers along the route. The added strength and weight are needed to resist the unbalanced pull of the conductors, which might overturn an ordinary tower. These special towers are called deviation or angle towers.
The transmission-line tower everybody knows is an Erector Set latticework of steel girders and diagonal braces. The techniques for designing and building these towers are the same ones used in constructing steel bridge trusses or crane booms. The individual pieces can be made cheaply from rolled steel and then bolted together on the site. This last point is more important than it might seem: transporting a fully assembled tower 100 feet tall is an awkward and expensive business.
Authentic architectural experiences
Authentic architectural experiences consist of approaching or confronting a building, rather than the formal apprehension of a facade; of the act of entering, and not simply the visual design of the door; of looking in or out through a window, rather than the window itself as a material object; or of occupying the sphere of warmth, rather than the fireplace as an object of visual design.
Architectural space is lived space rather than physical space, and lived space always transcends geometry and measurability.
A World Where Things Only Almost Meet
Recall that great line from Umberto Eco’s novel The Name of the Rose
How beautiful the world would be if there were a procedure for moving through labyrinths.
Only, here, it’s some lonely postal worker—or a geography Ph.D. driven mad by student debt—out mapping the frayed edges of the world, wearily noting every new dead-end and cul-de-sac in a gridded notebook, diagramming loops, sketching labyrinths and mazes, driving empty streets all day on a quest for something undefinable, some answer to why the world’s patterns have gone so wrong. A self-diverging world, where things only almost meet.
Rearranged
Put together with odd bits of the useless Clarice, a survivors’ Clarice was taking shape, all huts and hovels, festering sewers, rabbit cages. And yet, almost nothing was lost of Clarice’s former splendor; it was all there, merely arranged in a different order, no less appropriate to the inhabitants’ needs than it had been before.
Simple variations of the parts
Symmetry, indeed, has been grossly overemphasized in both art and science: its main value is in giving meaning to its absence, dissymmetry, without which there could be no hierarchy.
The eye is repulsed by complexity if no order is detected, but it can be delighted by repetition, translation, rotation, reflection, magnification, and other simple variations of the parts.
The Topography of Tears
A Book by Rose-Lynn FisherThe Topography of Tears is a visual investigation of tears photographed through an optical, standard light microscope, a vintage Zeiss from the late 1970's, mounted with a digital microscopy camera.
Tears are the medium of our most primal language in moments as unrelenting as death, as basic as hunger, and as complex as a rite of passage. They are the evidence of our inner life overflowing its boundaries, spilling over into consciousness. Wordless and spontaneous, they release us to the possibility of realignment, reunion, catharsis, intractable resistance short-circuited. Shedding tears, shedding old skin. It’s as though each one of our tears carries a microcosm of the collective human experience, like one drop of an ocean.
Plus Equals #4
An Article by Rob WeychertOne of the seeds for Plus Equals was planted a few years ago with Incomplete Open Cubes Revisited, my extension of a Sol LeWitt work. I learned a lot about isometric projection from that project, but my affection for the concept didn’t begin there. Whether I’m looking at a Chris Ware illustration or an exploded-view technical drawing of a complex machine, an isometric rendering always stirs something in me.
The joy of the humble brick
An Article by Tim HarfordThe brick is one of those old technologies, like the wheel or paper, that seem to be basically unimprovable. ‘The shapes and sizes of bricks do not differ greatly wherever they are made,’ writes Edward Dobson in the fourteenth edition of his Rudimentary Treatise on the Manufacture of Bricks and Tiles. There’s a simple reason for the size: it has to fit in a human hand. As for the shape, building is much more straightforward if the width is half the length.
Subtilitas
A BlogSUBTĪLITĀS (latin; noun f., 3rd):
fineness of texture, logic, detail; slenderness, exactness, acuteness; sharpness : precisionnarrowdesign.com
A Website by Nick JonesDesign
Prototype
CodeRafael Araujo's Golden Ratio
A GalleryBlue Morpho Double Helix & Icosahedron
Cityspace series
A Gallery by Emily GarfieldPrimary series for imaginary map drawings, spanning 2008-present and using various materials and techniques.
bees & bombs
A Blog
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.