Software & Digital Products
A late change in requirements is a competitive advantage
Make the change easy
Software often feels inevitable
Growing in the correct way
It begins with craft
So insufficiently palimpsestic
Spatial software references
- Nototo
A great painting has to be better than it has to be
This sounds like a paradox, but a great painting has to be better than it has to be. For example, when Leonardo painted the portrait of Ginevra de Benci in the National Gallery, he put a juniper bush behind her head. In it he carefully painted each individual leaf. Many painters might have thought, this is just something to put in the background to frame her head. No one will look that closely at it.
Not Leonardo. How hard he worked on part of a painting didn't depend at all on how closely he expected anyone to look at it. He was like Michael Jordan. Relentless.
Relentlessness wins because, in the aggregate, unseen details become visible. When people walk by the portrait of Ginevra de Benci, their attention is often immediately arrested by it, even before they look at the label and notice that it says Leonardo da Vinci. All those unseen details combine to produce something that's just stunning, like a thousand barely audible voices all singing in tune.
Great software, likewise, requires a fanatical devotion to beauty. If you look inside good software, you find that parts no one is ever supposed to see are beautiful too.
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.
Jacked in
In digital design, products and services are frequently imagined and implemented placelessly: as if the consumer were jacked into The Matrix, and considering this product or that product from among an infinite set of choices at an infinitely-provisioned mercantile. The things we make are good, by this way of reasoning, if they fit the market’s demand.
Losing meaning
The people who’ve proven that they can make very good individual products with the radical focus of a spotlight seem to be pushed ever further from making good ecosystems.
Products are being made “consistent” with the application of so-called “design patterns,” and rather than bringing coherence to these various touch-points, the painting-on of interface standards and interaction patterns did something far less valuable.
Rote consistency, in the way many seem to be going about it (Material Design being just one example), is at odds with making things be good. It simplifies what needs to remain complex.
Always, when simplification is underway, meaning is being lost.
Penn Station
In the same way that physical architecture can affect a mind, so too can software. Slower, less reliable software is like Penn Station: Sure, you can catch a transfer from one train to another but the dreary lowness of the place, the lack of sunlight or sensible wayfinding will make you feel like a rat, truculent and worthless, and worse: You’ll acclimate to that feeling and accept it as a norm.
The Design of Design
A Book by Frederick P. Brooks, Jr.Visualizing Algorithms
An Article by Mike BostockManifesto 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.
Stop Drawing Dead Fish
A Talk by Bret VictorThe Future of Programming
A Talk by Bret VictorDesign Links & Learning
A Blog by Nick TrombleyCollections of articles, links, and other material from around the web, relevant to software design and engineering.
Ensuring Excellence
An Article by Marty Cagan…in so many of the best product companies there is an additional dimension that goes beyond individual empowered product teams, and even goes beyond achieving business results.
It has to do with ensuring a level of what I’ll refer to here as “excellence” although that is clearly a very ambiguous term.
Over the years, this concept has been referred to by many different names, always necessarily vague, but all striving to convey the same thing: “desirability,” “aha moments,” “wow factor,” “magic experiences,” or “customer delight,” to list just a few.
The concept is that an effective product that achieves results is critical, but sometimes we want to go even beyond that, to provide something special.
Maybe it’s because we believe this is needed to achieve the necessary value. Maybe it’s because the company has built its brand on inspiring customers.
Often this dimension shows up most clearly in product design, where functional, usable but uninspiring designs can often achieve our business results, but great design can propel us into this realm of the inspiring.
On online collaboration and our obligations as makers of software
An Essay by Baldur BjarnasonIs it the notetaking system that’s helping you think more clearly? Or is it the act of writing that forces you to clarify your thoughts?
Is it the complex interlinked web of notes that helps you get new ideas? Or is it all the reading you’re doing to fill that notetaking app bucket?
Is all of this notetaking work making you smarter? Or is it just indirectly forcing you into deliberate, goalless practice?
In Search of Organic Software
An Article by Pirijan KetheswaranTwo different kinds of farms can grow vegetables. One is a factory farm built for scale, and the other takes the time to grow more expensive but healthier plants without pesticides.
Will everyone appreciate the difference? Of course not, but the latter plants are labelled ‘organic’ to give us the information and the choice, so that those of us who do care can make better decisions.
So maybe we should have ‘organic’ software as well, made by companies that:
- Are not funded in such a way where the primary obligation of the company is to 🎡 chase funding rounds or get acquired (so bootstrapping, crowdfunding, grants, and angel investment are okay)
- Have a clear pricing page
- Disclose their sources of funding and sources of revenue
Reflections on Software Performance
An Article by Nelson Elhage- Performance is a feature
- Performance changes how users use software
- Performance needs effort throughout a project’s lifecycle
- Architecture strongly impacts performance
- Performance isn’t just about hot spots
- Performant foundations simplify architecture
…we underrate performance when designing and building software. We have become accustomed to casually giving up factors of two or ten or more with our choices of tools and libraries, without asking if the benefits are worth it.
Undoing the Toxic Dogmatism of Digital Design
An Essay by Lisa Angela- Design educators and industry leaders have never reached a consensus about what comprises a “good enough” foundational education for digital design.
- We do not properly retire methods (or ways of conducting them) that have been shown to be ineffective.
- Design team seniority levels are meaningless.
- We’ve collectively lost the safety (and subsequently the desire) to explore and fail.
- We afford well-known design leaders too much power to dictate how design is discussed and conducted.
- We have no ethical standards.
- Inclusive design and accessibility are afterthoughts — both in design education and in practice.
The things that you’re meant to do
A Quote by Josh WardleI used to work in Silicon Valley, and I’m aware of the things that, especially with games, you’re meant to do with people’s attention. You’re trying to capture as much of people’s attention as you can. So that involves things like endless play, or sending them push notifications, or asking them for sign-up information.
And philosophically, I enjoy doing the opposite of all those things, doing all the things that you are not meant to do, which I think has bizarrely had this effect where the game feels really human and just enjoyable. And that really resonates with where we’re at right now in the world and with COVID, and then also we’re trying to figure out, what is tech? What has tech become? I think that really resonates with people, and no ads—well, no monetization. People ask me a lot about these things, and it was like, I was literally just making a game for my partner, and I made some decisions that we would like.
I don’t believe in Zoom fatigue
An Article by Matt WebbIt’s not Zoom fatigue, it’s Zoom whiplash.
It’s a hunch. I can’t prove this.
The trick to get around this is to move smoothly up and down the gradient of social interaction intensity, never dropping below a basic floor of presence: the sense that there are other people in the same place as you.
Instead of having two modes, “in a call” and “on my own,” we need to think about multiple ways of being together which, minimally, could be:
- In a video call
- In an anteroom to a video call, hearing the sound of others
- In a doc together
- On my desktop but with the sense that colleagues are around
And the job of the designer is to ensure that their software ensures the existence of these different contexts, instead of having the binary on-a-call/not-on-a-call, and to design the transitions between them.
Spatial Software
An Article by John PalmerScales of cities, scales of software
An Article by Linus the SephistAmerican cities seem like a product of industrial processes where older European cities seem like a product of human processes. This is because most American cities were built after and alongside the car and the industrial revolution – the design of cities took into account what was easily possible, and that guided the shape and scale of everything.
Software has similar analogues. There are software codebases that feel much more industrially generated than hand written, and they’re usually written in automation-rich environments fitting into frameworks and other orchestrating code.
…But despite the availability of cars, I still much prefer the scale and ambiance of European, human-scale cities, because ultimately cities are places humans must inhabit and understand. In the same way, I still much prefer the scale and ambiance of hand-written codebases even in the presence of heavy programming tooling, because ultimately codebases are places humans must inhabit.
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.
How can we develop transformative tools for thought?
A Research Paper by Andy Matuschak & Michael NielsenConventional tech industry product practice will not produce deep enough subject matter insights to create transformative tools for thought.
...The aspiration is for any team serious about making transformative tools for thought. It’s to create a culture that combines the best parts of modern product practice with the best parts of the (very different) modern research culture. You need the insight-through-making loop to operate, whereby deep, original insights about the subject feed back to change and improve the system, and changes to the system result in deep, original insights about the subject.
Software Engineering as a Craft
An Article by Thomas WilsonThe decreasingly tangible product of code, i.e. that all we have are files on a hard-drive, may make it easy to forget that writing software produces a thing. If you produce a wonky chair or an overly long fork, it’s easy to see the quality of work was not great. By calling for a perception of software as a craft, we fight against that ability to forget or not notice the final quality of the product. You could watch two software engineers with different levels of experience, or in different domains, and it wouldn’t necessarily be so easy to guess which is which, at least from a distance.
So maybe there is something to be said for the value of software as a craft, for sometimes focusing on the practice of making better, or at least different, software just for the sake of it.
Why Scrum is killing your product
An Article by Henry LathamDeadlines are bullshit
An ArticleIn software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil.
- External vs. internal deadlines
- Why are internal deadlines evil?
- Engineers who love their work
Software developers have stopped caring about reliability
An Article by Drew DeVaultOf all the principles of software engineering which has fallen by the wayside in the modern “move fast and break things” mentality of assholes modern software developers, reliability is perhaps the most neglected, along with its cousin, robustness. Almost all software that users encounter in
$CURRENTYEAR
is straight-up broken, and often badly.The Rise Of User-Hostile Software
An Essay by Den DelimarskyWe are truly living in an era of user-hostile software, and when I say “user-hostile” I mean it as “software that doesn’t really care about the needs of the user but rather about the needs of the developer.”
I personally do not know anyone who asked for an online account requirement before they can use a keyboard; however, some product lead somewhere decided that it’s important to better “understand the customer” and “maximize marketing reach” through some weekly “Hey, we have a new keyboard!” newsletter.
Minimum Awesome Product
An Article by Carlos BeneytoUsers are accustomed to a minimum of quality, and they expect that of all new products.
If our product does not [meet basic expectations of quality], people will automatically believe that it is a bad product and they will not take it seriously. It is not what they expect.
Hence my suggestion that the MVP has died and the MAP: Minimum Awesome Product was born.
Traditional 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.
Research, empathy, simplicity, speed
An Article by Matthew StrömAs Nosrat provides a simple list of essential ingredients for any great meal, can we describe a simple list of essential components for digital products?
Here are four elements that I believe are the foundation of great digital products: Research, Empathy, Simplicity and Speed.
Craft and Material in Digital Design
An ArticleProduct Design Resources
A Reference Work by Brandon DornThings I‘ve read, people I‘ve tried to learn from, and things I‘ve done to become a better designer. This is an idiosyncratic list reflecting what has helped me along the way, rather than an exhaustive list of design classics.
Though the list leans toward theory — principles are more durable than technique — I offer a few ideas further down about how to practice design. It also leans toward information design, because the task of presenting rich, dense information in an accessible way is ultimately the task of any digital product.
Functional Prototyping. A Missed Opportunity in Web Design
An Essay by Chuánqí SunPrototyping allows engineers in various industries to “fail fast, fail cheap”, “select the best from the pool”, and “bring in the reality”.
Apps Getting Worse
An Article by Tim BrayToo often, a popular consumer app unexpectedly gets worse: Some combination of harder to use, missing features, and slower. At a time in history where software is significantly eating the world, this is nonsensical. It’s also damaging to the lives of the people who depend on these products.
...Maybe we ought to start promoting PMs who are willing to stand pat for an occasional release or three. Maybe we ought to fire all the consumer-product PMs. Maybe we ought to start including realistic customer-retraining-cost estimates in our product planning process.
We need to stop breaking the software people use. Everyone deserves better.
Feature parity
An ArticleWhilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business.
Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'.
The return of fancy tools
An Article by Tom MacWrightTechnology is seeing a little return to complexity. Dreamweaver gave way to hand-coding websites, which is now leading into Webflow, which is a lot like Dreamweaver. Evernote give way to minimal Markdown notes, which are now becoming Notion, Coda, or Craft. Visual Studio was “disrupted” by Sublime Text and TextMate, which are now getting replaced by Visual Studio Code. JIRA was replaced by GitHub issues, which is getting outmoded by Linear. The pendulum swings back and forth, which isn’t a bad thing
On Design Engineering: I think I might be a design engineer...
An Article by Trys MudfordDesign engineering is the name for the discipline that finesses the overlap between design and engineering to speed delivery and idea validation. From prototyping to production-ready code, this function fast-tracks design decisions, mitigates risk, and establishes UI code quality. The design engineer’s work encapsulates the systems, workflows, and technology that empower designers and engineers to collaborate most effectively to optimise product development and innovation.
— Natalya ShelburneWebsites are not living rooms and other lessons for information architecture
An Essay by Sarah R. BarrettWhile there is a lot that IA can learn from actual architecture or city planning, websites aren’t buildings or cities, and they don’t have to work like them. Instead, they should be designed according to the same principles that people’s brains expect from physical experiences.
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
Guidebook: Graphical User Interface Gallery
A WebsiteGuidebook is a website dedicated to preserving and showcasing Graphical User Interfaces, as well as various materials related to them.
A Mindful Mobile OS
An Article by Clo S.I read and loved Potential's "iOS 15, Humane" proposition. Published earlier in June by co-founders Welf and Oliver, it tackles how iOS could help us better protect our attention.
As a designer who cares about and writes about digital wellness, I'm profoundly aligned with their suggestions.
- Persuasive design
- Disclosure requirement
- From infinite feeds to pages
- Was this time well spent?
- Regret tax
- Conditions of use
Clues for software design in how we sketch maps of cities
An Article by Matt WebbGiven there’s an explosion in software to accrete and organise knowledge, is the page model really the best approach?
Perhaps the building blocks shouldn’t be pages or blocks, but
neighbourhoods
roads
rooms and doors
landmarks.Or rather, as a knowledge base or wiki develops, it should - just like a real city - encourage its users to gravitate towards these different fundamental elements. A page that starts to function a little bit like a road should transform into a slick navigation element, available on all its linked pages. A page which is functioning like a landmark should start being visible from two hops away.
Fast Software, the Best Software
An Essay by Craig ModI love fast software. That is, software speedy both in function and interface. Software with minimal to no lag between wanting to activate or manipulate something and the thing happening. Lightness.
Software that’s speedy usually means it’s focused. Like a good tool, it often means that it’s simple, but that’s not necessarily true. Speed in software is probably the most valuable, least valued asset. To me, speedy software is the difference between an application smoothly integrating into your life, and one called upon with great reluctance. Fastness in software is like great margins in a book — makes you smile without necessarily knowing why.
A Plea for Lean Software
An Essay by Niklaus WirthSoftware'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.
Speed is a feature
An Article by Nikita ProkopovMillions of programs have that unfulfilled potential of becoming your second nature, something you don’t even think about when interacting with. They’re waiting to be enabled to “click”. Speed is a feature.
The Great Divide
An Article by Chris CoyierOn one side, an army of developers whose interests, responsibilities, and skill sets are heavily revolved around JavaScript.
On the other, an army of developers whose interests, responsibilities, and skill sets are focused on other areas of the front end, like HTML, CSS, design, interaction, patterns, accessibility, etc.
The care and feeding of software engineers (or, why engineers are grumpy)
An Article by Nicholas ZakasWe do say “no” very quickly, not just to designs, but to everything. That led me into thinking about the psychology of software engineers and what makes us the way we are.
Web Brutalism, seamfulness, and notion
An Essay by Brandon DornHow a tool for sensemaking reconciles two distinct software design ideologies.
- Seamful vs. seamless
- Reveling in infrastructure
- The brilliance of notion
- How our understanding is working
Dear Microsoft
An EssayWe realized a few years ago that the value of switching to Slack was so obvious and the advantages so overwhelming that every business would be using Slack, or “something just like it,” within the decade. It’s validating to see you’ve come around to the same way of thinking. And even though — being honest here — it’s a little scary, we know it will bring a better future forward faster.
However, all this is harder than it looks. So, as you set out to build “something just like it,” we want to give you some friendly advice.
How Microsoft crushed Slack
An Article...and why the era of worker-centered work tools may be over.
Technical debt as a lack of understanding
An Article by Dave Rupert"If you develop a program for a long period of time by only adding features but never reorganizing it to reflect your understanding of those features, then eventually that program simply does not contain any understanding and all efforts to work on it take longer and longer.” — Ward Cunningham
People expect technology to suck because it actually sucks
An Article by Nikita ProkopovI decided to record every broken interaction I had during one day.
If I decided to invest time into thinning this list down, I could theoretically...reduce this list from 27 down to 24. At least 24 annoyances per day I have to live with. That’s the world WE ALL are living in now. Welcome.
Why Software is Slow and Shitty
An Article by Pirijan KetheswaranPlanning 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.
Figma's Engineering Values: Craftsmanship
An ArticleCraftsmanship is about thoughtfulness and care in the work we do. It means being deliberate about what we build and how possible it will be to maintain and extend in the future. A solution that will require revisiting in a month — because it’s not scaling, because it has a ton of bugs, because it doesn’t support all the use cases it needs to — is not useful to us and ultimately will generate pain for our users.
What we trade off by living this value is (sometimes) day-to-day speed. It’s easy to imagine an engineering team that emphasizes moving fast over keeping things stable and bug-free -- like a team building a product that isn’t responsible for important user data and doesn’t support anyone’s livelihood. But given the role the Figma product plays in the lives of our users, we feel it’s worth it to ensure we hold a high quality bar for them. And in the long run, being thoughtful about how we build often reduces the complexity of ongoing development and new features regardless.
On the "Building" of Software and Websites
An Essay by Dorian TaylorI’m beginning to suspect that software, and more conspicuously the Web, is fundamentally the wrong shape for the archetype of the construction project.
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.
Silicon Valley Product Group
A Website by Marty CaganThe best companies go about building great products differently. Silicon Valley Product Group (SVPG) was created to share lessons learned and best practices about how to build innovative products customers love
Like, just a post complaining that screens should be better
An Article by Matt WebbIt’s been 19 years since Pixar released Monsters, Inc. with all that CGI hair. Where are my hairy icons? Ones that get all long and knotted as the notifications number goes up.
Why can’t I feel my phone? I found that paper from 2010 (when I was complaining about keyboards) about using precision electrostatics to make artificial textures on touchscreens.
I should be able to run my thumb over my phone while it’s in my pocket and feel bumps for apps that want my attention. Touching an active element should feel rough. A scrollbar should *slip. Imagine the accessibility gains. But honestly I don’t even care if it’s useful: 1.5 billion smartphone screens are manufactured every year. For that number, I expect bells. I expect whistles.
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.