this post was submitted on 26 Aug 2023
214 points (81.8% liked)
Linus Tech Tips
3791 readers
3 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
They did an okay job of addressing the accuracy issue, but failed to even mention the issues of workplace culture and absurd quotas.
It does not matter if workers start and stop their shifts at particular time - as strictly required by law - when the amount of work they are expected to do within that time frame is unrealistic.
Upping the expections for quality, without lowering those for quality, will only make things worse for everyone working there.
Not to mention it didn't even touch on the note serious allegations of sexual harassment.
Don't worry, they lowered the quotas (while adding a shitton of process).
Linus just can't seem to get over the fact that employees should have some free time at work, especially in creative or highly technical fields. It's all about time being money.
If someone wants to take longer on a project just because they want to, there should be time for that. Salaried employees shouldn't have to account for their time down to 15 minutes increments outside of contracting work. The fee for that kind of time accountability is about 4x what a salaried employee generally makes.
If you do it right, having processes that are well reasoned and adhered to is a net time saver. I've been on teams with many different levels of processes. I can say from 20+ years of experience that there is nothing worse than a pipeline with too few processes. When every writer has a different way of delivering information to the editors, that's a time waster. When every tester has a different way of putting together a spreadsheet to hand off to the graphics department, that's a time waster.
Also, processes are supposed to serve the needs of the staff. Not the other way around. If a process adds too much effort for little reward, you can always change it or scrap it. Ideally, you'd have someone on staff whose job it is to manage your process flow, facilitate handoffs, and make periodic changes to the processes to close up inefficiencies and pain points for the staff.
Absolutely agreed. Work gets done faster with the correct processes. If I don't know what to do when I have issues, I have to pester multiple people until I get to the right person that can handle it. If I knew exactly where to go and what to do, I might not even need that person in the first place.