Hacker News new | ask | show | jobs
by rsp1984 3064 days ago
My opinion as an employer: Sure, feel free to take your work hours as you like and WFH every once in a while.

Just make sure that overall your total hours are what we agreed to in the employment contract.

3 comments

It's probably different where you're located, but around here it's pretty much a given that an engineer will work more hours than what is written in the employment contract, even if they regularly come in late / leave early / WFH.

Imho flexible hours are a good thing as they remove the pressure to stay around doing nothing until late because you can't be seen leaving before 7pm.

> Just make sure that overall your total hours are what we agreed to in the employment contract.

What's the justification for monitoring total hours and not something more directly tied to business success? End users and profit margins (assuming your engineers are salaried) don't care about whether your engineers had consistent 40+ hour work weeks.

In my previous company, they has a name to distinguish these two kinds of metrics.

- Inputs are the things employees can act on easily, like the number of LoC written or the number of features developped.

- Outputs are related to business success, for example the number of customers, or the revenue.

The key here is to consider the external business environment as a complex machine, in which you put some effort, measured by inputs, and you observe the outputs as a result (reward). Because you don't know how the environment is going to respond, running the activity consists in adjusting the measures of inputs according to previous results, and trying to maximize those.

This is sane for business because executives can focus on maximizing the input metrics, without caring too much about the outputs, and evaluate separately the assumptions they made about the business (e.g. that x number of features requested by customers developped within 1 month increase the userbase).

It kind of looks like a reinforcement learning process actually.

> This is sane for business because executives can focus on maximizing the input metrics, without caring too much about the outputs, and evaluate separately the assumptions they made about the business...

That's basically the problem right there. If you treat the employees as a giant black box, you don't observe when workplace policies (that might not even work!) get in the way of human decency, let alone helping a diverse group of employees each flourish in their own way.

Employers instead sit around wondering why there aren't enough Latino engineers without even considering a remote work policy that would let engineers live in El Paso, Phoenix, Los Angeles, or Miami.

That problem I worked on all day? I'm still trying to solve it when I'm cooking, showering, washing dishes, etc. I'll solve it before I get to the office tomorrow. How should I track all that time?
By adjusting your pay rate.

As a society, we agree on pay for hours. We pay more for folks who bring more, better solutions during those hours. How they do that is beyond the employment agreement's scope.

Short of being a contractor with a fixed-price-on-delivery contract, we'll have to be content with that.