Totally agree with this article, there are no immediate consequences to bad CPU bound code. I am seeing the consequences of this at my current position as a Senior Engineer at a startup where a lot of things were written naively, pushed the burden to cloud costs to keep pushing out features.
Something that really taught me to look for things like the "HDD Light" or Fan speed was starting my career in embedded systems. 16 bit MCUs really let you know if you are trying to much on them. They also let you know if you toggle the wrong pin by going up in flames.
The disconnect between your fingers and what actually runs the code is becoming greater and greater for newer developers. It will be interesting to see how computing power keeps up with bad code (it had been doing a good job so far).
I used to be a computer engineer working on embedded systems for automobiles. Quiescent current is what the normal proper draw is called for these systems when the car is off. We worked very hard getting these numbers in spec but it was hard to catch everything especially in this case where the issue is probably due to software missing the sleep state for that module. This could be from bad code or your CAN/LIN bus is messed up in your car. 99% of mechanics (and engineers) have no idea where to start with debugging these issues and the answer will be "replace the module".
Something that really taught me to look for things like the "HDD Light" or Fan speed was starting my career in embedded systems. 16 bit MCUs really let you know if you are trying to much on them. They also let you know if you toggle the wrong pin by going up in flames.
The disconnect between your fingers and what actually runs the code is becoming greater and greater for newer developers. It will be interesting to see how computing power keeps up with bad code (it had been doing a good job so far).