> I am more worried about the individual lounging on their couch, halfway through a 6 pack of IPA getting in some of that game of thrones re-watch, while the r

> I am more worried about the individual lounging on their couch, halfway through a 6 pack of IPA getting in some of that game of thrones re-watch, while the rest of the team is mopping up a shitty merge to master wondering where that individual may be at 11am on a Tuesday. I've had these scenarios in a 9-5 office job - eg. someone merged in some shit that broke migrations, CI takes forever to run so they don't catch it, the next day they are off and now I'm there touching systems I know little about just to revert my setup to a working state. I think if you can't rely on people in your team to be professional/competent it's going to be shit no matter where you work. That being said managing flexible work hours is really hard, it's especially hard if you're bad at estimating how much is acceptable to deliver in some time frame. If you always give estimates based on what you're capable at your ideal 8 work hours you're going to sink a lot more time than 8 hours a day - especially if you allow yourself to be distracted. I try to give my estimates based on 4 productive hours per day.