Agile Design and Development
So that you can get feedback on it and make it better
The most rewarding iterations
Building is never a straight line
Product owner vs. product manager
A Product Owner is focused on output i.e. how quickly can we build these features?
Product Management, on the other hand, is focused on outcomes i.e. why are we building these features in the first place?
Good design is redesign
Good design is redesign. It's rare to get things right the first time. Experts expect to throw away some early work. They plan for plans to change.
It helps to have a medium that makes change easy. When oil paint replaced tempera in the fifteenth century, it helped painters to deal with difficult subjects like the human figure because, unlike tempera, oil can be blended and overpainted.
Finish designing as close to the end of a sprint as possible
The traditional process of delivering design, vs. delivering design just in time.
Designers are often working at least one sprint ahead of engineers. While one sprint might not seem like much of a lag, a typical product team learns a lot after the design hand-off. ...Instead of working ahead, we should finish designing as close to the end of a sprint as possible: just-in-time design.
We optimize what we measure
Scrum does not say “only focus on output”, but, unfortunately, humans will optimize for what they measure.
If you worry about story points & hitting your estimations, that’s what is going to consume your attention. That is what you and your team will optimize for.
And that is the core critique of Scrum as it is practiced: That it focuses a product team’s attention so heavily on delivery — on building lots of features quickly & efficiently — that teams fail to focus on spending time to discover what the right thing to build is.
How we can do better
It actually doesn't matter whether you actually have a formal retrospective. It doesn't matter whether you have four or five labels of things on your retro board, or exactly how you do the retro. What does matter is the notion of thinking about what we're doing and how we can do better, and it is the team that's doing the work that does this, that is the central thing.
The 'date scrum' anti-pattern
Date Scrum is an R&D pattern where developers are asked to estimate software project requirements upfront for the entirety of the project. After the project is green lighted and the budget is set based on the final estimates, the team then holds daily scrums to status and manage risk as they “iterate” the solution toward the release date. To some, this approach is described as doing Waterfall in sprints.
The fundamental problem with Date Scrum is that the team is de-focused from discovering the best solution. Instead they are heavily focused on delivering Something™ by the Date™. Engineers are problem solvers, and if the primary problem becomes delivering Something™ that will pass QA by the Date™, they will, with enough pressure, solve that exact problem.
That which requires caring
Today's real world of technology is characterized by the dominance of prescriptive technologies.
The temptation to design more or less everything according to prescriptive and broken-up technologies is so strong that it is even applied to those tasks that should be conducted in a holistic way. Any tasks that require caring, whether for people or nature, any tasks that require immediate feedback and adjustment, are best done holistically. Such tasks cannot be planed, coordinated, and controlled the way prescriptive tasks must be.
Prescriptive technologies eliminate the occasions for decision-making and judgment in general and especially for the making of principled decisions. Any goal of the technology is incorporated a priori in the design and is not negotiable.
Manifesto for Agile Software Development
A DefinitionWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Agile Scrum is not working
The Agile founders had it right, one size doesn't fit all. What the founders perhaps didn’t foresee, or couldn’t agree on, is that in order for the world to scale and consume their wisdom, it had to be packaged as concrete practices, not as abstract classes with virtual methods to be defined in context. And to the proponents of Agile Scrum, give them their due, for their part, they made it concrete – Agile Scrum has been packaged and delivered. Yet much work remains to realize the promise of Agile, which in summary is, the realization of wise use of lightweight development practices and workflows that flexibly adapt to the changing and evolving needs of customers.
Driving engineers to an arbitrary date is a value destroying mistake
An Article by Gandalf HudlowWhat happens when you apply date pressure to software engineers working on high value software projects? The engineers will focus on delivering Something™ by the Date™! This fatal flaw results in delivery of a Something™ full of chaos and features that nobody really wants or needs.
Beware SAFe, an Unholy Incarnation of Darkness
An Article by Sean DexterThe Lean Portfolio Management function that controls funding, are given sole authority to approve which Portfolio Epics move into each stream. Epics are not explanations about a problem that needs to be solved. They are pre-formed ideas about how best to solve those problems.
Right away we can see signs of the old-school mindset of viewing teams as a “delivery” function instead of a strategic one. The high level thinkers come up with ideas, and the low level doers execute on those ideas. Ignored is the possibility that those closest to the work might be best equipped to make decisions about it. Escaping from this misguided mindset is a core goal of Agile thinking that SAFe fails to remotely accomplish.
Why Scrum is killing your product
An Article by Henry LathamDesign Systems, Agile, and Industrialization
An Article by Brad FrostI’ve come to the conclusion that “enterprise web development” is just regular web development, only stripped of any joy or creativity or autonomy. It’s plugging a bunch of smart people into the matrix and forcing them to crank out widgets and move the little cards to the right.
In these structures, people are stripped of their humanity as they’re fed into the machine. It becomes “a developer resource is needed” rather than “Oh, Samantha would be a great fit for this project.” And the effect of all this on individuals is depressing. When people’s primary motivation is to move tickets over a column, their ability to be creative or serve a higher purpose are almost completely quashed. Interaction with other humans seems to be relegated to yelling at others to tell them they’re blocked.
Reading “AS PER THE REQUIREMENTS” in tickets makes me dry heave. How did such sterile, shitty language seep into my everyday work?
The value-destroying effect of arbitrary date pressure on code
An Article by Gandalf HudlowThe mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™!
What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™.
Agile is Dead (Long Live Agility)
An Article by Dave ThomasThe word “agile” has been subverted to the point where it is effectively meaningless, and what passes for an agile community seems to be largely an arena for consultants and vendors to hawk services and products.
…Let’s abandon the word agile to the people who don’t do things. Instead, let’s use a word that describes what we do. Let’s develop with agility.
- You aren’t an agile programmer—you’re a programmer who programs with agility.
- You don’t work on an agile team—your team exhibits agility.
- You don’t use agile tools—you use tools that enhance your agility.
/
Individuals and Interactions over Processes and Tools
Working Software over Comprehensive Documentation
Customer Collaboration over Contract Negotiation, and
Responding to Change over Following a PlanTraditional companies are losing because they mismanage software engineers
An Article by Emma WattersonInnovation is messy, and frankly Anti-Steve [Jobs] can’t figure out why you wouldn’t just tell people the right thing to build and skip all the trial and error that comes with innovation. Anti-Steve and his board of directors that keep him in place fundamentally believe that they know what needs to be built. Or at least that they can hire the messiah that will come down off the mountain and tell everyone what to build. There is no such messiah.
Why we stopped breaking down stories into tasks
An Article by Adam SilverThe Scrum process says to break down stories into tasks to make estimation easier, encourage collaboration and to be able to show more granular progress during a sprint.
But after a few sprints, we decided to do the next sprint without creating tasks. As a result we drastically increased our velocity and never went back. Here I'll jot down some of the reasons we decided to do this:
- Breaking down stories into tasks is time consuming
- The tasks we came up with invariably would change as we worked on the stories
- Tasks are repetitive
- Tasks were often carried out in parallel
- Our estimates didn't improve
- It decluttered our task board
- It encouraged collaboration throughout the sprint
While we started our process by following Scrum to the letter, we soon realised that breaking down stories into tasks was something that wasn’t worthwhile for us. In the end we realised that it was overplanning and poor use of our time. In the end we used that time to get on with the work and deliver at a significantly faster pace.
Why We Don't Do Daily Stand-Ups at Supercede
An Article by Jezen ThomasYesterday I worked on the widget.
Today I will work on the widget.
I have no blockers.Are you asleep yet? The developers are. You promise them an intellectually stimulating work environment and what they end up with is drudgery.
What value can be had from these meetings anyway? Using “alignment” for justification is so nebulous that it is essentially meaningless. Engineers align themselves. They talk. Especially if you hire good ones (which, you know, you’ll struggle to if you have a culture of coercing them into this kind of busywork). Where does the real discussion happen? It’s written down.
Software that nobody wants
An Article by Gandalf HudlowFinding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
- Not wanted - Company specified a solution to a problem that customers don't actually have
- No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
- Incorrect Packaging - Customers need a website, but the company created an iOS app instead
- Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
Making sense of MVP
An ArticleHenrik Kniberg:
The top scenario (delivering a front tire) sucks because we keep delivering stuff that the customer can’t use at all. If you know what you’re doing – your product has very little complexity and risk, perhaps you’ve built that type of thing hundreds of times before – then go ahead and just do big bang. Build the thing and deliver it when done.
Doing It Right
An Article by Brad FrostDoing it right requires a different pace of working and a much broader thought process than “ok, let’s get this thing out the door.” Which is super tough because most workplaces place a huge emphasis on getting things out the door, and fast. Little agile tickets that are expected to be completed in micro sprints to me seem to be antithetical to doing it right.
Planning doesn't make for better software
A Fragment by Robin RendleMy own time in a Silicon Valley startup has proved this much to be true; planning doesn’t make for better software. In fact today our design systems team doesn’t have sprints, we don’t have tickets or a daily standup. Each day we come to work, figure out what’s the most important thing that we could be doing, and then we—gasp!—actually do it.
Watching so many other teams slowly flail about whilst they plan for quarter 3.2 of subplan A, whilst our team produces more work in a week than they all do combined in a quarter has been shocking to me.
After four years of working in a large startup, I know what I always assumed was true: you don’t need a plan to make a beautiful thing. You really don’t. In fact, there’s a point where overplanning can be a signal of inexperience and fear and bullshit. The scrum board and the sprints and the inane meetings each and every day are not how you build another Super Mario 64.
Instead all you have to do is hire smart people, trust them to do their best work, and then get the hell out of their way.
Agile as Trauma
An Essay by Dorian TaylorThe Agile Manifesto is an immune response on the part of programmers to bad management.
Yagni
A Definition by Martin FowlerYagni originally is an acronym that stands for "You Aren't Gonna Need It". It is a mantra from Extreme Programming that's often used generally in agile software teams. It's a statement that some capability we presume our software needs in the future should not be built now because "you aren't gonna need it".
The State of Agile Software in 2018
A Talk by Martin FowlerOn the surface, the world of agile software development is bright, since it is now mainstream. But the reality is troubling, because much of what is done is faux-agile, disregarding agile's values and principles. The three main challenges we should focus on are: fighting the Agile Industrial Complex and its habit of imposing process upon teams, raising the importance of technical excellence, and organizing our teams around products (rather than projects).
Product vs. Feature Teams
An Article by Marty CaganThis article is certain to upset many people.
20 Minutes in Manhattan
It begins with a trip down the stairs
The walk from my apartment in Greenwich Village to my studio in Tribeca takes about twenty minutes, depending on the route and on whether I stop for a coffee and the Times. Invariably, though, it begins with a trip down the stairs.
The building I live in is a so-called Old Law tenement and was built in 1892, a date inscribed on the metal cornice that also carries the building’s name: Annabel Lee. Like most such tenements, ours is five stories high (a few are six, even seven), and I live with my wife, Joan, on the top floor.
Thoughts on stairs
...There is something hypnotic about stair climbing, and as often as I find myself thinking I ought to be at the fourth floor when I am only at the third, I think I've only gotten to three when I'm actually arriving at four.
...To my eyes (and legs) the straight run is more elegant and enjoyable to ascend.
...The narrowing is both functional and artistic, acknowledging that a stair is likely to be used by a smaller number of people as it rises and forcing the perspective narrowing of the long view upward.
...The symbolic weight of stairs is embodied in both their form and their magnitude.
(an architectural stem cell that might transform itself into any organ for living)
The grid and its difficulties
Criticism of the grid and its difficulties was voiced from the start. Olmsted himself noted several problems that arose from the fixed dimensions of the city’s blocks: the impossibility of producing sites for very large buildings and campuses; issues of daylighting; the difficulty of creating systems of formal and symbolic hierarchy within the field of uniformity.
The relative homogeneity of building
The relative homogeneity of building—and city making—in different cultures is the result of their social organization (large buildings and enclosures are the product of the need for large gatherings), their economic possibilities (only a very rich and powerful Church could produce the cathedrals), their available material and technological resources (very little timber construction is to be seen in desert cultures), and their styles of living (portable tepees and tents are logical if you’re involved in seasonal migration). The same is true today. New York builds within an essentially narrow range of configurations, materials, and structural systems, its limits set by culture, technology, and economics: small apartments in high-rise buildings result from extremely high costs for land and construction, a growing predominance of non-nuclear-family living arrangements, and a legal framework that continuously negotiates the bar of bulk upward.
All-use environments
Until the nineteenth century, virtually all cities were “all use” environments. Craft-scale production was typically carried out in a workshop below the home of the craftsperson, which often also served as the site of exchange.
Sonorisms II
the symbolic weight of stairs
the regulation of obnoxious uses
a collector and transmitter of memory
Dubai is the world made Disney
people whose traditions and desires cannot be repressed by mere architecture
the annihilation of space by time (Marx)Zoning for diversity
As production becomes increasingly clean and knowledge-based, as our urban economies tip dramatically to service industries, as racism and ethnic animosities ebb, and as the model of mixed use becomes more and more persuasive and visible, cities are in a position to dramatically rethink zoning as a medium for leveraging and usefully complicating difference, rather than simply isolating it.
Cities designed to facilitate walking
It seems clear that for reasons of both sustainability and sociability, human power as a means of locomotion in the city should be optimized. Cities designed to facilitate walking will—because of their accessible dimensions—likely be more neighborhood-focused and compact as well as more mixed in use. To be reached by walking, a destination—whether a school, office, or shop—must be close at hand. A reasonable walking time (in this culture) for basic necessities is generally considered to be about ten minutes, which translates (at an average walking speed of three to four miles per hour) into six to eight short blocks (or three to four long ones). Using this dimension as a radius, we might begin to think of a comfortable scale for a neighborhood as ten to fifteen New York City blocks.
Obsessed with absolute numbers
Modernist planning was obsessed with absolute numbers, including the minimum dimensions of rooms, open space per capita, and the one-size-fits-all head counts of neighborhood units. This was often pegged at five to seven thousand and was used as a formula for determining the distribution of schools, shops, sports fields, and other facilities. The failure of such planning is not in its effort to be comprehensive or to equalize access to necessary facilities. It is, rather, the attempt to rationalize choice on the basis of a homogeneous set of subjects, a fixed grammar of opportunities, a remorseless segregation of uses, and a scientistic faith in technical analysis and organization that simply excludes diversity, eccentricity, nonconforming beauty, and choice. The utopian nightmare.
A collective right to the city
A collective right to the city was seminally articulated by the French philosopher Henri Lefebvre, a right understood not simply as individual access to the goods, services, and spaces of the city but as the right to change the city in accordance with our deepest desires, to steer the very process of urbanization and the way in which the city nurtures the kinds of people we wish to become.
The axis of movement
Moving in the city means constantly changing the axis of movement. In general, lateral movement is confined to a single plane, what’s called grade, the ground level.
Because circulation in multistory buildings is fundamentally one way—which is to say from the bottom up—the condition at the top is invariably different from that at the bottom. Rooftop circulation is the domain of Fantômas, of cat burglars and fleeing criminals, of lovers, and of those acrobatic enough to negotiate the gaps between buildings.
Controlled environments
“Controlled environments” are another of modernism’s great obsessions. Extravagant amounts of energy are spent to keep buildings—as well as skyway systems, shopping malls, and domed stadia—at a constant temperature year-round via entirely mechanical means. The folly is not simply a touchy-feely isolation from the authenticities of nature, which can admittedly be cruel, but a larger disciplinary presumption that seeks to extend the centralized authority (central air, central government) of power ever more comprehensively. It is possible that this particular hubris may have pushed Gaia to the tipping point.
Ground displaced upward
Imagine that our rooftops were parkland, that the area of ground occupied by buildings was, in effect, simply displaced upward. Imagine that the city enacted legislation requiring that the equivalent of 100 percent of the surface area of New York were to be green. A 100 percent requirement would not simply oblige green roofs. It would also demand that compensatory greenery be added to make up for such ungreenable areas as roadways, runways, and other unplantable places. Perhaps the requirement would be satisfied with road narrowings, cantilevered gardens, or green floors in buildings (utilities on the order of the mechanical floors that occur in almost all tall buildings).
The stoop is a space of spectatorship
Along with being a meeting place, the stoop is a space of spectatorship. A street lined with stoops is a kind of lateral stadium, ideal for viewing the passing parade, whether formal ones like the giant Gay Pride and Halloween Parades (until their route was changed a few years ago) or the more informal quotidian version. Hanging out on the stoop allows the sitter to observe the dance (Jane Jacobs’s ballet) of daily activity, to notice what is out of the ordinary, to provide the kind of public presence that prompts neighborly behavior.
The Poop Press Project
(In the run-up to the law, I myself had undertaken the “Poop Press Project,” which had entailed fixing a star-shaped cookie mold to the end of a stick to transform the noisome waste into street art, an attempt only intermittently effective.)
Walking is a natural armature for thinking sequentially
Walking is a natural armature for thinking sequentially. It also has a historic relationship to mental organization that ranges from the Peripatetics, to the philosophers of Kyoto, to the clockwork circuit of Immanuel Kant, to the sublimities of the English Romantics and their passages through nature. It is not simply an occasion for observation but an analytic instrument.
The drift
The Situationists were also practitioners of a special urban-analytic walking style, the dérive—the “drift”—which Debord described as “a technique of transient passage through varied ambiences. The dérive entails playful-constructive behavior and awareness of psychogeographical effects; which completely distinguishes it from the classical notions of the journey and the stroll.” “In a dérive,” Debord deadpans, “one or more persons during a certain period drop their usual motives for movement and action, their relations, their work and leisure activities, and let themselves be drawn by the attractions of the terrain and the encounters they find there."
The dérive joins the free association of surrealism, the LSD of hippiedom, and cinematic montage as tactics for overcoming the fixity of received ideas of order and logic.
By putting progress through the city into a state of constant indeterminacy, it represents a schooled “style” of being lost.
To disappear in the crowd
The modern city produces its own style of getting lost, rooted in its special form of alienation. Here, the crowd, while it can be protective, is also a medium for both erasing individuality and homogenizing experience, for making us disappear.
Daylight should not tyrannize architecture
Daylight should not tyrannize architecture. As with so many aspects of the design of the city, light is something that should be available in a variety of modulations and susceptible to a variety of controls. However, the prejudice must always be for access.
The 1916 Zoning Resolution
Architecturally, what is striking about the 1916 legislation is that it sought to articulate a logical formula for achieving a public good in the absence of a specific vision of exactly what would actually be produced.
The spatial dimension of democracy
Since the time of the Greeks, democracy has been understood to have a spatial dimension and so, by extension, an element of scale. Plato measured the polis, the unit of democratic citizenship, at five hundred citizens, an extremely tractable size for a community that seeks to express itself through direct engagement.
Induced demand
Every attempt to cul-de-sac city streets, to change traffic patterns in favor of pedestrians, or to narrow street ends is met with the same howl of protest from the authorities: this will increase congestion because urban traffic is a zero-sum game. Any reduction in volume in one place in the city will inevitably be accompanied by a rise in traffic somewhere else.
This claim is fallacious: the true corollary is the opposite. In case after case, a reduction of the space available for vehicular traffic has simply resulted in the reduction of traffic overall.
Greenfill
I have for years been engaged in a thought experiment, the product of which is the idea of a program of “greenfill” for the city streets. The idea is simple: if one lane of every block in the city were removed from the automotive system and returned to the pedestrian realm, an enormous range of urban problems could be solved.
Responsibility for the sidewalk
It is a bizarre anomaly that we freely spend countless billions on the construction and maintenance of our streets but leave the repair, and cleaning, of our sidewalks—and the crucial shading apparatus they support—to the tender mercies of private landlords who show no strong inclination to take proper responsibility for this vital duty and whose responsibility for but a fragmentary increment of the block creates conditions of uneven repair and character.
Surrealism has become the kitsch of postmodernity
A dialogue between homogeneity and exception
All cities can be described as a dialogue between homogeneity and exception, and each strikes a particular balance that is at the core of its character.
If you want to build an outrageous building
If you want to build a bad building, hire a good architect, and If you want to build an outrageous building, hire a distinguished one.
The informing idea of functionalism
The informing idea of functionalism is what is called elegance by engineers and scientists—the notion that the best solution to a problem (whether applied to a mathematical proof, a machine, or an organizational diagram) is the most succinct. This conceit collapses the technical, the ethical, and the aesthetic, which powers the idea exponentially.
The Radiant City
Le Corbusier’s advocacy of what he had come to call the “Radiant City” continued to his death, and in the 1960s he published his most complete vision, drawn with seductive elegance and insanely mesmerizing to the generation of architects teaching in my school days, for whom possession of a Corb drawing or painting was tantamount to owning a relic of the True Cross.
Tower blocks and slabs
The buildings of Washington Square Village and Silver Towers are museum-quality examples of the two great apartment typologies of modernity: the tower block and the slab. Both illustrate their strengths and disadvantages when introduced into the urban fabric in their pure state.
Genuinely sustainable architecture
The received version of modern architecture, with its social simplification and technical sophistication, has gotten it exactly backward. Genuinely sustainable architecture must begin with the simplest technical solutions (sunshades, cross ventilation, correct solar orientation) but conduce the most complex social relations (variety before uniformity). Invention will come not simply from the fevered acts of lonely imagination but from the constant reframing of questions raised at the intersection of climate, culture, technology, politics, and taste, by the understanding that architectural meanings are produced, not inherent.
New-urbanist projects
The overwhelming majority of new-urbanist projects retain the almost purely residential, exclusively middle-class character of suburbia, simply substituting one formal paradigm for another. Instead of curving streets, cul-de-sacs, and half-acre lots, these developments offer grids, tightly spaced houses with front porches, and a town center instead of a shopping center containing the very same shops.
Touring SoHo
SoHo has, however, become part of a tourist archipelago where the definition of place falls into a set of increasingly generic categories. The act of touring devolves less on the particulars of geography than on the consumption of a set of prepackaged lifestyles, defined by a fixed array of goods and services. Almost every city in America now boasts a SoHo equivalent.
The question of gentrification
The question of gentrification is made complex by the fact that the urban qualities it produces—lively street life, profuse commerce, preservation and upgrading of old buildings—are highly desirable, the substrate of urbanity. The problem with gentrification is with its particulars and with its effects.
Gentrification suppresses reciprocity by its narrowed scripting of formal and social behavior, by turning neighborhoods into Disneylands or Colonial Williamsburgs, where residents become cast members and the rituals of everyday life become spectacle or food for consumption.
Non-architects
In 1964, the historian Bernard Rudofsky curated a show at MoMA called Architecture Without Architects, celebrating the formal qualities of a range of traditional building practices drawn from around the world.
Setting aside the endlessly troubled implications of the Western gaze on “primitive” cultures, the show had the very constructive impacts of encouraging formal diversity at a time when mainstream architecture had grown desperately, myopically monochromatic and of suggesting that “non-architects” were capable not only of making good judgments about their environments but of actually taking the lead in creating them.
A sensitively tailored combination of modes
Efficiency is produced not by the sort of movement monoculture of cars-only American cities but by a sensitively tailored combination of modes sited to exploit the particular efficiencies of each and providing useful duplication and alternative.
Flying a kiwi
Flying a kiwi fruit from New Zealand to New York produces four times the weight of the kiwi in greenhouse gases; moving a head of lettuce to here from California requires ten times the calories the lettuce yields to the eater.
Ideas for linear cities
Arturo Soria y Mata, who proposed a linear streetcar suburb for Madrid in 1882 and managed to build something like three miles’ worth of an intended thirty. Likewise, the project by Edgar Chambless for Roadtown, published in 1910, depicted an infinitely long, two-room-wide building atop three levels of underground rail lines for express, local, and freight traffic. In the late 1920s, N. A. Miliutin proposed a Soviet Union–spanning linear plan that—following Soria y Mata’s rhetoric—would have solved the old Marxian chestnut of city/country contradiction at a stroke. Le Corbusier’s Algiers scheme of 1933—a highway-topped fourteen-story building meant to stretch miles along the Mediterranean and house 180,000 people—was surely the most immediate precursor of Rudolph’s “City Corridor.”
The final architectural embellishments
The final architectural embellishments for the neighborhood should be the most exceptional, a kind of punctuation by relief, the last bursts of creative potential as the scene shifts.
Those glowing domes and minarets
I began to have my doubts about those glowing domes and minarets. Finally, I felt that this modern celebration of history subtracted something: I felt gypped out of the dark.
Induced communication
I remain mystified by what seems like an exponential increase in the need to communicate induced by the availability of a ready new means to do so, just as new highway capacity produces increased traffic. Witness the cabdrivers who talk uninterrupted on the phone as they travel the city, or the truly huge numbers of people who speak on the phone as they walk down the street: the medium has clearly become the message, if the meaning of the message remains somewhat opaque.
Management and manipulation of fear
More and more of daily life is governed by the management and manipulation of fear.
A society can be judged by the risks to which it chooses to respond, the dangers it values, the targets it gives high priority.
If those striped bass need a place to fuck
The real deathblow to Westway proved to be a lawsuit filed on behalf of the striped-bass population—shepherded through the courts by the activist Marcy Benstock—that sought to protect their breeding grounds in the pilings beneath the piers that the fill would have eliminated. After this was decided in the federal courts, Mayor Ed Koch, a Westway supporter, reportedly uttered, in frustration, the most memorable line of the affair: “If those striped bass need a place to fuck, I will build them a motel in Poughkeepsie.”
High-priced good times
Once again, a neighborhood dedicated to production has been transformed into one for consumption. As someone who believes that an internal balance between these activities is vital to the health, character, and autonomy of the city, I find that the sight of yet another zone of high-priced good times gives me the willies, even as I tuck into my perfect branzino in the lovely back garden of the delightful Italian restaurant.