You’re writing a book. Or a technical manual. Or an advertisement. Whatever you’re writing, you have a key point you want the reader to come away with. “The revolution of October 1917 was inevitable.” “The central algorithm in the system is RSA.” “Zonko is better than Zarko.” Whatever your point is, to teach your reader of it, you should repeat that point throughout!
The reader leaves your writing with very little retained. You must make sure that your key point is one of those retained items. But there are many ways to emphasize your key point:
- Say it up-front: put your important point at the beginning, in an introduction.
- Say it LOUD: put your important point in a big 48pt header.
- Say it repeatedly: put your important point several times throughout.
I want to emphasize the last method: say it repeatedly! If, like me, you’re an engineer, you have a bias against repetition. You think that concision is a virtue. You think that repetition is redundancy, to be squeezed out. Well, it’s not. Repetition serves a purpose. Repetition is your most powerful tool, because all that matters is what the reader remembers when they leave, and repetition is the most powerful way to remember.
Why do you remember your name and birthdate? Not because you were told them at birth, but because you’ve had to recall them thousands of times. Why do you remember the flags for curl
? Not because you read the man page, but because you repeatedly consulted that man page every time you used it. Why do you remember the lyrics of Tubthumping? Not because Chumbawumba shouted the chorus at you (although they did), but because they repeated that infernal chorus twenty-seven times every time the song was played.
The state-of-the-art technique for memorization is spaced repetition, used by tools like Memrise, Duolingo, and Anki. One key word there is repetition, but the other key word is spaced. You did not have to write your name thousands of times on a chalkboard one day in childhood; instead, you have had to recall your name most days when talking to people and filling out forms. You did not lock yourself in a room with the man page for curl
, repeatedly reading it until it was committed to memory; instead, you consulted it each time you used curl
. The lyrics of Tubthumping are burned into your mind not just because they are repeated throughout the song, but also because the song was on the radio all through 1997.
To get your point across, it’s not enough to just repeat it. That repetition must be appropriately spaced. How do we space out our writing? Above, I illustrated a few communication strategies. At the top, we have the “Man page” approach: terse, concise, no repetition. This is the approach that many engineers want to take when explaining something. It’s too terse for most people, and does not result in good recall after reading. A naïve expansion of this approach results in the second diagram: the writing proceeds logically from beginning to end. In the naïve approach, there’s more time for the reader to ruminate, but such rumination is not aided by the writer. The ends of the writing, at the start and end, trail off, loose and frayed. This is why schools teach the “shit sandwich” approach: stick a summary at the start and the end (calling them an “introduction” and “conclusion”). There is at least some repetition and recall in the shit sandwich, but the reader still has to wade through a lot of shit to get there.
I think “good” writing uses some kind of fractal approach to repetition. The overall structure is that of the naïve approach, but with many opportunities for recall, at many levels of detail. Each repetition is colored by the general position in the text: what the reader has already read, what they trust they’ll soon read, and how it relates to the overall structure. By the end, the reader is acquainted with your overall argument, because she has read it many times and considered it from different angles.
Repetition is recall!
Tagged .
Similar posts
More by Jim
What does the dot do in JavaScript?
foo.bar
, foo.bar()
, or foo.bar = baz
- what do they mean? A deep dive into prototypical inheritance and getters/setters. 2020-11-01
Smear phishing: a new Android vulnerability
Trick Android to display an SMS as coming from any contact. Convincing phishing vuln, but still unpatched. 2020-08-06
A probabilistic pub quiz for nerds
A “true or false” quiz where you respond with your confidence level, and the optimal strategy is to report your true belief. 2020-04-26
Time is running out to catch COVID-19
Simulation shows it’s rational to deliberately infect yourself with COVID-19 early on to get treatment, but after healthcare capacity is exceeded, it’s better to avoid infection. Includes interactive parameters and visualizations. 2020-03-14
The inception bar: a new phishing method
A new phishing technique that displays a fake URL bar in Chrome for mobile. A key innovation is the “scroll jail” that traps the user in a fake browser. 2019-04-27
The hacker hype cycle
I got started with simple web development, but because enamored with increasingly esoteric programming concepts, leading to a “trough of hipster technologies” before returning to more productive work. 2019-03-23
Project C-43: the lost origins of asymmetric crypto
Bob invents asymmetric cryptography by playing loud white noise to obscure Alice’s message, which he can cancel out but an eavesdropper cannot. This idea, published in 1944 by Walter Koenig Jr., is the forgotten origin of asymmetric crypto. 2019-02-16
How Hacker News stays interesting
Hacker News buried my post on conspiracy theories in my family due to overheated discussion, not censorship. Moderation keeps the site focused on interesting technical content. 2019-01-26
My parents are Flat-Earthers
For decades, my parents have been working up to Flat-Earther beliefs. From Egyptology to Jehovah’s Witnesses to theories that human built the Moon billions of years in the future. Surprisingly, it doesn’t affect their successful lives very much. For me, it’s a fun family pastime. 2019-01-20
The dots do matter: how to scam a Gmail user
Gmail’s “dots don’t matter” feature lets scammers create an account on, say, Netflix, with your email address but different dots. Results in convincing phishing emails. 2018-04-07
The sorry state of OpenSSL usability
OpenSSL’s inadequate documentation, confusing key formats, and deprecated interfaces make it difficult to use, despite its importance. 2017-12-02
I hate telephones
I hate telephones. Some rational reasons: lack of authentication, no spam filtering, forced synchronous communication. But also just a visceral fear. 2017-11-08
The Three Ts of Time, Thought and Typing: measuring cost on the web
Businesses often tout “free” services, but the real costs come in terms of time, thought, and typing required from users. Reducing these “Three Ts” is key to improving sign-up flows and increasing conversions. 2017-10-26
Granddad died today
Granddad died. The unspoken practice of death-by-dehydration in the NHS. The Liverpool Care Pathway. Assisted dying in the UK. The importance of planning in end-of-life care. 2017-05-19
How do I call a program in C, setting up standard pipes?
A C function to create a new process, set up its standard input/output/error pipes, and return a struct containing the process ID and pipe file descriptors. 2017-02-17
Your syntax highlighter is wrong
Syntax highlighters make value judgments about code. Most highlighters judge that comments are cruft, and try to hide them. Most diff viewers judge that code deletions are bad. 2014-05-11
Want to build a fantastic product using LLMs? I work at
Granola where we're building the future IDE for knowledge work. Come and work with us!
Read more or
get in touch! This page copyright James Fisher 2017. Content is not associated with my employer. Found an error? Edit this page.