3 ms·
I agree. In my experience, "flexible work hours" is often code for "everyone works weird fucking hours so instead of having a set routine, you have to be quasi-
by awsthro00945 5y ago
I agree. In my experience, "flexible work hours" is often code for "everyone works weird fucking hours so instead of having a set routine, you have to be quasi-available at all times to respond to the person who decided to wait until 8pm to do the work you were waiting on". It's great for the person who needs flexibility, and shitty for everyone that depends on that person.
Flexible working arrangements are great when the team is able to asynchronously work, but I have yet to see a team that really does asynchronous work right.
- dopidopHN 5y agoExcellent point. If the expectations is to not respond right away and not be available right away. It can be fine. I’ve seen it work. But it require discipline. In my situation the time difference were too striking to hope having synchronized interaction, and the team built on that habit. But then one day we had a major refactor in our orgs and that was gone.
- mhitza 5y ago> I have yet to see a team that really does asynchronous work right. I think the Linux kernel developers can be considered the biggest software team that does asynchronous work, and it works just fine. Honestly just some basic mailinglist software installation goes a long way. And an organization can still have a process in place on how to get synched when its needed (scheduled calls, impromptu emergency response situations, etc).