Skip to content

Why Don’t SFF Characters Ever Read the Manual?

18
Share

Why Don't SFF Characters Ever Read the Manual? - Reactor

Home / Why Don’t SFF Characters Ever Read the Manual?
Books Science Fiction

Why Don’t SFF Characters Ever Read the Manual?

By

Published on January 1, 2020

Overlay of mechanical blueprints (Public Domain images)
18
Share
Overlay of mechanical blueprints
Overlay of mechanical blueprints (Public Domain images)

Every so often, I find it entertaining to muse about and lament the ill effects of missing or erroneous documentation. Or the ill effects of failing to read the manual… or, having read it, ignoring its wise advice.

Unsurprisingly, SFF authors have arrived at a consensus as far as technical documentation is concerned: For the most part, they’re against it, at least as part of the setting of the story. There is nothing more encouraging to thrills and spills, exciting disasters and pulse-quickening cliffhangers, than protagonists doing ill-advised things…that is, things that would have been ill-advised if anyone had bothered to write down useful advice. Or if the protagonists had bothered to read such advice.

Of course, there’s some excuse for bold experimentation if the problem, or setting, is brand-new to all involved. Someone actually has to create the documentation later people can use. Thus the situation in Brian Stableford’s Daedalus Mission series—The Florians (1976), Critical Threshold (1977), Wildeblood’s Empire (1977), The City of the Sun (1978), Balance of Power (1979), The Paradox of the Sets (1979). Earth has founded and then abandoned extra-solar colonies. A later expedition finds no survivors. A second expedition, the focus of the series, turns up survivors…and also information which, had it been available back when the colonies were first founded, would have had a profound effect on their survival rate. If only there had been a manual!

Another reason to eschew proper documentation is simple economics. It’s just so much faster and cheaper to let the end users pool their experiences to work out what the heck is happening and why. It’s a philosophy embraced by organizations from roleplaying game companies to my phone service provider. It’s not surprising to see it pop up, then, in SF works like Nnedi Okorafor’s Binti: Home, where new and powerful technology is not accompanied by a useful manual. But at least there are other users to query.

In other stories the manual writers may be long gone and their manuals fallen into dust. Or into the bit bucket. The explorers in Melissa Scott’s Finder are looking for relics of a civilization that may as well have been gods as far as the modern era is concerned. The modern era has enough experience with the materials they salvage from old ruins to have a general idea of how it might behave. This allows for all manner of surprises—some nice, some not so nice. But all very plot-friendly surprises.

Of course, even if the builders have left decent documentation, there’s no reason to think that people will read it. This was a running gag in many of Robert Sheckley’s comedies, in particular the AAA Ace stories. Protagonists Arnold and Gregor—well, Arnold mostly, with poor Gregor dragged along for the ride—go gaga over potentially profitable gadgets or contracts. They…well, again, Arnold mostly…never bother to read manual, or the fine print.

Buy the Book


Network Effect

Then there are the “KEEP OFF! THIS MEANS YOU” notices. All too many well-meaning folks who have managed to seal some dire evil in a can have also decided to mark the spot with large, clearly written warnings intended to repel the curious. These warnings are, alas, archaeologist and treasure-hunter bait par excellence. There is no warning stern enough to keep those fools away. Examples are too numerous to list (but don’t let that stop you from trying in comments): Lost Things by Scott and Graham, A Fire Upon the Deep by Vernor Vinge, The Silver Spike by Glen Cook, and from a certain point of view, Monstress by Marjorie Liu and Sana Takeda.

In such cases, it may seem better NOT to document. Opt for security through obscurity. After all, if people cannot find the Horrible Thing or understand what it is, there is no reason to worry that they will decide to dig it up. Except they do. They always do. People are forever digging stuff up. If they don’t know what it is, they won’t know to be careful. In Iain M. Banks’ Matter, had the characters understood just what it was that had been found beneath the Hyeng-Zhar Falls they might have left it alone. As it was… not so much.

But even if one does provide documentation, there’s always the pitfall demonstrated by George O. Smith’s story “Lost Art.” Archaeologists Carroll and Baler struggle to grasp the principles behind an ancient Martian power relay. The Old Martians did believe in proper documentation, save (of course!) for those important details so widely known by all Martians there was no need to explain them. Neither Carroll nor Baler happen to be Old Martians. But most of the neighbourhood survives Carroll and Baler’s experiments, so it’s all good.

Which brings us back, full circle, to lack of documentation. If you don’t document, disaster. If you do document, disaster. A good reason to simply stay home in your nice hobbit hole and never, ever have adventures.

Originally published March 2019.

In the words of Wikipedia editor TexasAndroid, prolific book reviewer and perennial Darwin Award nominee James Davis Nicoll is of “questionable notability.” His work has appeared in Publishers Weekly and Romantic Times as well as on his own websites, James Nicoll Reviews and Young People Read Old SFF (where he is assisted by editor Karen Lofstrom and web person Adrienne L. Travis). He is surprisingly flammable.

About the Author

James Davis Nicoll

Author

