What Le Corbusier got right about office space An Article by Tim Harford timharford.com In the 1960s, the designer Robert Propst worked with the Herman Miller company to produce “The Action Office”, a stylish system of open-plan office furniture that allowed workers to sit, stand, move around and configure the space as they wished. Propst then watched in horror as his ideas were corrupted into cheap modular dividers, and then to cubicle farms or, as Propst described them, “barren, rathole places”. Managers had squeezed the style and the space out of the action office, but above all they had squeezed the ability of workers to make choices about the place where they spent much of their waking lives. ...It should be easy for the office to provide a vastly superior working environment to the home, because it is designed and equipped with work in mind. Few people can afford the space for a well-designed, well-specified home office. Many are reduced to perching on a bed or coffee table. And yet at home, nobody will rearrange the posters on your wall, and nobody will sneer about your “dog pictures, or whatever”. That seems trivial, but it is not. workpersonalityownershipmodularitychoice
Can maintenance save civilisation? An Article by Tim Harford timharford.com Maintenance is a low-status affair: you can confess to being unable to change a tyre in a way that you would never confess to being unable to name a play by Shakespeare. …We understand the expertise of janitors, plumbers and mechanics, and we suffer mightily in their absence, yet somehow we take them for granted. We take for granted, too, the most basic maintenance of all — preparing food, washing clothes, changing dirty nappies. Nobody would boast at a dinner party or on a first date about doing any of this, yet it is essential. …This is about more than breaking bridges and breaking bike chains. There is a missed opportunity here to find something rather wonderful in maintenance. repaircivilization
Ideas behind their time An Article by Tim Harford www.ft.com These days I am more interested in the reverse case [of Da Vinci's helicopter]: ideas that could have worked many centuries before they actually appeared. The economist Alex Tabarrok calls these “ideas behind their time” Curious minds want to know why these ideas appeared so late — and whether there might be anything that would prevent delays in future. One explanation is that the ideas aren’t as simple as they appear. The bicycle is not as straightforward an invention as it seems. To move from ox-hauled cart to human-powered bicycle requires smooth-rolling wheel bearings, which in turn need precisely engineered bearing balls. Modern steel ball bearings were not patented until the late 1700s, and demand from the 19th-century bicycle industry helped to improve their design. Materials and how to employ them inventionideas
The joy of the humble brick An Article by Tim Harford timharford.com The 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. I am hereWhat the material wants to beWhat the brick really wants. materialbuildingmodularitygeometry
A Plea for Lean Software An Essay by Niklaus Wirth cr.yp.to Software's girth has surpassed its functionality, largely because hardware advances make this possible. The way to streamline software lies in disciplined methodologies and a return to the essentials. Measured by the number of its featuresEssential vs. nice to haveDependence is more profitable than educationThe most rewarding iterationsNever enough time A grossly obese set of requirementsFeatures and complexity softwareperformancefunction
Measured by the number of its features A primary cause of complexity is that software vendors uncritically adopt almost any feature that users want. Any incompatibility with the original system concept is either ignored or passes unrecognized, which renders the design more complicated and its use more cumbersome. When a system's power is measured by the number of its features, quantity becomes more important than quality. Every new release must offer additional features, even if some don't add functionality. featuresqualitycomplexity
Essential vs. nice to have Customers have trouble distinguishing between essential features and those that are just "nice to have." Examples of the latter class: those arbitrarily overlapping windows suggested by the uncritically but widely adopted desktop metaphor; and fancy icons decorating the screen display, such as antique mailboxes and garbage cans that are further enhanced by the visible movement of selected items toward their ultimate destination. These details are cute but not essential, and they have a hidden cost. / Increased complexity results in large part from our recent penchant for friendly user interaction. I've already mentioned windows and icons; color, gray-scales, shadows, pop-ups, pictures, and all kinds of gadgets can easily be added. Menus, Metaphors and Materials: Milestones of User Interface Designlittlebigdetails interfacesux
Dependence is more profitable than education A customer who pays—in advance—for service contracts is a more stable income source than a customer who has fully mastered a product's use. Customer dependence is more profitable than customer education. What I find truly baffling are manuals—hundreds of pages long—that accompany software applications, programming languages, and operating systems. Unmistakably, they signal both a contorted design that lacks clear concepts and an intent to hook customers. The design concept documentation
The most rewarding iterations Initial designs for sophisticated software applications are invariably complicated, even when developed by competent engineers. Truly good solutions emerge after iterative improvements or after redesigns that exploit new insights, and the most rewarding iterations are those that result in program simplifications. Evolutions of this kind, however, are extremely rare in current software practice—they require time-consuming thought processes that are rarely rewarded. Instead, software inadequacies are typically corrected by quickly conceived additions that invariably result in the well-known bulk. So that you can get feedback on it and make it betterTo anticipate all the uses and abuses agileiteration
Never enough time Time pressure is probably the foremost reason behind the emergence of bulky software. The time pressure that designers endure discourages careful planning. It also discourages improving acceptable solutions; instead, it encourages quickly conceived software additions and corrections. Time pressure gradually corrupts an engineer's standard of quality and perfection. It has a detrimental effect on people as well as products. Deadlines are bullshitThe Thing-deadline calculus