I'm not implying, it's what I, along with other technicians have come across in our profession as professional service techs.
We have websites that are strictly for us professionals, closed to any non-techs/DIYers, etc., where we discuss many topics.
We just don't want distractions of amateurs asking questions, there are other websites for that stuff.
This keeps out the rift-raff from fouling up the site.
In order to access the site and be a member, we have to first prove that we have the qualifications, the certifications, and are currently employed at a service shop.
And we have to send a yearly payment on our business checks.
We share and trade among us our findings, tips, and service info to stay abreast of what's going on in the tech world.
Frankly, this is a very paranoid perspective to take.
Firstly, focusing on appliances, many of them don’t have any way of persisting long term metric tracking. An average dishwasher or washer may only run from read-only memory and operate with a real time operating system, with volatile memory that doesn’t persist if the power cycles (which in any time span, it will). So I don’t think that it’s even feasible in many appliances to include such a time bomb. And in a simple appliance, they might even have to spend extra money to build in that sort of hardware to enable it!
But let’s say you have something that does have a small amount of non volatile memory- after all, you’d only need a few bytes to count time or cycles. Surely you’d see them dropping dead en masse in such numbers that would prompt a class action lawsuit? Because that would mean a near 100% failure rate.
Taking it a step further, perhaps they use a randomizer of some sort to make it only 40% of units have a time bomb. Then they’d be shooting their own reputation in the foot? I think we can all acknowledge if an appliance dies in a short time frame, you’re much less likely to buy from the same brand.
If this was really something done by a big manufacturer, the software developer would certainly have leaked this code to the FTC or similar agency, or to a news agency. Do you know how many people have to see, edit, review, comment on, approve code for it to be sent to production facilities? The answer is a LOT.
Now… I’m sure that somewhere, it’s happened. Perhaps not a full deliberate code time bomb failure, but a performance reduction. What can happen, will happen at least once, by someone’s hand.
But to assert that this is widespread or any level of common, and by major industry players, but then say the proof is “in private communities where you have to prove qualifications” amounts to “trust me bro”.
The reality is simple: cost reductions mean, intentional or not, some failures happen in a shorter time than we’d like due to cheaper parts. Maybe less of a protection on motor coil windings. Less heat dissipation on a triac, as someone mentioned. Poor solder joints on a relay that eventually cause a high-heat condition on the board. Or even circuitry thats perfectly fine, and just can’t handle a small power surge. It’s not a conspiracy.