Books You Should Read: Feynman’s Appendix To The Challenger Disaster Report

It isn’t really a book, but Richard Feynman’s Appendix to the Challenger Disaster Report is still definitely something you should read. It’s not particularly long, but it’s educational and relevant not just as an example of critical thinking in action, but as a reminder not to fool oneself; neither individually, nor on an organizational level. Sadly, while much was learned from the events leading to and surrounding the Challenger disaster, over thirty years later many of us can still find a lot of the same things to relate to in our own professional lives. There isn’t a single magic solution, because these problems are subtle and often masquerade as normal.

Feynman and the Challenger Disaster

Richard Feynman (1918-1988) was a Nobel Prize winning physicist and one of the best-known scientists of his time. In 1986 he somewhat reluctantly agreed to join the Rogers Commission, whose task was to investigate the Challenger disaster. The space shuttle Challenger had exploded a little more than a minute after launch, killing everyone on board. The commission’s job was to find out what had gone wrong and how it had happened, and figure out how to keep it from happening again.

Continue reading “Books You Should Read: Feynman’s Appendix To The Challenger Disaster Report”

Books You Should Read: IGNITION!

Isaac Asimov described the business of rocket fuel research as “playing footsie with liquids from Hell.” If that piques your interest even a little, even if you do nothing else today, read the first few pages of IGNITION! which is available online for free. I bet you won’t want to stop reading.

IGNITION! An Informal History of Liquid Rocket Propellants is about how modern liquid rocket fuel came to be. Written by John D. Clark and published in 1972, the title might at first glance make the book sound terribly dry — it’s not. Liquid rocket fuel made modern rocketry possible. But most of us have no involvement with it at all besides an awareness that it exists, and that makes it easy to take for granted.

Most of us lack any understanding of the fact that its development was the result of a whole lot of hard scientific work, and that work required brilliance (and bravery) and had many frustrating dead ends. It was also an amazingly dangerous business to be in. Isaac Asimov put it this way in the introduction:

“[A]nyone working with rocket fuels is outstandingly mad. I don’t mean garden-variety crazy or a merely raving lunatic. I mean a record-shattering exponent of far-out insanity.

There are, after all, some chemicals that explode shatteringly, some that flame ravenously, some that corrode hellishly, some that poison sneakily, and some that stink stenchily. As far as I know, though, only liquid rocket fuels have all these delightful properties combined into one delectable whole.”

At the time that the book was written and published, most of the work on liquid rocket fuels had been done in the 40’s, 50’s, and first half of the 60’s. There was plenty written about rocketry, but very little about the propellants themselves, and nothing at all written about why these specific substances and not something else were being used. John Clark — having run a laboratory doing propellant research for seventeen years — had a unique perspective of the whole business and took the time to write IGNITION! An Informal History of Liquid Rocket Propellants.

Liquid rocket propellant was in two parts: a fuel and an oxidizer. The combination is hypergolic; that is, the two spontaneously ignite and burn upon contact with each other. As an example of the kinds of details that mattered (i.e. all of them), the combustion process had to be rapid and complete. If the two liquids flow into the combustion chamber and ignite immediately, that’s good. If they form a small puddle and then ignite, that’s bad. There are myriad other considerations as well; the fuel must burn at a manageable temperature (so as not to destroy the motor), the energy density of the fuel must be high enough to be a practical fuel in the first place, and so on.

The actual process of discovering exactly what materials to use and how precisely to make them work in a rocket motor was the very essence of the phrase “the devil is in the details.” For every potential solution, there was a mountain of dead-end possibilities that tantalizingly, infuriatingly, almost worked.

The first reliable, workable propellant combination was Aniline and Red Fuming Nitric Acid (RFNA). “It had the one – but magnificent – virtue that it worked,” writes Clark. “Otherwise it was an abomination.” Aniline was difficult to procure, ferociously poisonous and rapidly absorbed through skin, and froze at an inconvenient -6.2 Celsius which limited it to warm weather only. RFNA was fantastically corrosive, and this alone went on to cause no end of problems. It couldn’t be left sitting in a rocket tank waiting to be used for too long, because after a while you wouldn’t have a tank left. It needed to be periodically vented while in storage. Pouring it gave off dense clouds of remarkably toxic gas. This propellant would go on to cause incredibly costly and dangerous problems, but it worked. Still, no one wanted to put up with any of it one moment longer than they absolutely had to. As a result, that combination was not much more than a first step in the whole process; there was plenty of work left to do.

