The professor called out here has approaching zero impact in this industry. Her ideas won't go anywhere to drive the approach to education, engineering, or science. However, making a big deal out of it clearly leads to clicks, views, comments, and controversy; the lifeblood of media in general and modern internet-based forums in particular. It's just that sometimes the mess that spills out is difficult to clean out and control, even with Boraxo.
If rigor is important, then many of you in general, and Dave in particular, are missing the point. The lack of rigor has already permeated engineering so completely that it merits very little attention here, and goes unnoticed until pointed out, at which point it gets ignored anyway because of the near-complete lack of ability to do anything about it.
The key driver for lack of rigor throughout engineering is the control of engineering by management who use non-engineering methods to determine the course of the engineering process.
So what is this lack of "rigor" in this context? A few examples:
1. Scheduling by simplistic guessing.
2. Assumptions that external solutions work perfectly.
3. Assumptions that internal solutions are completely reusable.
4. Jumping to conclusions about the cause of the problem, which leads to...
5. Jumping to solutions for a problem, which only wastes time and money.
6. It can be debugged in the field.
How many more can you add to the list?
This makes its way to the real world where corporations allow mechanical engineers, MBAs, etc. to determine the complexity and scheduling of electrical and software projects. Lowly software and electrical engineers, who always seem to be asking for more money, time, and documentation, are dismissed and ridiculed because somehow they didn't internalize the factors that are actually important such as ROI and time to market.
The results of an engineering organization driven by management who neither understand nor value rigor are products that are incomplete, unsafe, unreliable, have flaws, have bugs, etc. Many problems you can attribute to a product derives from this.
The other side of the argument is that by putting so much into research, development, and testing, the product would never get done, take too much money, etc. This false economy works only because the costs of not running an engineering organization properly are externalized to customers, warranty claims, unknown lost sales, unpaid overtime, and other such things.
So, sure, let's stir the pot and yank the chain by posting some random video. However, if you are going to do that under the guise of defending "rigor", at least drive the discussion to something realistic and productive, and that by the way, is an actual problem.