Earlier quoted context omitted.
> If your company doesn't believe that burnout is an issue and ignores your "no's" It's up to you to ensure that your "no's" can't be ignored. Really what shy programmers need is confidence and healthy boundaries.
And if you're not a shy programmer who has shown schedules, estimates, timelines, and are also trying to prevent those you manage/mentor from being burntout? Or what if your direct manager actually agrees with you! But your combined arguments are being shot down for reasons of growth, culture, or they decide to change the metrics so when you do say no, your performance plummets and they now have more power in convers…
"Do you want someone who will tell you want you want to hear? Or do you want someone who will tell you how much it's gonna cost?"