Comment Wow, what a revelation (Score 1) 46
It's almost as if they're just now realizing Goodhart's Law exists.
"Wear-out failures aren't always different from infant mortality failures, though."
That are completely different issues, always different.
Only in the most utterly pedantic sense of the word "different" wherein you mean that by definition, infant mortality occurs early and wear occurs later. But they can both stem from the same root cause, which is a component not built with adequate tolerances. In other words, they can be the same fundamental issue, just expressing themselves at different times.
That would be reflected in a low MTBF rather than the example "MTBF of 600000 hours".
Most products don't have an MTBF. And things that do have MTBF are based on accelerated wear testing on a small number of units, and can have almost zero basis in reality. There was one model of major brand hard drive about twenty years back where a couple of RAIDs where I used to work got lost because the drives all died after such a predictable number of powered-on hours that by the time you could re-stripe the RAID, the next drive would die. They ended up making sure the drives had a high variance in powered-on hours before using them in RAIDs after that.
Do you really understand what that means? Because it seems clear you don't.
It's an example that proves or demonstrates a point. And the point it was proving was that the same root cause can be responsible for both catastrophic early product failures and premature deterioration-related failures.
I'm skeptical of this.
People who don't understand that wear out failures are a different statistical mechanism to infant mortality failures I'm sure are very sceptical. I guess you also don't believe any HDD can fail within the first month of operation because they have an MTBF of 600000 hours?
Devices get shipped with manufacturing defects and bad batches all the time. That has zero to do with wear out failure rate.
Wear-out failures aren't always different from infant mortality failures, though. If the defect is caused by a design flaw in a component resulting in a structural weak point, that same weak point could fail after one use or a thousand, and it could just be a ticking time bomb. Someone could get very unlucky and find one that is slightly weaker, and it could break much sooner.
Case in point, I recall a machine where some people would have to have their laptops replaced every couple of months for motherboard failures, while others lasted for years, and it turned out to be dependent on how people closed their laptops at the end of the day and whether they pressed on the bottom of the case in a particular spot that wiggled the GPU. But if you handed one that had been working for five years to someone who used their left hand under the laptop while closing it, it would be dead in two or three months. If you replaced it with a brand new one, the brand new one would be dead in two or three months. And so on.
The truck looked legitimate. The paperwork appeared routine. And in the middle of a workday, about 1,800 cases of bourbon were loaded onto the truck as if it were just another shipment.
Later in the story, the explanation for how this happened is nearly identical to these tech thefts:
Newman said investigators believe the theft may be tied to a "complex ring" targeting high-value consumer products. The perpetrators appeared to impersonate an existing trucking company, using a company name, phone number and other details to gain trust and secure the load, he said.
"They basically try and look like, sound like ⦠a legitimate trucking company," Newman said. "They spoof the company name, they spoof the trucking dispatcher."
In the company's news release, it said the theft appeared to have been carried out with knowledge of "logistics operations and product movement schedules," suggesting planning and coordination.
Every data center Ukraine can locate needs to be leveled. That would be far easier if the Russian asset in the White House would stop sucking Putin's dick and help Ukraine do its job.
After that, a systematic destruction of every power generation site surrounding Moscow needs to be undertaken. The city needs to go dark and stay dark during the winter.
If Ukraine hasn't already planned for this, they need to do it now. So long as Russia deliberately Ukrainian power generation and civilian targets, Ukraine needs to do the same. Once Moscow is dark, the muscovite midget's whining will be a joy to hear.
My parents have Verizon and have had them for years. The cost of phone, tv, and internet is roughly $135/month, and that's only for them to get 12 specific channels they choose along with local channels. Neither watch much tv any more which is why they went with this package.
That is still far too much. However, when my dad and I look over what it would cost to drop the tv portion and use something else such as YoutTube TV, they'd only say about $10/month.
We've talked about moving him to Comcast to get the lower rates, but he hasn't made the jump yet.
I have Comcast for internet only and have no problems with them despite the repeated complaints on here.
Because it embeds into html, rather than rendering the html. It makes for very fragmented code.
In my experience, most sufficiently advanced use of PHP involves rendering the HTML. You can do it either way.
And most sufficiently complex PHP uses PHP as a full-fledged language, complete with classes, etc., and to the extent templates are used, the code in them consists of tiny partial-line-long fragments of code that call some method in some other file that is basically just code.
In other words, very fragmented code isn't caused by PHP; it's caused by the way that the developer chose to use PHP.
The following statement is not true. The previous statement is true.