Matt's Homepage

I’m a huge fan of the Fighting Fantasy book created in 1982 by Steve Jackson and Ian Livingstone. I still have a good collection of them, but my first and favorite had to be Deathtrap Dungeon.

ChrisC has a nice Youtube channel with a few good playthroughs of some of my favorite adventure books. He does a good job on his walkthroughs and is a nice, calming listen. Honestly, I don’t know why more Twitch streamers don’t read old adventure books like this and let people vote on the next choice. Perhaps there’s an idea there…

Back to the topic. My first introduction to the books was as a middle schooler and I can’t tell you how many times I checked out this white-cover Dell version of Deathtrap Dungeon. I soon found the City of Thieves, Warlock of Firetop Mountain, and many others. Before the internet, one had to visit many libraries to find more of them. There is even a great fan site that has lots of details about each book – including interesting errors.

They did a reprint series a few years back, but that has ended as well. The books can still be had on ebay, or if you’re interested in a more professional production, Eddie Marston was hired to do an interactive video series that’s had much higher production values.

I love finding old adventure books from my childhood – but eBay and many online shops often charge top dollar. Here’s some cheap sources for rarer paperbacks.

• https://www.abebooks.com/
• https://www.thriftbooks.com/
• https://www.bookdepository.com/

Or, if you are so inclined, be sure to check out the Internet Archive’s Open Library. It often has the books for free checkout.

I have been fascinated with early stories of people trying to climb mountains, have early adventures through vast foreign lands, or cross the great unknown and deserted barrens.

Yet no stretch of land is so isolated, bare, and desolate as the Sahara desert. It’s hard for us to imagine the realities of traveling during the early centuries of modern civilization, but fortunately we have some documents from those periods. Some of which have been summarized and collected in a book called ‘The Golden Rhinoceros: Histories of the African Middle Ages‘, by Francois-Xavier Fauvelle.

First off, there were your guides. You had to travel in groups for safety from bandits and injury. Guides at the journey’s port cities had to be purchased to lead you across the desert. Deserts they knew fairly well because when not guiding, they might be the very raiders that would kill you on a different trip. They were often a shady lot that had little patience for the unprepared.

While today’s travelers complain about $4 bottles of water at the airport, the water situation was different for earlier Saharan travelers:

Then there was the problem of water. It would be even better to say the problem of thirst, your constant companion during the crossing. All travelers, all geographers say the same thing: the water is sometimes “fetid and lethal” and, Yaqut al-Hamawi humorously reckons, “has none of the qualities of water other than being liquid.” Such a beverage inevitably generates intestinal pains that make life difficult and sour the memory of the trans-Saharan experience. In good years, when there had been plenty of rain, water filled the rocky gullies, and people could drink and do laundry. In bad years, the burning wind dried out the water in the goatskins; consequently, a camel’s throat had to be cut and its stomach removed. The water it contained was drawn off into a sump and drunk with a straw. In the worst-case scenario, one could kill an addax antelope and follow a similar procedure to extract greenish water from its entrails.

We complain about uncomfortable airline seats for 8 hours while crossing the ocean at 30,000ft. Earlier travelers endured countless days/weeks of far worse inconveniences.

And then there were the small, but numerous and in the end obnoxious, daily inconveniences: the omnipresent fleas, which you would try to drive away by wearing cords soaked in mercury around your neck; the numerous flies everywhere there was a rotting carcass (i.e., precisely around the wells and the camps); and the snakes.

And then there was the ever present danger of dozing off, lack of attention during a stop, or just getting turning around in the maze of dunes to realizing you were separated and probably lost in the desert to die.

