4 ms·
> for more than a few days Yes! But do occasionally fall on a grenade for your team. Pull one 12 hour day to get a deployment plan just right, to check that on
by jeffrallen 4y ago
> for more than a few days
Yes! But do occasionally fall on a grenade for your team. Pull one 12 hour day to get a deployment plan just right, to check that one last rollback scenario, etc. Plan 8 hours for a bug and then follow it for 24, if the rabbit hole it takes you into is important. Develop the discernment to be able to say "this is where I'm going to overwork one time this quarter". And say it, literally out loud if you need to.
You need to be able to look yourself in the mirror and say, "my boss counts on me" before you can go and tell him the same thing.
- H8crilA 4y agoWhy though? I don't want to overwork a single day per week/quarter/year. And I have absolutely no fairness problems with that. If it can't be done this week it will be done next week. It's your problem to deal with it, and my problem to make the tech work.
- jeffrallen 4y agoBecause knowing something is important to the organization and to you and choosing to do it is not overworking. It is delivering the necessary effort at the right time to end up proud of your work. And with a reasonable boss, there's nothing stopping you from knocking off early the next Friday.
- whitemary 4y agoNo, thanks.