By the mid-sixties, liquid rocket propellant was a solved problem and the propellant community had pretty much worked themselves out of a job. Happily, a result of that work was this book; it captures history and detail that otherwise would simply have disappeared.

Clark has a gift for writing, and the book is easy to read and full of amusing (and eye-widening) anecdotes. Clark doesn’t skimp on the scientific background, but always in an accessible way. It’s interesting, it’s relevant, it’s relatable, and there is plenty to learn about how hard scientific and engineering development actually gets done. Download the PDF onto your favorite device. You’ll find it well worth the handful of evenings it takes to read through it.

Books You Should Read: The Idea Factory

You’ve heard of Bell Labs, but likely you can’t go far beyond naming the most well-known of discoveries from the Lab: the invention of the transistor. It’s a remarkable accomplishment of technological research, the electronic switch on which all of our modern digital society has been built. But the Bell Labs story goes so far beyond that singular discovery. In fact, the development of the transistor is a microcosm of the Labs themselves.

The pursuit of pure science laid the foundation for great discovery. Yes, the transistor was conceived, prototyped, proven, and then reliably manufactured at the Labs. But the framework that made this possible was the material researchers and prototyping ninjas who bridged the gap between the theory and the physical. The technology was built on what is now a common material; semiconducting substances which would not have been possible without the Labs refinement of the process for developing perfectly pure substances reliably doped to produce the n-type and p-type substances that made diode and transistor possible.

Continue reading “Books You Should Read: The Idea Factory”

Books You Should Read: The Bridge

A few weeks ago, Amazon’s crack marketing AI decided to recommend a few books for me. That AI must be getting better because instead of the latest special-edition Twilight books, I was greeted with this:

“The asteroid was called the Hand of God when it hit.”

That’s the first sentence of The Bridge, a new Sci-Fi book by Leonard Petracci. If you think that line sucks you in, wait until you read the whole first chapter.

The Bridge is solidly in the generation ship trope. A voyage hundreds or even thousands of years long, with no sleep or stasis pods. The original crew knows they have no hope of seeing their destination, nor will their children and grandchildren. Heinlein delved into it with Orphans of the Sky. Even Robert Goddard himself discussed generation ships in The Last Migration.

I wouldn’t call The Bridge hard Sci-Fi — and that’s perfectly fine. Leonard isn’t going for scientific accuracy. It’s a great character driven story. If you enjoyed a book like Ready Player One, you’ll probably enjoy this.

The Bridge Is the story of Dandelion 14, a ship carrying people of Earth to a new planet. At some point during the journey, Dandelion 14 was struck by an asteroid, which split the ship in two. Only a few wires and cables keep the halves of the ship together. The crew on both sides of the ship survived, but they had no way to communicate. They do catch glimpses of each other in the windows though.

Much of the story is told in the first person by Horatius, a young man born hundreds of years after the asteroid strike. Horatius’ side of the ship has a population of one thousand, carefully measured at each census. They’ve lost knowledge of how to operate the ship’s systems, but they are surviving. Most of the population are gardeners, but there are doctors, cooks, porters, and a few historians. At four years old, Horatius is selected to become a gardener, like his father was before him. But Horatius has higher aspirations. He longs to become a historian to learn the secrets of the generations that came before him and to write his own story down for those who will come after.

Horatius sees the faces of the people on the other side of the ship as well. Gaunt, hungry, often fighting with knives or other weapons. A stark contrast to the well-fed people on his side of the vessel. The exception is one red-haired girl about his age. He often finds her staring back at him, watching him.

Horatius might have been chosen as a gardener, but he’s clever — a fact that sometimes gets him in trouble. His life takes an abrupt turn when the sleeping ship awakens with an announcement blaring “Systems Rebooting, Ship damage assessed. Reuniting the two halves of the ship and restoring airlock, approximately twenty-four hours until complete.”

