Sailing Ships, Slide Rules, And The Quality Of Engineering

We recently ran a post about engineers being worse, better, or the same than they “used to be” and it got me thinking. Of course “used to be” is in the eyes of the beholders. To me, that’s the 1950s and 1960s. To some of you, my generation is the “used to be” generation. To some of you, I’m past even that.

I’ve often said, there are two things that are simple: something really simple, and something really complex. For example, when a caveman grabbed a log floating down the river and hitched a ride a few miles downstream that was pretty simple. Today, you can go on a well-equipped boat, stab your finger at a map, click go, and the boat will do almost all the work. However, get onboard a sailing vessel from 1850 and you better know what you are doing. What’s more is, some sailors were better than others.

What’s Better or Best?

Were yesterday’s engineers better than today? That’s like asking who is the “best” driver. It depends a lot on what “best” means. Safer? Faster? Most efficient? I would suggest that yesterday’s engineers were better at doing yesterday’s jobs. I own several slide rules and I can use them, but I bet my mentor who finished college in the 1940s was faster. I don’t need to be faster. On the other hand, he might have some trouble doing a good Internet search.

But here’s the problem. Doing basic math is like the caveman on the log (and yes, that begs for a slide rule joke). Asking Wolfram Alpha to solve your set of simultaneous equations is like the modern computer-controlled ship with GPS. You can bet that the sailing master of a barque in 1850 knew a lot more about sailing and winds and ship construction than the average guy on a modern ship. He had to. That gave him extra reasoning tools when faced with a problem.

Slide Rules Do (Most) of the Math

By the same token, using a slide rule is very helpful but–paradoxically–you have to know a little math to be able to use it. In particular, you had to have a rough idea of the magnitude of the answer to get the right answer. If you couldn’t get that concept or do the simple estimate in your head, the slide rule was useless and you probably dropped out of engineering school. Today, you may or may not have that kind of math smarts, and it doesn’t matter.

I’ve known graybeards that keep up with the modern technology. I’ve also known plenty who are stuck in the past, talking about how horrible transistors, or ICs, or software is and how it has ruined everything. Of course, they haven’t.

Lesson Learned

As Gerrit pointed out, we tend to remember the brilliant engineers and projects and forget the bad ones (unless they are really bad). Even in “the golden age” there were good engineers and bad.

So how can you maximize your chances of being one of the good ones when this turns into some kid’s golden age? Two things, I think. Never stop learning the new technology. The hot-shot engineer with the slide rule wouldn’t function as well in today’s world unless he was willing to learn about the new things. But also, learn the fundamentals. You don’t have to know how an engine works to drive a car. But all the race car drivers do know. Having tools to do circuit analysis or solve thorny math equations is a great time saver. But you ought to know how to do it without those tools. The insights you’ll gain will give you more tools at your disposal when faced with a problem.

Engineering is a series of abstractions. Always try to drive down the abstraction layers. Know how to program? How does a CPU work at the logic gate level? Know how that works? Then how do the transistors form those gates? When you understand that, dig into why the transistors work at all. Sure, you probably aren’t going to build a transistor from raw materials. But you’ll gain new insights and those insights will help you solve future problems. Besides, if there’s ever a zombie apocalypse, it might be good to know how to use a slide rule or build a transistor.

Chemical Nomenclature

Looking at the ingredient list of some popular processed foods will produce a puzzled look on the typical hacker’s face. Tricalcium phosphate, thiamine mononitrate, zinc proteinate, pyridoxine hydrocloride… just who the hell comes up with these names anyway? It turns out that there is a method to the madness of chemical name structures. Some of them are well known, such as sodium chloride (NaCl) and hydrogen peroxide (H2O2). Others… not so much. In the early years of chemistry, chemical substances were named after their appearance, affects and uses. Baking soda, laughing gas and formic acid (formic is Latin for ant, and responsible for the sting in an ant bite) to name a few. As more and more chemical substances were discovered over time, a more structured naming convention was needed. Today, the above are known as sodium bicarbonate (NaHCO3), nitrous oxide (N2O) and a type of carboxylic acid (R – COOH, think of the “R” as a variable) respectively.

In today’s article, we’re going to talk about this naming structure, so that next time you admire the back of soup can, you won’t look so puzzled. We’ll also cover several common definitions that every novice biohacker should be familiar with as well.

Continue reading “Chemical Nomenclature”

Program Your Brain, Hack Your Way To Productivity

