People that have done QA have the best understand of this.
I was doing the QA on a life safety product. Any new hardware would mean pulling the specs for the ICs and verifying that the layout and pin-out where correct on the product designs. You don't need an electrical engineering degree to know that PIN-1 on IC-2 should be connected to PIN-A on IC-4 but deigns having it traced to PIN-C.
Not once was there ever a recall and all early product issues where just a firmware update. After no longer working at the company they stopped doing QA. Heard from a former coworker that they latest product releases have required a compete recall.
QA not only saves lives it also reduces service and support costs. It helps keep a good standing relationship with your clients. Good QA is about trying to brake the solution as a consumer not reading the manual.
Ever since they added the "universal search" thingy, their NAS do that anytime they reach a decently large video file. Even if you turn down search indexing, media indexing, media thumbnails, ... It still kills itself with no throttling processing those files.
May or may not be what you encountered, but had a customer caught by this and found out the hard way you can't stop it. My issue is not the processing, it's the throttling, it's so crazy how the entire NAS gets taken down for like ten minutes (and that was on a racked xeon model), no samba no nfs no nothing answering anymore.
While it is noctua advice, I don't think AMD supports that view, so it would seem correct to at least test the cpu the way the vendor recommends before making conclusions
You may have missed the part in the article that says that they only switched to offset mounting after their first Ryzen 9950X died when the cooler was mounted centered.
> But note that the 1st failure happened with a more centred heat sink. We only made the off-centre mounting for the 2nd system as to minimise the risk of a repeated system failure.
I hardly disagree with the first part of your statement, but the second half it should be noted that Microsoft hired the designer in chief of the delphi language at the time to design c#
Probably depends on your specific company or industry
Personally I've never seen anyone use Pascal as anything other than the butt of a joke or a background slide on "how far we've come" since the 80s. Nobody even seems to remember object Pascal.
... But I'm also in a sector that routinely relies on Fortran code so ymmv
People were not laughing at Turbo Pascal or Delphi when they came out, and they dominated for many years. Delphi/Object Pascal is still taught in the schools of many countries.
There are people who want everyone to forget Delphi/Object Pascal and they wish it was dead. But what they wish for and reality are two different things. Delphi still makes money, otherwise they wouldn't sell it.
It lasted for a few years as a first-class supported language, but by the early 90s they shifted most of their focus to C++ so the system API being in Pascal became more of a legacy annoyance than anything. You got to deal with Str255 types, putting "\p" at the start of all your string literals, remembering the rules for when to pass by reference or pass by value when you call toolbox functions, etc.
The fact is that without Object Pascal, there would not exist employees to work on MPW at all, or even Apple most likely.
Maybe in some alternative universe they would have been just as successful using BCPL, but the fact C and C++ were ignored at Apple until some employees came up with MPW as side project until it was too late to turn back, speaks volumes about Apple culture.
Just as it does the way A/UX was originally designed.
Apple officially supported C for Macintosh application development even back when they were still making devs do all their work on Lisas (see http://www.bitsavers.org/pdf/apple/lisa/workshop_3.0/Lisa_Wo...), but you're right that they were a majority Pascal shop until they shifted to C++ around when System 7 came out.
Not sure if salaries are rising for the popular and lower middle class in the us but if they're stagnating like here people will notice when things they could afford without thinking have now become luxuries .
Amazon is the only company I regularly use that has implemented AI as a front that users very often interact with, and it's not a total disaster. Their customer service AI (when you have an issue) actually works well, and in many cases I didn't need to escalate to a human to get something sorted. YMMV, of course, but I hate about 99.9999999% of those "AI" customer service crap usually, and the recent "smart" ones are somehow way worse than the tree based ones of old.
Huh, interesting. I periodically ask Siri "hey siri, are you actually smart yet?" (or variants on this depending on how I feel). So far I've always received a polite "I'm sorry, I don't know how to do that". No worries, you'll get there.
It's funny how the unexpected is way more impressive. I tried out the voice commands on my new car (BYD) and after it correctly interpreted and implemented my request, I politely said "thank you!" (as I always do, it's important to set a good example) and the car responded "you're welcome!". 100% could just have been a lucky setup for a scripted response... but...
> Its the biggest example out there why should not use PHP for anything close to, say 10% of facebook scale.
What a weird take to base your current belief on something that happened more than a decade ago.
Not only the condition for Hack creation (speed, memory usage and strict type checking) have been fixed a long time ago since php 7.0
But also if you reach 10% of facebook scale, it doesn't matter what language you used, you will need to rewrite anyway.
Show me a company where PHP is the issue because they reached 10% of facebook scale, and what you're showing is a company that succeeded thanks to PHP. Applies to other language the same. Picking your stack based on "but what if I reach that scale" has to be the mother of all premature optimisations.
There are many large projects out there written in say, Java (the old boring dog) that did not have to rewrite. I can add C# as another traditional corpororate language.
reply