107
'It's Literally the Gulag': Furious Meta Employees Speak Out on 'Soul-Crushing' AI Jobs
(www.ibtimes.co.uk)
this post was submitted on 15 Jun 2026
107 points (100.0% liked)
Work Reform
16656 readers
179 users here now
A place to discuss positive changes that can make work more equitable, and to vent about current practices. We are NOT against work; we just want the fruits of our labor to be recognized better.
Our Philosophies:
- All workers must be paid a living wage for their labor.
- Income inequality is the main cause of lower living standards.
- Workers must join together and fight back for what is rightfully theirs.
- We must not be divided and conquered. Workers gain the most when they focus on unifying issues.
Our Goals
- Higher wages for underpaid workers.
- Better worker representation, including but not limited to unions.
- Better and fewer working hours.
- Stimulating a massive wave of worker organizing in the United States and beyond.
- Organizing and supporting political causes and campaigns that put workers first.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
For sure, my lab has been doing that for a long time.
How is graphdb more ML-friendly?
If you’re doing PSQL (or any typical relational DB flavor), there’s a lot more complexity in terms of understanding the shape of the data, what joins to what, how to optimize queries, etc. Graph DBs are gonna be easier for a model to explore, since they can just do stuff like “I want to see tests with samples that have reactivity to mutation ABC on chromosome 14 over a threshold of X”, which is a lot easier for an ML agent (or less experienced developer, or even a molecular biologist with limited CS/DB experience) to just intuitively evaluate correctly using the syntax of GraphQL than it would be trying to do a shitload of joins between 6 or 7 tables in PSQL.