Most people wish they were more productive. Some buckle down and leverage some rare facet of their personality to force the work out. Some of them talk with friends. Some go on vision quests. There are lots of methods for lots of types of people. Most hackers, I’ve noticed, look for a datasheet. An engineer’s reference. We want to solve the problem like we solve technical problems.

It's got the cover equivalent of click-bait, but the centimeter thick bibliography listing research sources at the back won me over.
It’s got the cover equivalent of click-bait, but the centimeter thick bibliography listing research sources at the back won me over.

There were three books that gave me the first hints at how to look objectively at my brain and start to hack on it a little. These were The Power of Habit by Charles Duhigg, Flow By Mihaly Csikszentmihalyi, and Getting Things Done By David Allen.

I sort of wandered into these books in a haphazard path. The first I encountered was The Power of Habit which I found to be a bit of a revelation. It presented the idea of habits as functions in the great computer program that makes up a person. The brain sees that you’re doing a task over and over again and just learns to do it. It keeps optimizing and optimizing this program over time. All a person needs to do is trigger the habit loop and then it will run.

For example: Typing. At first you either take a course or, if your parents left you alone with a computer for hours on end, hunt-and-peck your way to a decent typing speed. It involves a lot of looking down at the keyboard. Eventually you notice that you don’t actually need to look at the keyboard at all. Depending on your stage you may still be “t-h-i-n-k-i-n-g”, mentally placing each letter as you type. However, eventually your brain begins to abstract this away until it has stored, somewhere, a combination of hand movements for every single word or key combination you typically use. It’s only when you have to spell a new word that you fall back on older programs.

Continue reading “Program Your Brain, Hack Your Way To Productivity”

Too Good To Throw Away: Dealing With An Out-Of-Control Junk Hoard

There it was, after twenty minutes of turning the place over, looking through assorted storage boxes. A Thinwire Ethernet network. About the smallest possible Thinwire Ethernet network as it happens, a crimped BNC lead about 100mm long and capped at each end by a T-piece and a 50 ohm terminator. I’d been looking for a BNC T-piece on which to hook up another terminator to a piece of test equipment, and I’d found two of them.

As I hooked up the test I wanted to run I found myself considering the absurdity of the situation. I last worked somewhere with a Thinwire network in the mid 1990s, and fortunately I am likely to never see another one in my life. If you’ve never encountered Thinwire, be thankful. A single piece of co-ax connecting all computers on the network, on which the tiniest fault causes all to fail.

So why had I held on to all the parts to make one, albeit the smallest possible variant? Some kind of memento, to remind me of the Good Old Days of running round an office with a cable tester perhaps? Or was I just returning to my past as a hoarder, like a Tolkienic dragon perched atop a mountain of electronic junk, and not the good kind of junk?

Continue reading “Too Good To Throw Away: Dealing With An Out-Of-Control Junk Hoard”

What We Are Doing Wrong. The Robot That’s Not In Our Pocket

I’m not saying that the magic pocket oracle we all carry around isn’t great, but I think there is a philosophical disconnect between what it is and what it could be for us. Right now our technology is still trying to improve every tool except the one we use the most, our brain.

At first this seems like a preposterous claim. Doesn’t Google Maps let me navigate in completely foreign locations with ease? Doesn’t Evernote let me off-load complicated knowledge into a magic box somewhere and recall it with photo precision whenever I need to? Well, yes, they do, but they do it wrong. What about ordering food apps? Siri? What about all of these. Don’t they dramatically extend my ability? They do, but they do it inefficiently, and they will always do it inefficiently unless there is a philosophical change in how we design our tools.

Continue reading “What We Are Doing Wrong. The Robot That’s Not In Our Pocket”

Beware Common Sense Engineering

I am always torn about the title of “engineer.” When I talk to school kids about engineering, I tell that an engineer is a person who uses science and math to solve or analyze practical problems. However, these days you hear a lot of engineering titles thrown around to anyone who does any sort of technical (and sometimes non-technical) work. “Software engineers” don’t have to be licensed to practice, while civil engineers do. What’s in a name and does any of this matter?

Continue reading “Beware Common Sense Engineering”

Automatic Resistance: Resistors Controlled By The Environment

Resistors are one of the fundamental components used in electronic circuits. They do one thing: resist the flow of electrical current. There is more than one way to skin a cat, and there is more than one way for a resistor to work. In previous articles I talked about fixed value resistors as well as variable resistors.

There is one other major group of variable resistors which I didn’t get into: resistors which change value without human intervention. These change by environmental means: temperature, voltage, light, magnetic fields and physical strain. They’re commonly used for automation and without them our lives would be very different.

Continue reading “Automatic Resistance: Resistors Controlled By The Environment”