The American lawn uses more resources than any other agricultural industry in the world. The American lawn could feed continents if people had more social responsibility.
Why should it be indecent to have anything useful in the front half of your property or around the house where people can see it? Why is it low-status to make that area productive? The condition is peculiar to the British landscaping ethic; what we are really looking at here is a miniature British country estate, designed for people who had servants. It has become a cultural status symbol to present a non-productive facade. The lawn and its shrubbery is a forcing of nature and landscape into a salute to wealth and power, and has not other purpose or function.
The only thing that such designs demonstrate is that power can force men and women to waste their energies in controlled, menial, and meaningless toil.
Neighborhood is a word that has come to sound like a Valentine. As a sentimental concept, “neighborhood” is harmful to city planning. It leads to attempts at warping city life into imitations of town or suburban life. Sentimentality plays with sweet intentions in place of good sense.
We shall have something solid to chew on if we think of city neighborhoods as mundane organs of self-government. Our failures with city neighborhoods are, ultimately, failures in localized self-government. And our successes are successes at localized self-government.
My article “Off the Grid… and Back Again? The Recent Evolution of American Street Network Planning and Design” has been published by the Journal of the American Planning Association and won the 2020 Stough-Johansson Springer Award for best paper. It identifies recent nationwide trends in American street network design, measuring how urban planners abandoned the grid and embraced sprawl over the 20th century, but since 2000 these trends have rebounded, shifting back toward historical design patterns.
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.
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.
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.
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.
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.
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.