language
Spike and spon
The pernicious issue with pangrams
The language itself has been weaponized
It’s quite difficult, to fight back against the seeming wisdom of axiomatic “truths,” when the language itself has been weaponized through the power of pattern. Through rhythm, rhyme, alliteration, and consonance.
The last time I was in England was at the invitation of Nomensa, to give a talk at a conference wherein I encouraged the audience to discard an axiom that I feel has done users of the English language more harm than good through endless and glib repetitions.
Like “Curiosity Killed The Cat,” “You Are Not Your User” sounds so good that we keep on saying it, without appreciating what we’re reifying through repetition. The pleasure of repetition, the pleasure of pattern matching, the pleasingness of Kuh Kuh Kuh consonants on the one hand, and of the round vowelly Yuh Yuh Yuh on the other make these things we say seem true because they sound and feel so good to say.
The fire of oak logs
The fire of oak logs which burned day and night for six months became the focal point of our family life.
...It is inevitable that the English word "home" cannot be translated directly into French. The nearest equivalent in French is the word foyer, the hearth.
Nominalization
The English language provides bad writers with a dangerous weapon called nominalization: making something into a noun.
Instead of affirming an idea, you effect its affirmation; rather than postponing something, you implement a postponement.
"Comprehension checks were used as exclusion criteria” would be better said as “we excluded people who failed to understand the instructions.”
“There is not any anticipation there will be a cancellation” would be better as “I don’t anticipate that I will have to cancel.”
Zombie sounds, unlike the verbs whose bodies they snatched, can shamble around without subjects. That is what they have in common with the passive constructions that also bog down these examples.
The arbitrariness of the sign
A key difference between verbal language and the modernist ideal of a visual “language” is the arbitrariness of a verbal sign, which has no natural, inherent relationship to the concept it represents. The sound of the word “horse”, for example, does not innately resemble the concept of a horse. Ferdinand de Saussure called this arbitrariness the fundamental feature of the verbal sign. The meaning of a sign is generated by its relationship to other signs in the language: the sign’s legibility lies in its difference from other signs.
The demand of a new word
Why are these phonosemantic classes enough, and we need neither more nor less? Why are these consonants enough, and we need neither more nor less? What determines the need for a new word? How is this demand ‘felt’ by a language? How did the metabolic pathways of American English recognize that ‘jerk’ and ‘twerp’ and ‘punk’ and ‘nitwit’ and ‘dork’ and ‘ass’ and ‘goon’ and ‘twit’ and ‘dodo’ and ‘bum’ and ‘nerd’ and ‘dunce’ and ‘turd’ and ‘boob’ and ‘chump’ and ‘bitch’ and ‘bastard’ and ‘prude’ and so on and so forth simply were not equal to the task? We had to add ‘turkey’ and ‘squirrel’ as well?
Scooting over
There is at this point no evidence that acquired characteristics can be inherited. It is held that all changes to a genome are random, and cannot be subject to any higher principle. However, when a word is used in a new context, as it is whenever we say something new, a new sense is permitted. This does affect the phonosemantic structure, the linguistic DNA. Words in the vicinity of this word ‘scoot over’ to make room and allow themselves to be influenced by its philosophy. The language itself is now different.
We must go with them
"You cannot make what you want to make, but what the material permits you to make. You cannot make out of marble what you would make out of wood, or out of wood what you would make out of stone. Each material has its own life, and one cannot without punishment destroy a living material to make a dumb senseless thing. That is, we must not try to make our materials speak our language, we must go with them to the point where others will understand their language."
— Constantin Brancusi
The receiving end
At times it helps to rephrase an observation in line with a perspective from the receiving end of technology. When my colleagues in the field of cold-water engineering speak of "ice-infested waters", I am tempted to think of "rig-infested oceans". Language is a fine barometer of values and priorities. As such it deserves careful attention.
The language of art
Everything points to the conclusion that the phrase 'the language of art' is more than a loose metaphor, that even to describe the visible world in images we need a developed system of schemata.
You're Probably Using the Wrong Dictionary
An Essay by James SomersBook from the Ground: From Point to Point
A Novel by Bing Xu- z-z-z
In Defense of Browsing
An Essay by Leanne ShaptonThe feeling of fortuitous gratitude at coming across unexpected information is something most of us who’ve done any research, have experienced — that kismet of finding the perfect book, one spine away from the one that was sought. In the field of art and image research, this sparking of transmission, of sequence and connection, happens on a subconscious level.
…Why is the vernacular image still being dismissed as ephemera? Why is its study not being prioritized? All languages are alive, but visual language is galactic. Keywords are not eyeballs, and creating rutted pathways to follow is the antithesis of study. A century of visual language, knowledge, and connectivity is marching toward a narrow, parsimonious basement of nomenclature. The NYPL takes a step backward if it models its shelves and research on a search engine. Spontaneity is learning. Browsing is research.
There Is No Word
A Poem by Tony Hoaglandwhat I already am thinking about
is my gratitude for language—
how it will stretch just so much and no farther;how there are some holes it will not cover up;
how it will move, if not inside, then
around the circumference of almost anything—how, over the years, it has given me
back all the hours and days, all the
plodding love and faith, all themisunderstandings and secrets
I have willingly poured into it.Idiolect
A DefinitionIdiolect is an individual's unique use of language, including speech. This unique usage encompasses vocabulary, grammar, and pronunciation.
An idiolect is the variety of language unique to an individual. This differs from a dialect, a common set of linguistic characteristics shared among a group of people.
Tortured phrases
An Article by Holly ElseIn April 2021, a series of strange phrases in journal articles piqued the interest of a group of computer scientists. The researchers could not understand why researchers would use the terms ‘counterfeit consciousness’, ‘profound neural organization’ and ‘colossal information’ in place of the more widely recognized terms ‘artificial intelligence’, ‘deep neural network’ and ‘big data’.
Further investigation revealed that these strange terms — which they dub “tortured phrases” — are probably the result of automated translation or software that attempts to disguise plagiarism. And they seem to be rife in computer-science papers.
Poison sniffers
An Article by Austin KleonChristopher Johnson says “prescriptivists” or “Cute Curmudgeons” — people who are interested in only policing usage and grammar rules — are “linguistic poison sniffers.” They turn language into “a source of potential embarrassment rather than pleasure.”
Johnson sees his job as getting people to love and appreciate language by being curious about and paying attention to “what makes language delicious.”
This reminded of Olivia Laing’s distinction between identifying poison and finding nourishment.
Everywhere you look these days, there are lots of poison sniffers, but very few cooking a delicious meal…
What happened when I stopped using Emojis
An Article by Clo S.In March 2021, I went through a fun self-imposed experiment: no emoji for 2 weeks. Not on social media, not in private messages, not even as Slack or Discord reactions. No emoticon either: the goal was to communicate without illustrations, only with words. I did a semi-rigorous (a.k.a. half-assed) diary study, taking notes on my feelings and behaviour.
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 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?