The hardest part of writing a book review is not giving too much away. While I won’t tell you much more about the plot for The Bridge, I can tell a bit about how the book came about. You might call this book a hack of the publishing system. Leonard Petracci is also known as leoduhvinci on Reddit. The Bridge started life as Leonard’s response to a post on /r/writingprompts. The prompt went like this:

After almost 1,000 years the population of a generation ship has lost the ability to understand most technology and now lives at a pre-industrial level. Today the ship reaches its destination and the automated systems come back online.

Leonard ’s response to the prompt shot straight to the top, and became the first chapter of The Bridge. Chapter 2 followed soon after. In only a few months, the book was complete. Available on Reddit, and on Leonard’s website. The Bridge is also available on Amazon for Kindle, and on paper from Amazon’s CreateSpace.

The only real criticism I have about The Bridge is the ending. The book’s resolution felt a bit rushed. It would have been nice to have a few more pages telling us what happened to the characters after the major events of the book. Leonard is planning a sequel though, and he teases this in the final pages.

You can start reading The Bridge right now on Leonard’s website. He has the entire book online for free for a few more weeks. If you’ve missed the free period, the Kindle edition is currently $2.99.

Books You Should Read: Making A Transistor Radio

When a Hackaday article proclaims that its subject is a book you should read, you might imagine that we would be talking of a seminal text known only by its authors’ names. Horowitz and Hill, perhaps, or maybe Kernigan and Ritchie. The kind of book from which you learn your craft, and to which you continuously return to as a work of reference. Those books that you don’t sell on at the end of your university career.

Ladybird books covered a huge range of topics.
Ladybird books covered a huge range of topics.

So you might find it a little unexpected then that our subject here is a children’s book. Making A Transistor Radio, by [George Dobbs, G3RJV] is one of the huge series of books published in the UK under the Ladybird imprint that were a staple of British childhoods for a large part of the twentieth century. These slim volumes in a distinctive 7″ by 4.5″ (180 x 115 mm) hard cover format were published on a huge range of subjects, and contained well written and informative text paired with illustrations that often came from the foremost artists of the day. This one was published at the start of the 1970s when Ladybird books were in their heyday, and has the simple objective of taking the reader through the construction of a simple three transistor radio. It’s a book you must read not because it is a seminal work in the vein of Horrowitz and Hill, but because it is the book that will have provided the first introduction to electronics for many people whose path took them from this humble start into taking the subject up as a career. Including me as it happens, I received my copy in about 1979, and never looked back. Continue reading “Books You Should Read: Making A Transistor Radio”

Books You Should Read: The Hardware Hacker

There’s no one quite like Andrew ‘Bunnie’ Huang. His unofficial resume begins with an EE degree from MIT, the author of Hacking the Xbox, creator of the Chumby, developer of the Novena, the first Open Source laptop, and has mentored thousands of people with dozens of essays from his blog.

Above all, Bunnie is a bridge across worlds. He has spent the last decade plying the markets of Shenzhen, working with Chinese manufacturers, and writing about his experiences of taking an idea and turning it into a product with the help of Chinese partners. In short, there is no person better suited to tell the story of how Shenzhen works, what can be done, and how to do it.

Bunnie’s The Hardware Hacker ($29.95, No Starch Press) is the dead tree expression of years of living and working in Shenzhen, taking multiple products to market, and exploring the philosophy that turned a fishing village into a city that produces the world’s electronic baubles.

Continue reading “Books You Should Read: The Hardware Hacker”

Books You Should Read: Poorly Made In China

This book is scary, and honestly I can’t decide if I should recommend it or not. It’s not a guide, it doesn’t offer solutions, and it’s full of so many cautionary tales and descriptions of tricks and scams that you will wonder how any business gets done in China at all. If you are looking for a reason not to manufacture in China, then this is the book for you.

The author is not involved in the electronics industry. Most of the book describes a single customer in the personal products field (soap, shampoo, lotions, creams, etc.). He does describe other industries, and says that in general most factories in any industry will try the same tricks, and confirms this with experiences from other similar people in his position as local intermediary for foreign importers.

Continue reading “Books You Should Read: Poorly Made In China”