The caravan tempers these harsh conditions with strict discipline; it diminishes them through distractions. You will put distance between yourself and the column only at your own risk, the Berber leader must have said. Those who paid for the crossing would amuse themselves hunting addax, letting their dogs run free, and riding a bit ahead of the caravan to let their horses graze and to enjoy the invigorating wait. But the games, the intemperance of the city-dwellers, could cost them dearly. Even though caravans could be made up of hundreds, sometimes even thousands, of camels, one could quickly lose sight of them behind a curtain of dunes. A few centuries later, on the same stretch of desert, but from the opposite direction, a caravan of pilgrims lost two of its members in a row and yet noticed only a day and a night after they disappeared. Nobody dared go back to look for them for fear of being lost themselves. The author of the story concludes philosophically: “But our conscience was clear because we had warned them of the risks they were running by not abiding by the rules of the caravan.”

This has to be one of the most interesting reads (audiobook listen in my case) I’ve had on the subject of nuclear history. I also think it should be read by every engineer of any background.

Why? Jim Mahaffey, while a Ph.D. in Nuclear Physics and having spent over 25 years in governmental, military, and civilian nuclear projects, presents a narrative that isn’t stilted in the usual pro/anti-nuclear rhetoric. I found myself captivated for three reasons. Firstly, some of these events and details I had never heard of before – like the fact there was a cave full of natural radioactive ore that sickened some hunters who wandered into it. Secondly, and related, he knows exactly what he’s talking about. He cites the chemistry, physics, and even patent information for everything involved. There is no hyperbole. His information comes from actual studies, chemistry, nuclear physics, and the hard scientific data. Some of the facts in the book I’d never heard anywhere else before. Sometimes I wondered if he wasn’t leaking secrets.  Finally, he does all this with a captivating sense of storytelling and a fantastically dry sense of humor. I found myself sitting in my car listening to a story finish out – such as when he tells the story of a cable tray fire that breaks out during one particular accident:

“The fire continued to grow so the supervisor ran down the hall and grabbed a larger fire extinguisher. He emptied it into the blaze, but the fire was unimpressed.”

The thing that makes this book great is that he isn’t arguing for or against nuclear power. He explains the chemistry and physics of what is going on so well that it removes the fear and terror we often associate with nuclear reactions. So all you are left with are the accidents. This is really unbiased storytelling that does what it should: it doesn’t tell you what to think – it presents all the data and narrates the story so that it makes YOU think. What would I have done? What should be done?

This is why I suggest every engineer read this book. Even if you are not interested in nuclear accidents or nuclear power scares you. It’s not really about that. It’s about the difficulty of engineering – especially engineering where failure means serious consequences. It’s about the mental traps we as engineers fall into. We can be extremely intelligent and well versed, but get taken out by a simple rat chewing a cable. The fact that it deals with energies that can, and have, killed people crystallizes the importance of each design decision. You’ll often see yourself connecting the thought that the designers had with your own engineering principles – and realizing the weak points.

Highly recommend.

Spoilers below on what I ‘learned’ – don’t read if you want to come up with your own conclusions

After listening to it on audiobook over the last week or so, I found myself thinking about these topics:

