Because "get it coded fast, we'll worry about resource-related problems in a future release" is a winning strategy if you expect to never hit your resource limits.

... when you have to prove your identity to submit a job application, much like how banks in the United States are required to verify identity before opening an account for a new customer.

I see what you did there.

Expect AI-written material to be put through a "cleanup to make it look less like AI and more like a person" post-processing step in the very near future.

It's probably already happening.

modern safety features and modern fuel economy.

OK that may mean a 2020s car with a 1970s user interface. Minus the 8-track, I don't need that.

Multiple places in the USA. Sorry I couldn't be more helpful.

Back in the early days of cable, I sometimes switched to dialup because of high packet loss on the cable connection. The dialup might have been slow but it was as solid as a rock.

A decade earlier I would sometimes throttle my modem to a slower speed for similar reasons.

... for slower technologies!

https://www.wired.com/story/fl... (may be paywalled by the time you read this).

One person's "OMGTHATSSOSTUPIDYOUAREANIDIOTIFYOUTHINKTHAT" is another person's "hmm, I haven't thought of things that way, tell me more about what you think so I can contemplate it."

We need more people in the second group.

I don't know how IPOs work in China but if this happened in the US, it would indicate the IPO price was set way too low.

The idea "IPO spike" is about 0 or maybe a little bit above 0.

If it drops on the first day that's obviously bad.

If it's goes up it means the company left money on the table. Sometimes its good to leave a little money on the table to give the IPO underwriters an others a reason to stay excited about your company.

Um, yeah, if you say so.

They did back it up.

They forgot the other part: Keep the original.

Or to put it another way: Have two copies that are extremely unlikely* to be erased/rendered useless by the same event or series of events.

*if a planet-killing asteroid hits, well....

Some people can heal minor loss of enamel.

Sometimes when a "big gorilla" (Microsoft) has a bug that is breaking you, the only practical thing is to code around it.

Especially if competing software isn't experiencing the same user-visible issues that your software is.

You may be morally right but shaming the gorilla without putting on your own band-aid is going to cost you users in the short run.

Besides, Microsoft's coders have their hands full finding and fixing security bugs before AI-equipped Black Hats find and exploit them.