Always work below your capacity.. if you give 100% that will always be expected. 70% gives you some wiggle room, plus you're the hero that saves the day when you kick it up to 100.

Also 100% all the time = inevitable burnout

You can always use
"I'm Givin' Her All She's Got, Captain!"

I still have to learn this.
I know about it but still..

It's called the "Scotty principle"

@irene You for real or you're trolling me?! 🤔
It's from Scotty in Star Trek, not sure if it's exact quote or from which episode..it's just something I just know but not sure why or from where.. o.O

This will however give management the power to shit on your estimations and ask for more features in less time.

Just made this formula up in my mind: actual_work_capacity_factor = desired_pay / actual_pay

What do you think?

P.S.: If you are over 1, you should raise your standards! :D

@Ederbit they can shit however they want... I wont deliver what I said can't be done.

Timeestimation
Developer: "Hmm.. 1 Month but I take 3 bcs customers dont know what they want and teh occassional update which will fuck up everything"
PO: "He said 3 Months so I plan rather 9 just in case" <--- from some rulebook on how to interact with developers and "understand" them
CEO:"9 Months so its 1 Month" <--- Made a promise on a party while being drunk and being ceo, dont trust your employees and keep them on edge

You can’t be promoted if your work where you are now is indispensable.

best thing I read today :D

Project managers: *internal screaming, coupled with external screaming*

I once read a nice quote like: you should never code with 100%. Because you need per definition double the power understanding and debugging the code. So you should only code with 50% or you will never understand your own code. Or something like that. I found it on cat-v if someone wants to look