|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.
Crappy Tech Journalism
June 11, 2019
Sometimes I long for the days of printed trade journals. Print was so expensive that a staff of editors was required to curate the material, to ensure only the most important information was presented, and it was dished out in a literate and accessible fashion. The Internet doomed these publications, and, worse, as the magazines went online-only, staffs were slashed. Copy editors are as extinct as dinosaurs, yet their role was to ensure the material was presented in clear and correct English. Now it's common to see sloppy mistakes. Just as code inspections harness multiple minds in a quest for perfection, one person simply cannot reliably edit his or her own work. I find errors in my writing and wonder what slips by me.
Many of the web sites that masquerade as technical journals are just collections of extended press releases. For instance, Electronic Products just ran a piece about TI's new 10 GSa/s 12-bit ADC. The specs are truly impressive, and I'd sure like to play with one.
But one critical spec isn't mentioned at all: price. TI's web site lists this IC at $2786. The price alone makes this part a poor fit for nearly all applications. How can an article in a tech magazine not mention this critical fact? Price is as important a parameter as sample rate or distortion, as it's generally a huge factor in device selection.
Oh, also not mentioned: it's not available. So cool part, nice bit of shilling by the magazine, but without price and availability the information is pretty useless for a working engineer.
I sampled a half-dozen other tech publications and none had price and availability info about this part. Some of the articles were nearly word-for-word identical. I assume they simply parrot a TI press release.
Or consider the home page of so many tech web sites. Here's a sample from Electronic Design:
The blurb under the title is just a snippet from the beginning of the article. I imagine a robot creates these. These are not sentences and convey little meaning.
Too many other sites follow the same practice. Embedded.com was once my home, but I find it almost unreadable today. You can't tell if you want to read the article without reading the article. I guess that's good for clicks and to sell advertising, but it doesn't address the needs of the engineer.
Some have maintained their journalistic integrity. Edn.com's layout hasn't changed in years and still does a good job of summarizing each article with one pithy sentence. EEtimes.com is excellent. EEworldonline.com is good, as is embedded-computing.com. Eeweb.com also provides decent summaries once you get deep into the home page, but first you have to navigate a picture header with titles like "Three steps to an efficient…" Efficient what? Bathroom? That's meaningless and doesn't entice me to read further.
And the same site puts forum responses ahead of article summaries. Forums are where very specific questions get asked. The articles appeal to a wider audience. Lead with the general, then present the highly-specific later. If a first-year calculus text started with the integral of (1/x)dx and later talked about limits, well, it wouldn't be useful at all.
In the early days of Embedded Systems Programming the editor wouldn't allow any articles written by vendors, fearing their bias would not be of service to readers. I thought that a bit extreme, as sometimes the vendors know more about an issue than anyone else. But today, with shrunken editorial staffs and a desperate need for "content," more and more articles are written by marketing folks. While vendor-supplied material can be very valuable, too much is just an ad for their products dressed in some high-level background material. Read the author bylines: you'll see what I mean.
Want to read the very first (print!) edition of Embedded Systems Programming? A PDF is here.
Worse, some bylines don't give the author's affiliation so you just don't know who they are working for. That strikes me as a deceptive practice. Part of the code of ethics for professional journalists reads: "Distinguish news from advertising and shun hybrids that blur the lines between the two."
Most printed trade publications came out monthly. A few, like EETimes, were weekly. Now content is added hourly in a bid for a leading Google search position. So one could say we're in a golden age of publishing, as never has so much material been available to engineers.
But I sure wish they'd replace some of their overpaid C-level executives with editors tasked with careful curation.
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.