Linus Tech Tips

3815 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

7heo@lemmy.ml

2367

Madison on why she quit (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by 7heo@lemmy.ml to c/linustechtips@lemmy.ml

560 comments fedilink hide all child comments

Some updates I got from threadreaderapp:

Link to the thread provided by @lbj@lemmy.world.

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

[–] mog77a@lemm.ee 28 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.