oxfordmale

Condoleances

I am happy to pay for the BBC licence fee if they stop harassing old grannies.

The real problem is social media. Their machine learning algorithms are optimised to boost toxic content, as they result in more engagement (time spent). This is a fundamental trait of humans. Even babies look at angry faces longer than happy faces.More time spent means more advertising revenue.

It means the current generation gets exposed to a lot of toxic content all in the name of driving advertising revenue. In the olden days you could get everything, but it wasn't forced down your throat, or rather your reels.

Outsourcing comes and goes in waves. Good talent in India and the Philippines tend to work for FAANG companies, often at very comparable salaries to the west.

The remainder of the talent tends to struggle with some of the outsourced work, but with AI they can now give a semblance of competence.

In the UK a major retailer, Mark and Spencer got hacked after outsourcing work to India. They couldn't fulfill orders online for months, and they are now reducing the amount of work they outsource to India.

We will see something similar happen to other companies in a year or two, but until then we just have to tighten our belts and hope we don't get layed off before then.

Meta is definitely at the forefront of recommendation algorithms built. However, the leadership team likely has shifted focus to LLMs.

I think you might be reading a bit too much into this.

He’s been with Meta for 11 years and is likely in a very comfortable financial position, given the substantial stock options he’s received over that time.

He also mentioned the arrival of a new child, and it’s well known that Meta's work-life balance isn’t always ideal.

On top of that, Meta, like many major tech companies, has been shifting its focus toward LLM-based AI, moving away from more traditional PyTorch use cases.

Considering all of this, it seems like a natural time for him to move on and pursue new, more exciting opportunities.

But is is a partial outage only, so it doesn't count. If you retry a million times everything still works /s

I am not sure that us the right question to ask.

The real question is how much utter garbage it produced in those 30 hours without human supervision.

The design is fundamentally flawed, with queries in close to hundred .js files.

Perhaps you marker and sell a few, but it looks insecure and would be hard to refactor.

Thanks for sharing this, very brave.

Looking at the code, there is a good chance this codebase is vulnerable to SQL injection.