|Jack Ganssle's Blog
This is Jack's outlet for thoughts about designing and programming embedded systems. It's a complement to my bi-weekly newsletter The Embedded Muse. Contact me at email@example.com. I'm an old-timer engineer who still finds the field endlessly fascinating (bio).
For novel ideas about building embedded systems (both hardware and firmware), join the 40,000+ engineers who subscribe to The Embedded Muse, a free biweekly newsletter. The Muse has no hype and no vendor PR. Click here to subscribe.
June 10, 2020
The Death of Expertise by Tom Nichols is a short and excellent book bemoaning the world's increasing rejection of skilled and knowledgeable people. It's a couple of years old, but I just read it and feel it matches the 2020 zeitgeist perfectly.
An example, of course, is the anti-vaccine crowd that substitutes emotion for science. Aided and abetted by celebrity morons like Gwyneth Paltrow who prey on pocketbooks by pushing potions of dubious (at best) effectiveness, too many people substitute obsessiveness with stars over cold, hard, facts. Cold, hard facts are, of course, cold and hard and not nearly as bankable as weeping, sadness, and stories of overcoming hardship or descriptions of descents into madness.
In engineering we live and die by cold, hard facts. So sometimes I have trouble understanding just where some of these people are coming from.
The Death of Expertise is a witty and very well-written book. I guess we engineers would all cheer it while others might find its message heretical. He states that once experts were highly regarded. If a doctor told you to take your meds, you did. Now, maybe not. Wiccan rites might preempt antibiotics. I remember taking a childbirth class prior to my son's arrival; the teacher advised us to respond to well-meaning but ignorant advice by saying "Doctor says…", which, in those days, would often short-circuit an argument. Now, perhaps not so much so.
The word "elite" has lost any real meaning. It used to mean someone of high class. Or someone who is good at something requiring deep knowledge. Perhaps an expert. Now it seems to be THEM – those miserable educated people who live on the coasts and make us do awful things. Yet many of those who complain about these elites, who are paid good salaries to pontificate about the declining state of the world, are educated people who live on the coasts. Elite = expert = bad, unless it's you complaining about those other elites.
Nichols posits that maybe too many people go to college. And that too many courses of study are what we used to call underwater basket-weaving: fun, maybe, but not of much account in the real world. If you read Rod Dreher in The American Conservative you're left with the impression that all colleges now are hives of political correctness, that you can't study English without dealing with all sorts of left-wing zaniness. It has been a very, very long time since I was in college, but it's hard for me to believe that calculus or transistor theory is steeped in anything but those cold, hard facts.
Perhaps engineering and science are immune. Or maybe even those bastions of rationality have changed. I hope not.
The book ends grimly with not much in the way of useful prescriptions. He suggests we practice humility. And that is really the point of this blog.
Engineering is all about using cold, hard facts to make things that work. But engineers are humans filled with buckets of hormones. We always want to be the smartest people in a room. And we like to be right.
But usually we're wrong. Case in point: bugs. None of us write bug-free code and we've all spent years sweating over a hot IDE setting breakpoints and collecting trace data. I'm glad the editor doesn't log the number of changes made to a file! How often have you covered a protype board with a sea of green wires to make it work?
If we can approach our work with humility we can recognize that we're error-prone. Maybe, if we can start a project humbly, we can work more proactively, and employ better processes to mitigate our mistakes. "What could go wrong" is a better way to start thinking about an engineering effort than "I can knock this out in a day!"
Feel free to email me with comments.
Back to Jack's blog index page.
If you'd like to post a comment without logging in, click in the "Name" box under "Or sign up with Disqus" and click on "I'd rather post as a guest."
Recent blog postings:
- Non Compos Mentis - Thoughts on dementia.
- Solution to the Automotive Chip Shortage - why use an MCU when a Core I7 would work?
- The WIRECARE - A nice circuit tester
- Marvelous Magnetic Machines - A cool book about making motors
- Over-Reliance on GPS - It's a great system but is a single point of failure
- Spies in Our Email - Email abuse from our trusted friends
- A Canticle for Leibowitz - One of my favorite books.
- A 72123 beats per minute heart rate - Is it possible?
- Networking Did Not Start With The IoT! - Despite what the marketing folks claim
- In-Circuit Emulators - Does anyone remember ICEs?
- My GP-8E Computer - About my first (working!) computer
- Humility - On The Death of Expertise and what this means for engineering
- On Checklists - Relying on memory is a fool's errand. Effective people use checklists.
- Why Does Software Cost So Much? - An exploration of this nagging question.
- Is the Future All Linux and Raspberry Pi? - Will we stop slinging bits and diddling registers?
- Will Coronavirus Spell the End of Open Offices - How can we continue to work in these sorts of conditions?
- Problems in Ramping Up Ventilator Production - It's not as easy as some think.
- Lessons from a Failure - what we can learn when a car wash goes wrong.
- Life in the Time of Coronavirus - how are you faring?
- Superintelligence - A review of Nick Bostrom's book on AI.
- A Lack of Forethought - Y2K redux
- How Projects Get Out of Control - Think requirements churn is only for software?
- 2019's Most Important Lesson. The 737 Max disasters should teach us one lesson.
- On Retiring - It's not quite that time, but slowing down makes sense. For me.
- On Discipline - The one thing I think many teams need...
- Data Seems to Have No Value - At least, that's the way people treat it.
- Apollo 11 and Navigation - In 1969 the astronauts used a sextant. Some of us still do.
- Definitions Part 2 - More fun definitions of embedded systems terms.
- Definitions - A list of (funny) definitions of embedded systems terms.
- On Meta-Politics - Where has thoughtful discourse gone?
- Millennials and Tools - It seems that many millennials are unable to fix anything.
- Crappy Tech Journalism - The trade press is suffering from so much cost-cutting that it does a poor job of educating engineers.
- Tech and Us - I worry that our technology is more than our human nature can manage.
- On Cataracts - Cataract surgery isn't as awful as it sounds.
- Can AI Replace Firmware - A thought: instead of writing code, is the future training AIs?
- Customer non-Support - How to tick off your customers in one easy lesson.
- Learn to Code in 3 Weeks! - Firmware is not simply about coding.
- We Shoot For The Moon - a new and interesting book about the Apollo moon program.
- On Expert Witness Work - Expert work is fascinating but can be quite the hassle.
- Married To The Team - Working in a team is a lot like marriage.
- Will We Ever Get Quantum Computers - Despite the hype, some feel quantum computing may never be practical.
- Apollo 11, The Movie - A review of a great new movie.
- Goto Considered Necessary - Edsger Dijkstra recants on his seminal paper
- GPS Will Fail - In April GPS will have its own Y2K problem. Unbelievable.
- LIDAR in Cars - Really? - Maybe there are better ideas.
- Why Did You Become an Engineer? - This is the best career ever.
- Software Process Improvement for Firmware - What goes on in an SPI audit?
- 50 Years of Ham Radio - 2019 marks 50 years of ham radio for me.
- Medical Device Lawsuits - They're on the rise, and firmware is part of the problem.
- A retrospective on 2018 - My marketing data for 2018, including web traffic and TEM information.
- Remembering Circuit Theory - Electronics is fun, and reviewing a textbook is pretty interesting.
- R vs D - Too many of us conflate research and development
- Engineer or Scientist? - Which are you? John Q. Public has a hard time telling the difference.
- A New, Low-Tech, Use for Computers - I never would have imagined this use for computers.
- NASA's Lost Software Engineering Lessons - Lessons learned, lessons lost.
- The Cost of Firmware - A Scary Story! - A hallowean story to terrify.
- A Review of First Man, the Movie - The book was great. The movie? Nope.
- A Review of The Overstory - One of the most remarkable novels I've read in a long time.
- What I Learned About Successful Consulting - Lessons learned about successful consulting.
- Low Power Mischief - Ultra-low power systems are trickier to design than most realize.
- Thoughts on Firmware Seminars - Better Firmware Faster resonates with a lot of people.
- On Evil - The Internet has brought the worst out in many.
- My Toothbrush has Modes - What! A lousy toothbrush has a UI?
- Review of SUNBURST and LUMINARY: An Apollo Memoir - A good book about the LM's code.
- Fun With Transmission Lines - Generating a step with no electronics.
- On N-Version Programming - Can we improve reliability through redundancy? Maybe not.
- On USB v. Bench Scopes - USB scopes are nice, but I'll stick with bench models.