|
|
|
|
|
by pc86
2203 days ago
|
|
At the same time if they're willing to do 60 hours a week of work (not if it takes them 60 hours to do 40 hours worth of work) they should probably be pointed out positively in the team meeting for putting the effort in, and privately told that it's probably not maintainable in the long term, and if they need to work that much to meet their objectives they have too much work. But I don't see anything wrong with praising more output under the right circumstances. Everything ebbs and flows. As an IC there are times I go 3-4 days without a single commit. And there are times I have commits for 12 days straight because I'm on a roll. I've been fighting for an "unlimited with minimum" vacation policy for the developers at my current job for a while now. It was fight to get the base increased from 2 weeks to 3, and the system doesn't allow negative PTO balances, which seems kind of draconian to me. But I'd love to see my coworkers taking 4-5 weeks a year. |
|