reading
Books are meant to be used
Wow, that's pretty cool
Why we should read
Narrative codes
A web of books
Silent Conversation
A GameSilent Conversation tells classic stories, poems and haiku in an interactive way, inspired by Walter Savage Landor's motto What is reading but silent conversation?. They are presented as levels where the player controls a small line (similar to a text prompt) to go through the winding words.
Interoperable Personal Libraries and Ad Hoc Reading Groups
An Article by Maggie AppletonWe would need a system that enables people to:
- Publish a list of books they would be willing to discuss with other people to the open web. Antilibraries – collections of books you haven't read yet but would like to read – are particularly well suited to this proposition.
- See which books people in their social network want to discuss, and/or subscribe to other people's lists
- Be notified when 4+ people in their network have the same book on their discussion list – possibly via an email thread?
- Coordinate and schedule a time to read and discuss the book with that group.
If a book can be summarized, is it worth reading?
An Article by Austin KleonIt is my opinion that if a book’s contents can be adequately “summed up,” so that you really don’t miss anything by reading the summary, it is not actually a book worth reading. (Of course, there’s no way to tell whether a summary is adequate or not unless you have also read the book.) Also, I suspect that the harder you find it to summarize a book you have read, the more valuable it might be.
Highlighter
An ApplicationHighlighter is a personal knowledge bank and collaborative learning network designed to feed your curiosity and help you examine new ideas.
Finding nourishment vs. identifying poison
An Article by Austin Kleon & Olivia LaingA useful analogy for what [Sedgwick] calls ‘reparative reading’ is to be fundamentally more invested in finding nourishment than identifying poison. This doesn’t mean being naive or undeceived, unaware of crisis or undamaged by oppression. What it does mean is being driven to find or invent something new and sustaining out of inimical environments.
I would like to adopt that line as a mission statement: “To be fundamentally more invested in finding nourishment rather than identify poison.”
Because you can identify all the poison you want, but if you don’t find nourishment, you’ll starve to death.
Which Books You Truly Love
An Essay by Salman RushdieI believe that the books and stories we fall in love with make us who we are, or, not to claim too much, the beloved tale becomes a part of the way in which we understand things and make judgments and choices in our daily lives. A book may cease to speak to us as we grow older, and our feeling for it will fade. Or we may suddenly, as our lives shape and hopefully increase our understanding, be able to appreciate a book we dismissed earlier; we may suddenly be able to hear its music, to be enraptured by its song.
Of Note: Better Text Annotations for the Web
An Article by Brandon DornGenerally speaking (and ignoring questions of styling, API availability, etc.), an ideal Web annotation pattern follows these principles:
- Annotations appear in close visual proximity to the primary content.
- Their design neither distracts from nor hides the primary content.
- The preceding principles are followed regardless of screen width.
The only pattern I’ve found that meets these criteria is FiveThirtyEight’s.
...As it turns out, FiveThirtyEight didn't invent this pattern. It likely originated in medieval illuminated manuscripts which contain “interleave notes” — comments written literally between the lines.
What 80% Comprehension Feels Like
An ArticleOne of the major principles of extensive reading is that if a learner can comprehend material at 98% comprehension, she will acquire new words in context, in a painless, enjoyable way. But what is 98% comprehension?
The case for rereading
An Article by Mandy BrownReread a book enough times, or often enough—keep it at hand so you can flip to dog-eared pages and marked up passages here and there—and it will eventually root itself in your mind. It becomes both a reference point and a connector, a means of gathering your knowledge and experience, drawing it all together. It becomes the material through which you engage with the world.
The most interesting things that come to mind
A Fragment by Nabeel QureshiA meta note, inspired both by Proust and by this book about Proust: after reading a book, when you're making notes, don't refer to the book; just write down the most interesting things that come to mind. This is a better way of digging out what actually struck you about the book; as soon as you have the book to reference, you will start looking up the bits you "should" write about, and end up aiming at comprehensiveness rather than interestingness. Your actual criterion should be whatever interested you. Later, you can fill in quotations & references.
Title Cities
An Artwork by Nicholas RougeuxA book’s title page contains more than its namesake—including its author, contributors, publisher, and release date, and. Antiquarian books are known for having lengthy titles, especially those of a scientific nature. These books’ frequently unassuming title pages are gateways to a wealth of knowledge and the focal point of this project.
Title pages of antique influential scientific books covering a variety of subjects were coded and reimagined as colorful cityscapes based solely on their words to illustrate the unique body of knowledge readers would find within.
Boxes were drawn around each word of a title page and color-coded by its first letter (words beginning with “A” are one color, “B” another, and so on). Each title page has its own palette. Those boxes were then upended and arranged to form an abstract cityscape while maintaining their original sizes relative to each other.
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?