>Much more difficult for collaboration especially for small questions
>Bad workers exploring nice policies
Pros-
>I can sleep/think about code without being paid. Making my solutions lower cost and higher quality
>Happier employees
>Potentially less micro management needed
As for people exploiting it, you should measure relative performance and not but time
One of my first startups I worked had a noon-4pm core hours. You had to be in by noon, and should stay until 4pm, the rest was flexible. I thought it worked really well for both early risers and late owls.
This is also easier said than done. How do you measure programmer performance? LOC is obviously not a reasonable metric. Closed tickets isn't either. It takes an experienced manager who understands code to understand what work is actually being done, and managers like that are rare and valuable.
- the company restaurant closes at the normal time (or all good stuff is taken)
- you still get that condescending look from early-birds
I definitely never got any bonus points for being at work before my boss.
In contrast, early-birds act superior while you are there.
As a result, there were people that worked 6am to 3pm(ish), 10-3, followed by 7-10 in the evening, 11-8, etc. I had a young child and handled school dropoff, so my hours were roughly 9am - 6pm. My boss, the CEO, was a workaholic who arrived around 10am and worked to whenever. I spent an amazing amount of time dealing with "where is everyone?" sorts of questions, despite the team running fairly efficiently and still completing work on aggressive schedules.
The solution was literally “come in any time you want as long as your projects get done” - what’s your objection? That everybody who wants to come in at lunchtime, and work until the small hours force themselves around your schedule because you have a family?
Even jobs that are quite flexible are going to want some overlap time and, even if an atypical schedule allows for a few hours of overlap, the reality is that people will get tired of always having to schedule around your preferences.
Not mainstream, but I think the idea has been popular for a while [1].
>6.4
>A manager went to his programmers and told them: "As regards to your work hours: you are going to have to come in at nine in the morning and leave at five in the afternoon." At this, all of them became angry and several resigned on the spot.
>So the manager said: "All right, in that case you may set your own working hours, as long as you finish your projects on schedule." The programmers, now satisfied, began to come in at noon and work to the wee hours of the morning.
[0] https://www.youtube.com/watch?v=ALaTm6VzTBw
[1] https://www.mit.edu/~xela/tao.html