Hacker News new | ask | show | jobs
by jypepin 2820 days ago
I don't agree with that, because the number of hours you work are pretty irrelevant when not in a butts-in-seats setup. Also, burnout is not really directly related to the number of hours you work.

Work should be focused on productivity, not hours spent. Employers, clients and managers have expectations of a quantity of work being accomplished for a specific budget, and it doesn't matter to them if its done in 2hrs or 200hrs.

1 comments

>"Employers, clients and managers have expectations of a quantity of work being accomplished for a specific budget, and it doesn't matter to them if its done in 2hrs or 200hrs."

You're assuming every project is fixed-scope, fixed-cost and variable-time. In my experience that matches a small minority of projects.

Although " fixed-scope, fixed-cost and variable-time" makes it easier, this works also in other situation, including variable-everything, part of a product team.

You are given tasks or projects for a specific budget (budget, for your manager is 1 engineer). They have expectations on what 1 engineer can deliver on average.

This is what people mean when they say "we care about output, not butts in seats".