media
More that can be done
Reveling in infrastructure
Logjam
- That there is a big danger in working in a single medium. The logjam you don’t even know you’re stuck in will be broken by a shift in representation.
Information Landscapes
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.
Art is the one medium in which one cannot lie successfully
When we build, say, a business area in which all (or practically all) are engaged in earning their livings, or a residential area in which everyone is deep in the demands of domesticity, or a shopping area dedicated to the exchange of cash and commodities—in short, where the pattern of human activity contains only one element, it is impossible for the architecture to achieve a convincing variety—convincing of the known facts of human variation. The designer may vary color, texture and form until his drawing instruments buckle under the strain, proving once more that art is the one medium in which one cannot lie successfully.
Constrained by the medium
The inevitable reciprocation that occurs between the act of drawing and the thinking associated with it. The hand moves, the mind becomes engaged, and vice versa. We might ask: How much does the medium of expression actually constrain a design process?
A medium has a way of constraining our choices, and this influence may not involve conscious choice at all. The planner, in the end, sees and understands only those things for which they can provide expression.
Conventions of a medium
When a new medium borrows from an existing one, some of what it borrows makes sense, but much of the borrowing is thoughtless, “ritual,” and often constrains the new medium. Over time, the new medium develops its own conventions, throwing off existing conventions that don’t make sense.
If you ever get the chance to watch early television drama you’ll find a strong example of this. Because radio required a voice-over to describe what listeners couldn’t see, early television drama often featured a voice over, describing what viewers could. It’s a simple but striking example of what happens when a new medium develops out of an existing one.
Thoughts On Shitpost Diplomacy
An Article by Tanner GreerThat our diplomat’s first impulse is to resort to a self-defeating meme speaks to a broader problem—the sort of cultural problem instinctual reactions to crisis make most clear. This is a problem of an entire generation—my generation. We are a people that retweets when we could be reading. The minds of best and our brightest have been poisoned by ratios, “god tweets,” and memes. We came of age on Twitter, Tumblr, and 4chan, and still see the world through their frames. We find it harder and harder to distinguish the actual from the image; we struggle to disentangle perception management from problem management. This is what it looks like when the terminally online ascend to positions of real responsibility. Welcome to the age of shitpost diplomacy.
A bad tweet is like a deepfake of an idea
A Fragment by Ryan BroderickI guess what you’re describing is like a tweet that hits the uncanny valley of good and bad in such a precise way, with such confidence, that it just pisses everybody off.
Because if you look at this tweet for just a second you’re like ok, that’s a fine bedroom, but then you look at it, and it starts to unravel in your mind, like trying to remember a dream after you just woke up. And you’re like “what is this?” It’s like a deepfake of a person’s face.
…Ok, I’ve got some fire for you: A bad tweet is like a deepfake of an idea.
The perfect bad tweet is like something you read and you’re like “ok yeah” but then you’re like, “wait…”, and it just starts to come apart in your mind and you’re like that makes no fucking sense, just like this photo of this incredibly bad room.
How to write a high-engagement tweet
An Article by Rach Smith- Pick a stance that that could be mistaken as contrarian, but in reality most people actually agree with.
- Posit your argument as if there are "people" who have been spreading the opposing view. You don't have to be specific about who it is. In fact, they don't actually have to exist.
- Make the subject matter something that people get emotional about: gender inequality in tech, TypeScript vs. JavaScript, hiring processes, etc.
- Watch the engagement from people agreeing with you/bonding over your common enemy roll in.
Coevolution and the bad take machine
An Article by David R. MacIverSo when you have a bad take machine, you get the following processes:
- They make a bad take.
- People are outraged and talk about it.
- The bad take machine likes it and does more of that behaviour in future.
If, on the other hand, they make a take and nobody cares, they do not get reward and the behaviour is selected against.
The behaviours drove the spread of the outrage replicator, and the outrage replicator provides the selection mechanism for the behaviours. Thus, via the spread of our outrage on Twitter, we have operant conditioned the bad take machine into producing worse takes.
Which is to say, it's bad on purpose to make you replicate it.
The medium is the message
A Quote by Marshall McLuhanMonoskop
A WebsiteMonoskop is a wiki for the arts, media and humanities.
Woodblock Prints
An Essay from The Beauty of Everyday Things by Yanagi SōetsuIt seems to me that many printmakers are suffering under a delusion. Looking at current trends, it appears that recent prints are simply copying fine art and painting. Some printmakers are working in the nanga style of painting. Others are attempting to reproduce the effects of oil. Some cleverly contrived prints are often difficult to distinguish from paintings done with a brush. The question arises: Why are these printmakers working in the medium of woodblock printing at all?
For prints to follow in the footsteps of painting has very little meaning. The art of the brush and palette should be left to the brush and palette.
The Design of Design
What's Wrong With This Model?
A ChapterDesign process models: A summary argument
- A formal design process model is needed, to help organize design work, to aid communication in and about projects, and for teaching.
- Having a visual, geometric representation of a design process model is crucial, for designers are spatial thinkers. They will most easily learn, think about, share, and talk in terms of a model with a clear geometric picture.
- The Rational Model of design occurs naturally to engineers.
- The linear, step-by-step Rational Model is highly misleading. It does not reflect what real designers do, or what the best design thinkers identify as the essence of the design process.
- The bad model matters. It has led to the too-early binding of requirements, leading in turn to bloated products and schedule/budget/performance disasters.
- The Rational Model has persisted in practice despite its inadequacies and plenty of cogent critiques. This is because of its seductive logical simplicity, and because builders and clients needs “contracts."
- Several alternative models have been proposed. I find Boehm’s Spiral Model the most promising. We need to keep developing it.
The spiral model
The spiral shape certainly suggests progress. It associates successive repetitions of the same activity. The geometric shape is easily understood and memorable. The model emphasizes prototyping, starting with user-interface prototypes and user testing long before an operational prototype is possible.
Since a development model is principally used by developers, I believe having it designer-centered is entirely appropriate. With Boehm and against Denning and Dragon, I advocate frequent but not continuous interaction with representative users, with successive prototypes as the vehicles.
I strongly believe that way forward is to embrace and develop the Spiral Model.
A grossly obese set of requirements
Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun.
The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing.
Requirements proliferation
Any attempt to formulate all possible requirements at the start of a project will fail and would cause considerable delays. — Pahl and Beitz, Engineering Design
As Project Manager, I had to reject the requirements document as totally impractical, and have a quite small team of architects, marketers, and implementers extract the essence.
Requirements proliferation must be fought, by both birth control and infanticide.
The architectural contracting model
It is the necessity for contracts, whether within an organization or between organizations, that forces the too-early binding of goals, requirements, constraints. The pressure for a complete and agreed-upon set of requirements run into the hard fact, that it is essentially impossible to specify any complete and accurate set of requirements for any complex system except in iterative interaction with the design process.
How have the centuries-old building design disciplines handled this perplexity? Fundamentally, by a quite different contracting model.
- The client develops a program, not a specification, for the building.
- He contracts with an architect, usually on an hourly or percentage basis, for services, not for a specified product.
- The architect elicits from the client, the users, and other stakeholders a more complete program, which does not pretend to be a rigid contractable product specification.
- The architect does a conceptual design that approximates the reconciliation of program and the constraints of budget, schedule, and code. This serves as a first prototype, to be conceptually tested by the stakeholders.
- After iteration, the architect performs design development, often producing more detailed drawings, a 3-D scale model, mockups, and so on. After stakeholder iteration, the architect produces construction drawings and specifications.
- The client uses these drawings and specifications to enter into a fixed-price contract for the product.
Notice how this long-evolved model separates the contract for design from the contract for construction. Even when both are performed by the same organization, this separation clarifies many things.
The rational model of design
Engineers seem to have a clear, if usually implicit, model of the process of design. It is usually an orderly model of an orderly process as the engineer conceives it.
The notion that the design process should be modeled as a systematic step-by-step process seems to have first developed in the German mechanical engineering community.
Herbert Simon independently argues for design as a search process in The Sciences of the Artificial. He was motivated to lay out a strictly rational model of design precisely because such a model was a necessary precursor to automating design. His model remains influential even if today we recognize the "wicked problem" of original design as one of the least promising candidates for AI.
In software engineering, Winston Royce independently introduced a seven-step Waterfall Model to bring order to the process. In fact, Royce introduced his waterfall as a straw man that he then argued against, but many people have cited and followed the straw man rather than his more sophisticated models. Even if ironically, Royce's seven-step model must be considered one of the foundational statements of the Rational Model of Design.
Design process models
Any systematization of the design process is a great step forward compared to "Let's just start coding, or building." It:
- Provides clear steps for planning a design project
- Furnishes clearly definable milestones
- Suggests project organization and staffing
- Helps communication within the design team
- Is readily teachable to novices, and tells novices facing their first design assignments where to begin.
The Rational Model in particular brings yet more advantages. The early explicit statement of goals, secondary desiderata, and constraints helps a team avoid wandering, and it breeds team unification on purposes. Planning the whole design process before starting coding or formal drawings avoids many troubles and much wasted effort. Casting the process as a systematic search of a design space broadens the horizon of the individual designers and lifts their eyes far beyond their previous personal experiences.
But the rational model is much too simplistic, even in Simon's richly developed version.
The dual ladder
The first task for growing designers, as opposed to managers, is to craft a proper career path for them, one whose compensation and sociological status reflect their true value to the creative enterprise. This is commonly called the dual ladder. It it easy to give corresponding salaries to corresponding rungs, but it requires strong proactive measures to give them equal prestige: equal offices, equal staff support, reverse-biased raises when duties change.
Why does the dual ladder need special attention? Perhaps because managers, being human, are inherently inclined to consider their own tasks more difficult and important than design and need to deliberately assess what makes creativity and innovation happen.
A platonic ideal
As the architecture design progressed, I observed what at first seemed quite strange. For the architecture team, the real System/360 was the Design Concept itself, a Platonic ideal computer. Those physical and electrical Model 50, Model 60, Model 70, and Model 90 things under construction out on the engineering floors were but Plato’s shadows of the real System/360. The real System/360’s most complete and faithful embodiment was not in silicon, copper, and steel, but in the prose and diagrams of IBM System/360 Principles of Operation, the programmer’s machine language manual.
I had a similar experience with the View/360 beach house. Its Design Concept came to be real long before any construction began. It persisted through many versions of drawings and cardboard models.
The design concept
Is there positive value to recognizing an invisible Design Concept as a real entity in design conversations? I think so.
First, great designs have conceptual integrity—unity, economy, clarity. They not only work, they delight, as Vitruvius first articulated. We use terms such as elegant, clean, beautiful to talk about bridges, sonatas, circuits, bicycles, computers, and iPhones. Recognizing the Design Concept as an entity helps us to seek its integrity in our own solo designs, to work together for it in team designs, and to teach it to our youth.
Second, talking frequently about the Design Concept as such vastly aids communication within a design team. Unity of concept is the goal; it is achieved only by much conversation.
Thus, moviemakers use storyboards to keep their design conversations focused on the Design Concept, rather than on implementation details.
The Idea
The design is thus the mental formulation, which Sayers calls “the Idea,” and it can be complete before any realization is begun. Mozart’s response to his father’s inquiry about an opera due to the duke in three weeks both stuns us and clarifies the concept.
For most human makers of things, the incompletenesses and inconsistencies of our ideas become clear only during implementation. Thus it is that writing, experimentation, “working out,” are essential disciplines for the theoretician.
The boldest decisions
In retrospect, many of the case studies have a striking common attribute: the boldest design decisions, whoever made them, have accounted for a high fraction of the goodness of the outcome. These bold decisions were made due sometimes to vision, sometimes to desperation. They were always gambles, requiring extra investment in hopes of getting a much better result.
Intuition and systems
Systematic design excluding intuition yields pedestrian follow-ons and knock-offs; intuitive design without system yields flawed fancies. How to weld intuition and systematic approach? How to grow as a designer? How to function in a design team?