Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics.
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
That is not quite the quote, and its meaning changes significantly.
“Worker smarter, not harder”. Means that when a challenge increases or you are wanting to do better/faster/more to step back and think about your methods instead of just brute forcing the problem.
No one that says should mean “do not work hard”. That is the complete wrong meaning to take from this statement.
This. I used to do assembly, the reason I was great at it wasn't that I pushed myself to the limit to make each thing as fast as possible, it's that I built everything in batches so I didn't have to transition between steps on each individual part. If something slowed me down, I'd make a tool specifically for that tedious task. Don't waste energy trying to make a bad system work.
Yeah, when I worked in factories, I wanted to do better, just increase my numbers because I like improving. I looked up to the people who would be casually doing their job while doing way more output than I could and from that I could easily tell that there were better ways than what I was doing.
I got the best results from things like optimizing my foot positions to reduce steps, thinking about how objects needed to be oriented before I picked them up, finding areas where things could be parallelized (like only pack a part while the machine is building the next one), reducing context switches (like if there's 5 stages, do a bunch in stage 1 before moving on to stage 2 so you spend less time picking up and putting down tools).
Once you've optimized the way you're doing the work (work smarter), then you can add speed to it if you want it even faster (work harder). If you skip that first step, you can end up working your ass off only to still be embarrassed by the guy that looks like he's half asleep.
Perfect example. Thank you!