The notion of a thermal optimum persists There is an underlying assumption that the best thermal environment never needs to be noticed, and that once an objectively "comfortable" thermal environment has been provided, all of our thermal needs will have been met. The use of all of our extremely sophisticated environmental control systems is directed to this one end—to produce standard comfort zone conditions. Lisa Heschong, Thermal Delight in Architecture heatcomfortenvironmentux
Interlocking "The art world is highly invested in the idea that you can take an object and set it in a room, and the internal relationships will be so strong and so meaningful that all the kinds of change that take place on the object as a result of its being in a new environment will not critically affect our perception of the object. If that is the given assumption, then the object can be moved from one environment to another without its being critically altered, which then gives rise to the illusion that it can be moved from culture to culture, that it has the ability to transcend its cultural specificity, which in turn gives rise to the ultimate illusion that the object can transcend time. Because what is being claimed is that there exist certain objects isolated and meaningful enough to be transcendent, that they have the power to go on and on, that they are, as it were, timeless. "Well, one of the things that I was becoming involved in at that point in playing artist was the growing suspicion that this breaking down of the edge, the idea of the painting's moving into its environment, was putting the whole heightened rationale of the art object into doubt. There is simply no real separation line, only an intellectual one, between the object and its time environment. They are completely interlocking: nothing can exist in the world independent of all the other things in the world." Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees Deep Interlock contextchangeenvironmentobjects
Little sense of season The real world of technology denies the existence and the reality of nature. For instance, there is little sense of season as one walks through a North American or western European supermarket. Just as there is a little sense of season, there is little sense of climate. Everything possible is done to equalize the ambiance – to construct and environment that is warm in the winter, cool in the summer. Ursula M. Franklin, The Real World of Technology naturecyclesenvironment
The receiving end At times it helps to rephrase an observation in line with a perspective from the receiving end of technology. When my colleagues in the field of cold-water engineering speak of "ice-infested waters", I am tempted to think of "rig-infested oceans". Language is a fine barometer of values and priorities. As such it deserves careful attention. Ursula M. Franklin, The Real World of Technology valuesenvironmentlanguage
Walden A Book by Henry David Thoreau The quality of the dayI went to the woodsI love to be aloneQuiet desperationA new wearer of clothes+2 More Upstream ColorThoreau 2.0Upstream Color Original Soundtrack naturesolitudeenvironmentlabor
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