1. Anything that is foolproof is not. All mechanical systems have a useful lifetime and/or fail at some point. Maintenance doesn’t always happen when it should. Things that fail sometimes take time for people to realize they failed – especially if it is a backup system that is rarely used. People plug things in backward by accident, read the wrong gauge, use the wrong lubricant, etc. You cannot suppose that everything will be maintained as it was when it was perfect and new and the designer is right there watching it. Plants become unprofitable and corners get cut. Staff turns over all the time and information is often lost.
2. The weakest system, not the strongest one is all that is needed to start a problem.
3. In work around dangerous forces, you cannot have an ignorant workforce. People must understand WHY each procedure is there, or they’ll come up with shortcuts that may get themselves or others killed unexpectedly because they’re trying to save time/effort/money/etc.
4. We should probably not run experiments on commercial reactors/preparation plants. That should only happen in the lab. But there are many ambitious, very smart people that want to make a name for themselves and do things they should not because they believe they are smart enough.
5. When something must run constantly over a long time – given a long enough timeline – EVERY possible thing will happen. Every possible combination of failures will also happen. You simply can’t imagine it all.
6. Even when you imagine and prepare for the worst, it can be worse.
7. Luck plays a big part in disasters. Given exact same plants and the same accident, one will be ok and the other will not because of luck in the smallest detail/timing of how something happens.
8. Real disasters usually involve 2 or more very unexpected and different things simultaneously going bad or failing in quick succession.
9. Individual systems that are failsafe on their own can react in unexpected combinations when more than a few things at once start failing. You must look at how the system as a WHOLE handles an event that causes serious single and multiple system failures (i.e. a delivery truck loses its brakes, knocks over a power pole, and then hits the turbine building. It starts a fire that shuts down the turbines. With the external electrical wires down, the lights in the building go off. Unfortunately, that happens to be where the fire handling equipment is – that nobody can now find in the dark. You now have a nuclear meltdown because you can’t put out a fire because the lights went out.)
10. You must design things to end in a state after such an event that you can recover from them without endangering lives. When the explosion/leak does happen, is there a way to clean it up?
11. It is often the discounted/seemingly unimportant support systems that cause the accident to become a disaster. While massive amounts of effort are spent understanding nuclear forces and fission, most reactor accidents are caused by things like pump bearing failures, valves that get stuck, emergency generators that don’t kick on because the wiring went bad, or running ill-advised tests.
12. An unexpected chain of failures is what sometimes causes a disaster. (ex: a failing data cable starts generating error messages. The error log starts filling the available hard drive. The drive fills and crashes because nobody thought there would be so many messages. The computer that crashed was also controlling some other subsystem, which now fails too. That causes a bigger failure that leads to a disaster.)
13. An alarm that goes off all the time is as useless as if it hadn’t been installed at all.
14. When what you’re doing trips a failsafe – this is not a good thing. It’s an indication you’re operating outside of the defined parameters of the design. It’s an indication that you were one step from disaster. It’s critical to examine exactly what happened and prevent that from happening again. Procedures or actions that regularly trip a failsafe indicates imminent disaster.
15. The amount of thought and fail-safes you build must be directly proportional to how bad it will be if it goes wrong. Dropping a jar of tomato juice requires water, a mop, and bucket and buying a new bottle of tomato juice. Dropping a jar of fission products all over the floor is a whole other matter. From isolation, to clean up, to personal safety, to disposal, to handling what to do with the materials, clothes, and items used in the cleanup – all require complete thought and handling.
16. One must stay a little paranoid and constantly vigilant when working with systems that involve deadly/dangerous forces. A regular schedule of checking and re-checking is the only way to know if things are working as they should. You cannot be laissez-faire until a failure to fix something. Even little anomalies are indications that must be checked out. One must stay curious, regularly check, and fix things that don’t even seem super-important at first. See #2.

Here’s a great example:

A liquid storage tank of olive oil that develops a tiny leak could be bad. You are losing product, money, and might cause an injury if someone slips. It is even worse if it was almost undetectable and goes dripping into the floor drains for weeks, months, or even a year.  It gets even worse when the oil coagulates in the underfloor drains and almost completely plugs them up. Then the 50,000-gallon vat of spaghetti sauce spills and the drains that should have saved everyone don’t work. It causes the spill to go everywhere and gets on everyone. It gets even worse when the sauce ruins tens of thousand dollars of product that was sitting on the floor and destroys electronic machinery drenched in it. It gets even worse when it runs into the basement, filling it 2 feet full of spaghetti sauce. Because of one dripping olive oil vessel, you now have tens of thousands in lost products, people drenched in goo, machinery destroyed, and a basement flooded with a sauce that may take hundreds of thousands to clean up. On top of the fact you can’t make one more jar of the product until it’s all cleaned up.

Now imagine that it was nuclear fission products that dripped. And when enough collects, it becomes an unshielded reactor in the floor that kills anyone that comes near it.

This is why every engineer should read this book. To understand how failures really happen, and why just making an individual system fool proof and having safety systems can be a false comfort. The nuclear world is full of extremely smart people that bragged nothing could go wrong. Humility and diligence are the values we should cultivate.