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.
The Mind of the Maker
Looking at man, [the author of Genesis] sees in him something essentially divine, but when we turn back to see what he says about the original upon which the “image” of God was modelled, we find only the single assertion, “God created”. The characteristic common to God and man is apparently that: the desire and the ability to make things.
Only in terms of other things
No legislation could prevent the making of verbal pictures: God walks in the garden, He stretches out His arm, His voice shakes the cedars, His eyelids try the children of men. To forbid the making of pictures about God would be to forbid thinking about God at all, for man is so made that he has no way to think except in pictures. But continually, throughout the history of the Jewish-Christian Church, the voice of warning has been raised against the power of the picture-makers: “God is a spirit”, “without body, parts or passions”; He is pure being, “I AM THAT I AM”.
The fact is, that all language about everything is analogical; we think in a series of metaphors. We can explain nothing in terms of itself, but only in terms of other things.
I mix it with two in my thought
It is the artist who, more than other men, is able to create something out of nothing. A whole artistic work is immeasurably more than the sum of its parts.
“I mix it with two in my thought”; this is the statement of the fact of universal experience that the work of art has real existence apart from its translation into material form.
Towards a synthesis of experience
The artist does not recognise that the phrases of the creeds purport to be observations of fact about the creative mind as such, including his own; while the theologian, limiting the application of the phrases to the divine Maker, neglects to inquire of the artist what light he can throw upon them from his own immediate apprehension of truth. The confusion is as though two men were to argue fiercely whether there was a river in a certain district or whether, on the contrary, there was a measurable volume of H2O moving in a particular direction with an ascertainable velocity; neither having any suspicion that they were describing the same phenomenon.
Our minds are not infinite; and as the volume of the world’s knowledge increases, we tend more and more to confine ourselves, each to his special sphere of interest and to the specialised metaphor belonging to it. The analytic bias of the last three centuries has immensely encouraged this tendency, and it is now very difficult for the artist to speak the language of the theologian, or the scientist the language of either. But the attempt must be made; and there are signs everywhere that the human mind is once more beginning to move towards a synthesis of experience.
And these three are one
For every work [or act] of creation is threefold, an earthly trinity to match the heavenly.
First, [not in time, but merely in order of enumeration] there is the Creative Idea, passionless, timeless, beholding the whole work complete at once, the end in the beginning: and this is the image of the Father.
Second, there is the Creative Energy [or Activity] begotten of that idea, working in time from the beginning to the end, with sweat and passion, being incarnate in the bonds of matter: and this is the image of the Word.
Third, there is the Creative Power, the meaning of the work and its response in the lively soul: and this is the image of the indwelling Spirit.
And these three are one, each equally in itself the whole work, whereof none can exist without other: and this is the image of the Trinity.
"The right phrase"
How can we know that the Idea itself has any real existence apart from the Energy? Very strangely; by the fact that the Energy itself is conscious of referring all its acts to an existing and complete whole.
Quite simply, every choice of an episode, or a phrase, or a word is made to conform to a pattern of the entire book, which is revealed by that choice as already existing. This truth, which is difficult to convey in explanation, is quite clear and obvious in experience. It manifests itself plainly enough when the writer says or thinks: “That is, or is not, the right phrase”—meaning that it is a phrase which does or does not correspond to the reality of the Idea.
The argument carried on in a sphere
We need not allow ourselves to be abashed by any suggestion that the old metaphors are out of date and ought to be superseded. We have only to remember that they are, and always were, metaphors, and that they are still “living” metaphors so long as we use them to interpret direct experience. Metaphors only become dead when the metaphor is substituted for the experience, and the argument carried on in a sphere of abstraction without being at every point related to life.
A diversity within its unity
The vital power of an imaginative work demands a diversity within its unity; and the stronger the diversity, the more massive the unity.
The work is what it means
It is desirable to bear in mind—when dealing with the human maker at any rate—that his chosen way of revelation is through his works. To persist in asking, as so many of us do, “What did you mean by this book?” is to invite bafflement: the book itself is what the writer means.
Writing for the stage
From experience I am inclined to think that one reason why writing for the stage is so much more interesting than writing for publication is the very fact that, when the play is acted, the free will of the actor is incorporated into the written character.
In conformity with its proper nature
If the characters and the situation are rightly conceived together, as integral parts of the same unity, then there will be no need to force them to the right solution of that situation. If each is allowed to develop in conformity with its proper nature, they will arrive of their own accord at a point of unity, which will be the same unity that pre-existed in the original idea.
This is my clamhood
It was said, sneeringly, by someone that if a clam could conceive of God, it would conceive of Him in the shape of a great, big clam. Naturally. And if God has revealed Himself to clams, it could only be under conditions of perfect clamhood, since any other manifestation would be wholly irrelevant to clam nature. By incarnation, the creator says in effect: “See! this is what my eternal Idea looks like in terms of my own creation; this is my manhood, this is my clamhood.
Only so much of the mind
Though the autobiography “is” the author in a sense in which his other works are not, it can never be the whole of the author. It is still a formal expression and bound by the limitations of all material form, so that though it is a true revelation it is only a partial revelation: it incorporates only so much of the mind as matter is capable of containing.
To know evil
For to know evil, for them, was to know it not by pure intelligence by by experience.
A time when time was not
Darkness cannot say: “I precede the coming light”, but there is a sense in which light can say, “Darkness preceded me”.
Doubtless there is an event, X, in the future, by reference to which we may say that we are at present in a category of Not-X, but until X occurs, the category of Not-X is without reality. Only X can give reality to Not-X; that is to say, Not-Being depends for its reality upon Being. In this way we may faintly see how the creation of Time may be said automatically to create a time when Time was not, and how the Being of God can be said to create a Not-Being that is not God.
These alien wills
Unfortunately his creation is only safe from the interference of other wills so long as it remains in his head. By materialising his poem—that is, by writing it down and publishing it, he subjects it to the impact of alien wills. These alien wills can, if they like, become actively aware of all the possible wrong words and call them into positive being. They can, for example, misquote, misinterpret, or deliberately alter the poem. This evil is contingent upon the poet’s original good: you cannot misquote a poem that is not there, and the poet is (in that sense) responsible for all subsequent misquotations of his work. But one can scarcely hold him guilty of them.
When we say we know Hamlet
When we say we “know Hamlet”, we do not mean merely that we can memorise the whole succession of words and events in Hamlet. We mean that we have in our minds an awareness of Hamlet as a complete whole—“the end in the beginning”. We can prove this by observing how differently we feel when seeing a performance of Hamlet on the one hand and an entirely new play on the other.
A fresh focus of power
The demand for “originality”—with the implication that the reminiscence of other writers is a sin against originality and a defect in the work—is a recent one and would have seemed quite ludicrous to poets of the Augustan Age, or of Shakespeare’s time. The traditional view is that each new work should be a fresh focus of power through which former streams of beauty, emotion, and reflection are directed. This view is adopted, and perhaps carried to excess, by writers like T. S. Eliot, some of whose poems are a close web of quotations and adaptations, chosen for their associative value, or like James Joyce, who makes great use of the associative value of sounds and syllables.
Some secret stirring in the world
There is some secret stirring in the world,
A thought that seeks impatiently its word.To stand independent of himself
The creator’s love for his work is not a greedy possessiveness; he never desires to subdue his work to himself but always to subdue himself to his work. The more genuinely creative he is, the more he will want his work to develop in accordance with its own nature, and to stand independent of himself.
What can be called a response
With living, though unconscious, matter, the creator must still adapt the work to the material, though here he experiences something that can without undue anthropomorphism be called a “response”; plants “respond” to cultivation and cross-fertilization in a sense rather different from that in which iron may be said to “respond” to hammering.
A passive beauty of right structure
The human maker, working in unself-conscious matter, receives no worship from his creatures, since their will is no part of his material; he can only receive the response of their nature, and he is alone in fault if that response is not forthcoming. If he tortures his material, if the stone looks unhappy when he has wrought it into a pattern alien to its own nature, if his writing is an abuse of language, his music a succession of unmeaning intervals, the helpless discomfort of his material universe is a reproach to him alone; similarly, if he respects and interprets the integrity of his material, the seemliness of the ordered work proclaims his praise, and his only, without will, but in a passive beauty of right structure.
Father-, son-, and ghost-ridden
We may properly and profitably amuse ourselves by distinguishing those writers who are respectively “father-ridden”, “son-ridden”, and “ghost-ridden”.
It is the mark of the father-ridden that they endeavour to impose the Idea directly upon the mind and senses, believing that this is the whole of the work.
Among the son-ridden, we may place such writers as Swinburne, in whom the immense ingenuity and sensuous loveliness of the manner is developed out of all proportion to the tenuity of the ruling idea.
The ghost-ridden writer, on the other hand, conceives that the emotion which he feels is in itself sufficient to awaken response, without undergoing discipline of a thorough incarnation, and without the coherence that derives from reference to a controlling idea. Such a man may write with the tears streaming down his cheeks, and yet produce nothing but turgid rhetoric, flat insipidity, or the absurdities of an Amanda Ros.
Running into the sand
His whole creative history is that of great rivers running into the sand
Not as the scribblers
What writer whose trinity was strongly co-ordinated would even dream of revising his work to conform with the majority report of a committee? Those whose Idea is in full control are especially obstinate and impervious to criticism; for in speaking for the father they speak with authority and not as the scribblers.
Failure in the ghost
Whereas failure in the father may be roughly summed up as a failure in Thought and failure in the son as a failure in Action, failure in the ghost is a failure in Wisdom—not the wisdom of the brain, but the more intimate and instinctive wisdom of the heart and bowels.
The unghosted are not unintelligent, nor yet idle or unskilled; it is simply that there are certain things which they do not know and seem incapable of knowing. Under the terms of our analogy, failure in the ghost is the characteristic failure of the unliterary writer and the inartistic artist.
A distressing trait of the unghosted is their complacency; they walk and talk, and do not know that they are dead. Neither, of course, are they alive to the deadness of their own creation. How should they be? Only the living can draw any distinction between death and life.
Violence to the very structure of our being
If we conclude that creative mind is in fact the very grain of the spiritual universe, we cannot arbitrarily stop our investigations with the man who happens to work in stone, or paint, or music, or letters. We shall have to ask ourselves whether the same pattern is not also exhibited in the spiritual structure of every man and woman. And, if it is, whether, by confining the average man and woman to uncreative activities and an uncreative outlook, we are not doing violence to the very structure of our being. If so, it is a serious matter, since we have seen already the unhappy results of handling any material in a way that runs counter to the natural law of its structure.
It will revenge itself in judgment
To the average man, life presents itself, not as material malleable to his hand, but as a series of problems of extreme difficulty, which he has to solve with the means at his disposal. And he is distressed to find that the more means he can dispose of—such as machine-power, rapid transport, and general civilised amenities, the more his problems grow in hardness and complexity. This is particularly disconcerting to him, because he has been frequently told that the increase of scientific knowledge would give him “the mastery over nature”—which ought, surely, to imply mastery over life.
Perhaps the first thing that he can learn from the artist is that the only way of “mastering” one’s material is to abandon the whole conception of mastery and to co-operate with it in love: whosoever will be a lord of life, let him be its servant. If he tries to wrest life out of its true nature, it will revenge itself in judgment, as the work revenges itself upon the domineering artist.
The solution of the age
The concept of “problem and solution” is as meaningless, applied to the act of creation, as it is when applied to the act of procreation. To add John to Mary in a procreative process does not produce a “solution” of John’s and Mary’s combined problem; it produces George or Susan, who (in addition to being a complicating factor in the life of his or her parents) possesses an independent personality with an entirely new set of problems.
...there is no strictly mathematical or detective-story sense in which it can be said that the works of a poet are the “solution” of the age in which he lived...The artist does not see life as a problem to be solved, but as a medium for creation.
That anything in this world should be inevitable
We do not so much fear the pains of dying, as feel affronted by the notion that anything in this world should be inevitable.
In a day and hour which we know not
“We are at work now upon various devices”, says some harassed spokesman; and the imagination sees “us” industriously assembling the device, as though it had been delivered in parts from a celestial workshop, and had only to be fitted together according to the book of instructions and put into use the same evening. That is not creation’s way. There is the wayward, the unpredictable, the not-to-be-commanded Idea, which may make its presence felt in the mind after long hours of fruitless thought and work, or suddenly after no thought at all, or after a long fallow period of unconsciousness, during which the conscious has been otherwise employed, but always in a day and an hour which we know not.
In terms which must be altered
[Life] frequently sets its problems in terms which must be altered if the problem is to be solved at all.
The unending labour of creation
Now the artist does not behave like this. He may finish a book, as we may finish a war or set up the machinery of a League, and he may think it is very good and allow his Energy a brief sabbath of repose. But he knows very well that this is only a pause in the unending labour of creation.
Each chapter concluded is only a day’s end in the course of the book; each book concluded is only a year’s end in the course of a life’s pilgrimage. Or, if you like the metaphor better, it is a “still” cut out and thrown off from the endless living picture which his creative mind reels out. It is a picture in itself, but it only leads from the picture behind it to the picture in front of it, as part of a connected process.
To see the fulfillment of the work
It is true that [the artist], like everybody else, derives remuneration from his work (though not, strictly speaking, profit in the financial sense, of the word, since what he invests in his work is not money but time and skill, whose returns cannot be calculated in percentages). The remuneration is frequently beyond the amount necessary to enable him to go on working. What is remarkable about him is the way in which he commonly employs the escape-from-work which the extra remuneration allows him. If he is genuinely an artist, you will find him using his escape-from-work in order to do what he calls “my own work”, and nine times out of ten, this means the same work (i.e. the exercise of his art) that he does for money. The peculiar charm of his escape is that he is relieved, not from the work but from the money.
What distinguishes him here from the man who works to live is, I think, his desire to see the fulfilment of the work.