Upstream Color Original Soundtrack Leaves Expanded May Be Prevailing Blue Mixed With Yellow Of The Sand I Used To Wonder At The Halo Of Light Around My Shadow And Would Fancy Myself One Of The Elect Fearing That They Would Be Light-headed For Want Of Food And Also Sleep Stirring Them Up As The Keeper Of A Menagerie His Wild Beasts The Finest Qualities Of Our Nature Like The Bloom On Fruits Can Be Preserved Perhaps The Wildest Sound That Is Ever Heard Here Making The Woods Ring Far And Wide I Love To Be Alone A Young Forest Growing Up Under Your Meadows Their Roots Reaching Quite Under The House The Rays Which Stream Through The Shutter Will Be No Longer Remembered When The Shutter Is Wholly Removed After Soaking Two Years And Then Lying High Six Months It Was Perfectly Sound Though Waterlogged Past Drying The Sun Is But A Morning Star A Low And Distant Sound Gradually Swelling And Increasing As If It Would Have A Universal And Memorable Ending A Sullen Rush And Roar Shane Carruth, Upstream Color www.discogs.com WaldenI love to be alone euphonynaturelonelinessmelancholysoundending
To know the place for the first time We shall not cease from exploration And the end of all our exploring Will be to arrive where we started And know the place for the first time. T.S. Eliot, Little Gidding The Dark Tower timecyclesendingexploration
She was wanting to break it off One summer morning, the beginning of July, I got this long letter from my girlfriend, and in it she’d written that she wanted to break up with me. I’ve always felt close to you, and I still like you even now, and I’m sure that from here on I’ll continue to…et cetera, et cetera. In short, she was wanting to break it off. She had found herself a new boyfriend. I hung my head and smoked six cigarettes, went outside and drank a can of beer, came back in and smoked another cigarette. Then I took three HB pencils I had on my desk and snapped them in half. It wasn’t that I was angry, really. I just didn’t know what to do. In the end, I merely changed clothes and headed off to work. And for a while there, everyone within shouting distance was commenting on my suddenly “outgoing disposition”. What is it about life? Haruki Murakami, The Last Lawn of the Afternoon ending
Until we leave the gate behind And yet the timeless way is not complete, and will not fully generate the quality without a name, until we leave the gate behind. Indeed this ageless character has nothing, in the end, to do with languages. The language, and the processes which stem from it, merely release the fundamental order which is native to us. They do not teach us, they only remind us of what we know already, and of what we shall discover time and time again, when we give up our ideas and opinions, and do exactly what emerges from ourselves. At this final stage, the patterns are no longer important: the patterns have taught you to be receptive to what is real. It is the gate which leads you to the state of mind, in which you live so close to your own heart that you no longer need a language. This is the final lesson of the timeless way. Christopher Alexander, The Timeless Way of Building The natural thing to do zenending
A circle of beads If you count off a circle of beads, you never reach an end. At what point, and with what feelings, would his fingers cease to move those beads? This may be a silly question, but it haunts me. Natsume Sōseki, Kokoro ending
Now get inside You say the ocean's rising like I give a shit You say the whole world's ending, honey, it already did You're not gonna slow it, Heaven knows you tried Got it? Good, now get inside Bo Burnham, Bo Burnham: Inside genius.com ending
When life is over At the end, which is when life is over, death removes all the clothing that differentiated them, and all are equal in the grave. Miguel de Cervantes, Don Quixote deathstatusending
That funny feeling That unapparent summer air in early fall The quiet comprehending of the ending of it all There it is again That funny feeling Bo Burnham, Bo Burnham: Inside genius.com ending
You can get anywhere from anywhere And if you can get anywhere from anywhere, You can start anywhere And end anywhere. There is no single necessary order. Verlyn Klinkenborg, Several Short Sentences About Writing progressending
Ending is better than mending “We always throw away old clothes. Ending is better than mending, ending is better than mending, ending is better…” Aldous Huxley, Brave New World noveltyrepairtrashwastemelancholyending
Graceful Exits: How Great Beings Die A Book by Sushila Blackman Japanese Death PoemsHe only who has lived with the beautiful exitsdeathending
How do you know when your paintings are finished? A Quote by Gerhard Richter matthiasott.com When nothing disturbs me and I have no idea what to do more, what I could add or destroy. This is very surprising, often, when I’m painting, again and again, every day and it feels like it is never-ending […] and it will never become a good painting. And suddenly, it’s finished. Oh! Good. Thanks. Painting With the Web perfectionprogressending
Exit pages An Idea by Brad Enslen ramblinggit.com Today I made an Exit page. So many people end their visit by hitting the Back button on their browser. The exit page is a last attempt to get them to explore the Blog Directory to find an entertaining blog. Or failing that to try a search on a search engine they may have never tried before. exitswwwfunwhimsyending
The Design of Design A Book by Frederick P. Brooks, Jr. www.goodreads.com Design process models: A summary argumentThe spiral modelA grossly obese set of requirementsRequirements proliferationThe architectural contracting model+9 More Design System as Style Manual With Web Characteristics designsoftwarearchitecturemakingstyle
What's Wrong With This Model? A Chapter What's wrong with the rational modelDeciding what to designEvaluating goodnessChanging constraintsThey just don't work that way+1 More
Design 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. design
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 proliferationA Plea for Lean Software features
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. YagniA grossly obese set of requirementsFeatures and complexity features
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. Large combinatorial spacesThe ordering of steps
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. Senior craftsperson work
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. Dependence is more profitable than educationI mix it with two in my thought
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. Everything has been composed making
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. Design with courage design
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? designteamwork