Shocked I tell you…shocked!

Read the comment above yours, that’s where I learned about it

Not sure if sarcasm, but the article is actually super insightful into a few different methods bad actors could use to accomplish the same feat (short of giving them a formula, from what I can read, but I’m not a battery maker)

Are you like building a mobile app or have 100k tests or is it just super slow?

It took me an embarrassingly long time to figure out what a “Pugina” was, should have just clicked the link

The best part of starting a new job is that you don’t have years of built up “status checkins” that we’re never cancelled for some reason.

Agree completely, this is how every machine learning system is built! Maybe this one was taking too long, but that’s exactly what beta’s are meant to prove.

I feel like this section is rather disingenuous for the article author to just drop without mentioning that this is how all machine learning models are trained. The idea is that now (and for the next year or whatever) it’s trained manually until the system is good enough to do it on its own with a good enough accuracy rating to not lose money.

Now, since Amazon is shuttering this, it’s totally possible that they determined they’d need too many years of training data to break even, but at the very least this is standard industry practice for any machine learning model.

That’s never been done before, we’re part of history!

There’s no way the model has access to that information, though.

Google’s important product must have proper scoped secret management, not just environment variables or similar.

React ugh, everybody is using NextJs these da- …oh, what’s that? We’ve moved on already?