Writing & Expression: Nature WritingDiscipline of Observation · Sense of Place · Thoreau's Move · The Ecological Essay
BigCat's Writing
Nature writing seems far from a technical person's work, yet it holds the root lesson behind all good prose: first see accurately, then turn what you saw into thought. It teaches you to sink beneath the abstract slogan to the concrete ground, and to take responsibility for this one place, this one moment. This week, four things from Dillard, Stegner, Thoreau, and Leopold — they will directly sharpen your postmortems, memos, and decision docs.
Principle 01
The Discipline of Observation: If You Can't Write It, You Probably Didn't See It
You Can Only Write What You Notice
Nature · Seeing
The Principle + The Master's Words
The raw material of prose is observation, not ideas. You see only what you call your attention to; what you never noticed, no amount of style can render.
"Seeing is of course very much a matter of verbalization. Unless I call my attention to what passes before my eyes, I simply won't see it."
— Annie Dillard, Pilgrim at Tinker Creek (1974)
Why It Works
Dillard sat by Tinker Creek for a year practicing "to name is to see": only what you find a word for truly enters awareness. The most common emptiness in technical writing isn't a failure of expression but of observation — you write the model of the system in your head, not its actual behavior. "Performance isn't great" is not-looking; opening the dashboard, reading the trace, watching the replay is looking. Observe well, and the words turn concrete on their own.
Before → After
Performance hasn't been great lately, and users have complained a bit.Over two weeks, P99 latency rose from 180ms to 640ms (dashboard link); "lag" appeared 47 times in support tickets, 3× last month.
The onboarding flow has some friction.In ten session replays, six new users paused over 20 seconds on the email-verification step, and three abandoned there.
When to Use + Common Mistakes
✓ Postmortems, root-cause analysis, user research — anywhere "get the facts straight before writing" applies
✗ Mistake: skipping observation and jumping to a verdict — guesswork dressed as a conclusion
✗ Mistake: using "some / a bit / to a degree" to hide that you never looked closely
✗ Mistake: looking only at the one thing that confirms your hypothesis, then stopping
This Week's Exercise + Reflection
Pick a corner you pass daily but never study — out the window, on your commute. Sit five minutes and write 150 words of only what you actually see (light, motion, sound, change), no impressions. Then bring that "look first, then write" to the opening of your next report.
Reflection: When you must conclude about something you never witnessed firsthand, how do you let the reader tell "what I saw" from "what I inferred"?
Principle 02
Sense of Place: Write "This One Spot," Not "Nature"
Specificity Grounds Meaning
Nature · Concrete
The Principle + The Master's Words
Meaning lives not in the abstract "nature" but in a specific place repeatedly lived and named. The more concrete the place, the more weight the words carry.
"A place is not a place until people have been born in it, have grown up in it, lived in it, known it, died in it — have both experienced and shaped it."
— Wallace Stegner, "The Sense of Place" (1992)
Why It Works
"Nature," "ecology," "scalability," "user experience" are abstract buckets — everyone nods, no one remembers. The opposite of a sense of place is the placeless argument: true everywhere, and so cared about nowhere. To make a reader care about a place, Stegner says, first give it a name, coordinates, a specific moment. Same for docs: don't write "the system," write "the orders service at 21:00 on peak night"; don't write "a cost problem," write "the $600 this one query burns every day." Concreteness is what bites.
Before → After
The forest is full of life, and the scenery is beautiful.On a July afternoon, cottonwood fluff drifted on Tinker Creek, and a thrush on the empty bank sang the same phrase over and over for a full quarter hour.
We have some scalability concerns with the database.The orders database tops out at 12k writes/sec; last Singles' Day it hit 18k at 21:00 and shed 4% of writes. That is the specific mountain we have to climb.
When to Use + Common Mistakes
✓ Decision memos, problem statements, promo packets — any opening meant to make the reader care
✗ Mistake: piling on abstract nouns (enable, ecosystem, resilience) that sound big but never land
✗ Mistake: thinking "concrete" means "wordy" — concrete is often shorter and sharper
✗ Mistake: numbers without a scene — the reader knows "how much" but not "where, when"
This Week's Exercise + Reflection
Take a recent abstract claim of yours ("we need to improve X") and nail it to a specific place and moment: which system, which day, what number, who is affected. Watch it turn from a slogan into a mountain you can actually climb.
Reflection: Extreme specificity costs generality. When should you stay in the concrete, and when climb up to a principle?
Principle 03
Thoreau's Move: From a Blade of Grass to a Truth
From the Concrete to the Universal
Master · Demo
The Principle + The Master's Words
What makes a nature essay thought rather than scenery is a single move: leaping from one concrete observation to a universal truth. Thoreau is the patriarch of that leap.
"I went to the woods because I wished to live deliberately, to front only the essential facts of life... Our life is frittered away by detail... Simplify, simplify."
— Henry David Thoreau, Walden (1854)
Why It Works
Thoreau's prose always has its feet in the mud and its head in the stars: he hands you an intensely concrete image (counting beans, listening to ice crack, listing his furniture), then vaults from it to a verdict on how to live. This is also the shape of a good memo — verifiable observation at the base, a memorable principle at the top, joined by one honest leap. Concrete alone is a logbook; abstract alone is hot air; connect them and the writing is both credible and forceful.
Universal: "Simplify, simplify" — most busyness is self-justification
↑ the leap (honest induction)
Middle: nine in ten meetings exist to justify one another
↑
Concrete: I cut my weekly meetings from 14 to 4
Thoreau's move — from the concrete underfoot to the truth overhead; drop a rung and it won't stand
Before → After
We should focus on what truly matters and cut the rest. Less is more.I cut my weekly meetings from 14 to 4. Week one I panicked; by week three I saw it: the other 10 existed mostly to justify one another.
Our lives are too busy and full of distractions.I counted my recurring meetings: fourteen. I kept four. The other ten, I found, existed mostly to justify one another.
When to Use + Common Mistakes
✓ Essays, leadership writing, principles — any "see the large in the small" expression
✗ Mistake: tossing out a slogan with no concrete (a castle in the air) — the reader won't believe it
✗ Mistake: piling detail with no payoff (a logbook) — the reader can't find the "so what"
✗ Mistake: a dishonest leap — forcing a grand conclusion from a single special case
This Week's Exercise + Reflection
Pick a small concrete thing from your week (a merge, a feature you deleted, a hard email). Describe it plainly in 80 words, then leap in one sentence to a universal truth you actually believe. Check whether that leap is honest.
Reflection: The biggest risk of "the large in the small" is overgeneralizing. How do you judge whether one concrete example can carry the universal conclusion you want to draw?
Principle 04
The Ecological Essay: Think Like a Mountain About Second-Order Effects
Thinking in Systems and Second-Order Effects
Nature · Systems
The Principle + The Master's Words
The core of ecological writing is the systems view: no change is isolated; every act travels down the chain to a place you weren't looking. Writing's job is to make that chain visible.
"I now suspect that just as a deer herd lives in mortal fear of its wolves, so does a mountain live in mortal fear of its deer."
— Aldo Leopold, "Thinking Like a Mountain", A Sand County Almanac (1949)
Why It Works
Leopold shot the wolves, thinking he helped the deer; the deer, unchecked, exploded and stripped the whole mountain bare. "Thinking like a mountain" means stretching time and widening the boundary to see second- and third-order consequences. This blind spot is everywhere in tech decisions: optimize one endpoint, shove the load downstream; kill the limiter, faster today and collapsing by quarter's end. A good decision doc writes not only "what this change does" but "down which chain it will travel." Here writing is an ethic: seeing, on the reader's behalf, the far place they cannot.
shoot wolves→deer explode→mountain stripped→deer starve too
First order looks helpful; third order wrecks the whole — push the chain two rungs further
Before → After
This change cuts the endpoint's response time by 40ms. Recommend shipping.The endpoint gets 40ms faster, but it pushes retry load onto the downstream auth service — first-order speedup, second-order risk of overwhelming auth. Recommend shipping, but add backoff and a limiter on auth.
Removing the rate limiter will improve latency.Removing the limiter cuts latency today; by next quarter the unthrottled retries will erode the very capacity it freed — shooting the wolves to save the deer.
When to Use + Common Mistakes
✓ Decision memos, architecture proposals, impact assessments — any "change one thing, move the whole" call
✗ Mistake: writing only the first-order gain, never the second-order cost (optimism bias)
✗ Mistake: writing the system as an isolated module, ignoring its coupling up- and downstream
✗ Mistake: pushing the chain too far with no evidence, sliding into alarmism — back each rung with proof
This Week's Exercise + Reflection
Take a change you're pushing. Write its first-order effect, then force yourself two rungs further: who's affected, what pushes back, where the chain leads in six months. Put those two rungs in your proposal, even if the conclusion stays the same.
Reflection: Second-order effects often can't be proven, only predicted. How do you hold the line between "responsibly warning" and "crying wolf"?
Deeper Questions
"Observe before writing" sounds like slowing down, but work demands speed. Do the discipline of observation and efficiency conflict?
They don't — observation is the precondition of efficiency. Speed without observation is shipping guesswork as conclusions, and everyone downstream pays for your vagueness; rework costs far more than the extra ten minutes of looking. The real waste isn't observing, it's "fast and wrong." A workable middle: match observation depth to reversibility. Reversible small things, look once and write; irreversible big calls deserve, like Dillard, a longer sit by the creek.
Sense of place stresses the concrete; the Pyramid Principle (Day 2) stresses leading with the abstract conclusion. Do they contradict?
Different layers, no contradiction. The pyramid governs order — conclusion first, kind to busy readers. Sense of place governs texture — wherever the conclusion sits, it must be nailed to a concrete place and time. The best writing stacks both: open with a conclusion so concrete it stings ("orders shed 4% of writes on peak night") — first AND grounded. Structure is abstract; content is concrete.
How does nature writing's plain description differ in Chinese versus English?
The English tradition (Dillard, Leopold) drives with precise verbs and concrete nouns, often with the cool of scientific observation. Chinese plain description has another source — the plants of the Book of Songs, Liu Zongyuan's landscapes, Wang Zengqi's grasses and insects — working by the juxtaposition of named things and by white space, meaning emerging without being spelled out. The shared enemy is adjectives and set phrases: "teeming with life," "birdsong and flowers" pre-package the verdict for the reader, which is to write nothing. Chinese plain description especially must dare the plainest verbs and the most concrete things.
Could "thinking like a mountain" about second-order effects trap you in analysis paralysis, afraid to act?
It can, if misused. Leopold didn't mean "compute every consequence before acting" (impossible); he meant "don't decide on first order alone." In practice, set a depth limit: push two rungs down, write the most likely blowback into the doc, and pair it with "if it happens, here's our response." This actually frees you to act — you've pre-installed the brakes. Paralysis comes from infinite extrapolation; decisiveness comes from "two rungs plus a contingency."
Nature writing is almost always slow, personal, first-person. Can this craft serve team, formal technical docs?
Yes — but transfer the underlying lessons, not the genre. Technical docs need no lyricism, but they badly need accurate observation (Dillard), concrete place (Stegner), the honest leap from example to principle (Thoreau), and the systemic second-order view (Leopold). Strip those four from their lyrical shell and they are the skeleton of a good postmortem. Nature writing's true legacy is an attitude — look hard at the world, then set it down honestly — and that is of one root with the most rigorous engineering writing.