Hacker News new | ask | show | jobs
by Moissanite 1307 days ago
> I'm confident that the willingness to pull out the stops and get it done has lead to promotions, raises, and freedom to scale down my workload during slow times.

If I had this confidence, I'd put in the hours cheerfully; I've had spells of 80-100 hour weeks in the past and invariably it was caused by sales people or managers over-promising without asking a technical expert, and could have easily been avoided. Doing the hours resulted in some vague gratitude at best.

Now (in a new role), I can see clear evidence of things which are correlated with promotion, but working long hours is not one of them.

1 comments

I agree that hours by themselves are largely meaningless. I should be more clear and specify hours when necessary, and not some arbitrary deadline. For example, I've been on projects that are stuck or failing and each day they are down or behind costs 7 digit revenue per day. Being the person capable and willing to work overnight to fix it or put in long weeks until it's done bought me a lot of Goodwill, promotions, Etc. I still have directors that mention them in all staff meetings after 5+ years.

Of course working 60 hours a week on some bullshit project with no impact will not have the same results.