I remember the Internet before Eternal September. You need to go back at least that far.

Not a financial person either, but wouldn't writing it down mean that a company no longer considers it to have value? Is there something unique to the hardware they use for search-specific AI that prevents it from being leased out as part of Google Cloud or being used to run other teams' models?

It's a disco inferno!

Free speech has never been free as in beer, or at least not at any meaningful volume level. Talking to a single person was free, but that's not going to spread your ideas very far or very quickly. In the early days, you paid scribes, but that would cost you money. Later, the printing press brought the costs down, but you still needed money. Radio and TV made it possible to reach even more people more quickly, but at a significantly nonzero cost.

The Internet is no different in that regard. In theory, you can always spin up your own server and post anything you want to. But that won't guarantee that anybody is going to actually visit your site. To get eyes, you'll still have to buy ads, etc.

Maybe, maybe not. That might only stop the AI from accessing the account, That does not stop hackers from getting AI to give up your passwords. I do not assume AI security it good enough right now to stop someone from prompting to get past the security.

I mean people have probably sued lawnmower companies because they were not warned to not to lift the mower with their hands when it was running. For every warning sign you see that you think it is stupidly obvious, there was probably someone who did exactly what was warned.

I always thought that coding questions during interviews were stupid anyways even before AI: it's information that one can simply look up with a simple internet search or programming book.

If you could learn to code with one simple internet search and having one book on your shelf, then you'd be right. Also, ha it occurred to you that you've been asking the wrong questions?

The only reason to ask programming questions is to figure out if the person was "fibbing" on their resume about their skills.

Kinda. That's the point of an audition. A substantial number of programmers can't write a simple program in a language of their choice or read existing code they're not already familiar with. I know there are companies that hoover up loads of mediocre people and they just kind of grind doing tiny amounts. And I'm pretty sure some people can only code by randomly permuting code in an existing codebase and seeing what happens.

Plus it shows absolutely nothing about their interpersonal skills, which are as important to be a valued member of a development team.

Gosh it's almost lie you can ask two interview questions or even 3! You don't need to ask a single question than answer every topic.

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.

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.

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.

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.

No one is forcing you to upgrade your iPad every 2-3 years just like no one is forcing you to upgrade your iPhone every year. Some people want to upgrade; that is their choice. For some people, they need an additional iPad for their children/spouse etc. For some, their iPad met an unfortunate end. For most of us, we upgrade if and when we need.

The iPad mini costs more than the base iPad because the base iPad is using a 4 year old chip. The base iPad in the current lineup as far as I remember got the oldest chips. The iPad mini is not cheaper than the iPad Air or iPad Pro.

The iPad does not have cellphone chips so using it as an iPhone is simply not possible. This is known. Not sure why you think Apple is trying to screw you over if you cannot use it as a cellphone when it is not a cellphone.

actually they rise because lowest 20% welding jobs are done by ignorant people just sputtering snot with chinese MIG kit.

Hey that sounds like my welding!

It's amazing how few programmers are willing to use a profiler, even if you show them how and why.

Yep. I think it's flat out arrogance often. I KNOW why things are slow.

"I'm a die hard Firefox user" - same here but Mozilla has made some really bone-headed decisions over the years.