Geoff Manaugh
A Burglar's Guide to the City
Home Star
Imperfectly locked doors quietly waiting
A Fragment by Geoff Manaugh“Without vitamin C,” Anthony writes, “we cannot produce collagen, an essential component of bones, cartilage, tendons and other connective tissues. Collagen binds our wounds, but that binding is replaced continually throughout our lives. Thus in advanced scurvy”—reached when the body has gone too long without vitamin C—“old wounds long thought healed will magically, painfully reappear.”
In a sense, there is no such thing as healing. From paper cuts to surgical scars, our bodies are catalogues of wounds: imperfectly locked doors quietly waiting, sooner or later, to spring back open.
Caustic Engineering
An Article by Geoff ManaughA piece of milled plexiglass acting as a projecting lens; via the Computer Graphics and Geometry Lab at the École Polytechnique Fédérale de Lausanne
New milling techniques applied to glass and plexiglass panels could be used to “create windows that are also cryptic projectors, summoning ghostly images from sunlight.”
[Pauly and Bompas] hope that the technique will be used in architectural design, to create windows that mould sunlight and throw images or patterns onto walls or floors,” which, if timed, milled, and manipulated just right, could produce a slowly animated sequence of images being projected by an otherwise empty window during different times of day.
A Plea for Lean Software
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 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.
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.
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 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.
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.