In the words of fanfiction author Musty181, current CSFFA Hall of Fame nominee, six-time Hugo finalist, prolific book reviewer, Beaverton contributor, and perennial Darwin Award nominee James Davis Nicoll “looks like a default mii with glasses.” His work has appeared in Interzone, Publishers Weekly and Romantic Times as well as on his own websites, 2025 Aurora Award finalist James Nicoll Reviews (where he is assisted by editor Karen Lofstrom and web person Adrienne L. Travis) and the 2021, 2022, 2023, 2024, and 2026 Aurora Award finalist Young People Read Old SFF (where he is assisted by web person Adrienne L. Travis). His Patreon can be found here.
Learn More About James
Subscribe
Notify of
guest
18 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
MByerly
6 years ago

A nice explanation of why guys don’t read manuals.   My elder brother spent untold hours having to readjust the blade belt on the lawn tractor because sweetgum balls would throw it out of whack.  When I took over the mowing, I read the manual, did a 1 minute adjustment of a part, and never had that problem, ever.  Unless you are Scottie who knows every dang thing an engineer needs to know, read the dang manual.  

princessroxana
6 years ago

Sometimes they lose the Manuel, like Ralph Hinkley and The Doctor.

JanaJansen
6 years ago

@1/MByerly: Scotty reads manuals for recreation.

princessroxana
6 years ago

Good manl

Winchell Chung
Winchell Chung
6 years ago

As a computer programmer, I find it alarming that commonly smartphone apps have no manual. People are expected to deduce how to use the app just  by playing with the user interface. Which leads to users being surprised years later when somebody shows them a hard-to-discover app feature that they never found.

Perhaps contemporary SFF readers expect there to be no manual. Kids these days…

zdamien
6 years ago

I just re-read Neogenesis, where a manual for supposedly no-longer-existent hardware is used as a bribe/payment.

Elli Quin panics Miles when she asks about the social manual, i.e. mercenary regulations and benefits package, of his purported troop.

JohnArkansawyer
6 years ago

Thanks to a well-placed Christmas gift, I am halfway through the Laundry Files series, which is full of pro-manual propaganda such as this story published by–who else?–Tor.com! Down on the Farm, by Charles Stross

princessroxana
6 years ago

I admit I seldom read instructions. I’m pretty good at seeing how things fit together and usually find studying the pieces clearer than trying to comprehend all that flap B into slot 2 stuff. 

oldfan
6 years ago

After all, if people cannot find the Horrible Thing or understand what it is, there is no reason to worry that they will decide to dig it up. Except they do. They always do. People are forever digging stuff up.

Hilarious and accurate.

I just read H. Beam Piper’s funny-but-sad Martian archaeology/paleolinguistics tale, “Omnilingual,” and the other side of the story’s story is: thinking you can read the manual ain’t no fun. The story’s free on Amazon and Gutenberg if anyone feels like reading about smokers polluting sites with casually lit up butts and “girls” getting condescended to over martinis made with native Martian root veggies.

o.m.
o.m.
6 years ago

@7, I was always irritated about Angleton & Co. not providing the proper manual, to see how Bob would react without any preconceptions.

mrbert
6 years ago

The lead character in the Poor Man’s Fight series by Elliott Kay gets out of a number of situations because he’s read the manuals for everything (he has a lot of free time). It’s kind of funny because everyone thinks he’s a genius and he typically responds, “I just read the manual.”

phuzz
6 years ago

@7 Indeed, part of the set-up for the Laundry Files books is that they are the memoirs of field agents, so that if they die their knowledge won’t be lost with them.

 

To answer the question in the headline though, it’s because reading the manual is rarely dramatic or interesting. That’s why it dosn’t appear in stories much.

AndyLove
6 years ago

In Asimov’s “Lest We Remember” a fellow with perfect memory is able to use the information in even the most poorly written manual – clearly a superpower

escaaape
6 years ago

So many interesting recommendations in these comments. This warms my manual-loving engineer heart.

One more: Mirabile by Janet Kagan 

“When humanity sent generation ships to colonize the planet Mirabile, the cargo included seed banks and cryopreserved embryos of every Earth species the colonists might need, genetically engineered to produce more Earth species on cue. However, many of the instructions were lost en route, and decades after arrival, the genetically-engineered fauna and flora are still causing problems…”

https://en.m.wikipedia.org/wiki/Mirabile_(novel) 

 

keithmo
keithmo
6 years ago

A long time ago I wrote and edited technical manuals. Not as many organizations want to pay for that effort any more. I recall a brief period of time when developers of user interfaces tested designs for intuitiveness with real people, added built-in help functionality, and last provided a user manual to complement the other two. The more effort put into the first two meant less work needed for the third.  Costs and development time pressures killed that practice quickly.  Without naming name, Nth generation developers rely on the early reputation of a product’s ease of use to get away with leaving out helpful documentation.  This happens even when the later generations have little resemblance to the original product.

 

JohnArkansawyer
6 years ago

o.m@10: To be fair, Angleton was pretty good about giving Bob the technical information he’d need. It was contextual information that he repeatedly left out.

zdamien
6 years ago

One fantasy character who reads the manual: http://egscomics.com/egsnp/2014-12-29

princessroxana
6 years ago

1. Because the Abusive Precursors didn’t include a manual

2. Because the manual is in an incomprehensible alien language

3. Because it’s more fun to meddle blindly and dangerously with Things Man Was never Meant To Know