Linus Tech Tips

3816 readers

1 users here now

~~⚠️ De-clickbait-ify the youtube titles or your post will be removed!~~

~~Floatplane titles are perfectly fine.~~

~~LTT/LMG community. Brought to you by ******... Actually, no, not this time. This time it's brought to you by Lemmy, the open communities and free and open source software!~~

~~If you post videos from Youtube/LTT, please please un-clickbait the titles. (You can use the title from https://nitter.net/LTTtranslator/ but it doesn't seem to have been updated in quite some while...)~~

founded 2 years ago

MODERATORS

[email protected]

2386

Madison on why she quit (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

677 comments fedilink hide all child comments

Some updates I got from threadreaderapp:

Link to the thread provided by @[email protected].

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 83 points 1 year ago (2 children)

My comment on the forums was very similar.

The key issue in all of this that they didn't address is that they're pushing too fast. There have been many red flags about Linus pushing people too hard to get stuff done too fast.

It doesn't matter what kind of "new processes" you put in place if people just don't have time. And you can't expect every employee to work as though they have 20% equity in the company. If you put more than 30 hours of work per week onto a full time, salaried employee, you're not going to get their best work, especially in creative or expertise-required jobs.

To do their best work, people need time to breathe. They need time to be able to talk to their coworkers about a problem without worry about pulling them away from their own work for 15 minutes. They need time to grab a drink or a sandwich while they step back from a problem and consider it from a distance. They need time to decide their previous work wasn't good enough and to go back and redo it. They shouldn't have to ask. Having to ask is a problem. Getting "no" back as an answer is an even bigger problem.

If you try to account for every 15 minutes, you're going to get shit quality product pushed out the door.

Madison brought this up. Employees have brought this up in videos. And Linus has raised red flags more than once. The biggest was with his equating doing things right to hours worked and directly to cash. That speaks to exactly this. People don't have time to do things right, and they don't have time to fix things.

The only way to fix this is to either hire more people (which you clearly can't afford), or allow your current people to put out less product.

[–] [email protected] 29 points 1 year ago

If you put more than 30 hours of work per week onto a full time, salaried employee, you’re not going to get their best work, especially in creative or expertise-required jobs.

Facts. If you claim you can work more than ~30 maybe 40 hours (that's really pushing it) a week in this type of work without output/quality falling off a cliff, you have lots of room for process automation from my experience. I don't think I do more than ~15-20 hours of actual active programming per week. If I have hard deadlines, pushing that out to 60-80 hours does increase output but nowhere close to linear output.

[–] [email protected] 5 points 1 year ago

And as other people said, she was expected to output that much social media posts, but now they post the bare minimum. Maybe she was being asked too much after all.