▲ | koyote 4 days ago | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> the number of people who work as well (or even better!) from the home is not zero, but the number of people who claim there's no difference and then end up doing significantly worse work, become a massive pain to get a hold of, become less motivated, etc. is way way higher For me the reverse thought always comes into mind: "The amount of tangible work achieved when in the office is close to zero". Countless chats, interruptions, distractions, meetings you can't easily get out of, getting in late due to traffic, having to leave early due to childcare, etc. Even if a person spends half a day WFH not doing any work, it will still be more productive than being in the office. When I say work, I mean actually producing tangible assets. Brainstorming, design, anything that requires high collaboration, works much better in the office when everyone is in attendance. The end result of this is that the most productive environment for software engineers is a mostly WFH schedule with anchor days in the office to hash out the collaborative tasks in big blocks. This translates into 1-2 days in the office depending on the team and the current phase of the development lifecycle they are in. If you have a person in your team who consistently does not perform any work when working from home, then that is a performance management issue that should be dealt with like every other performance management issue. I do not really see why 'wfh' makes this special. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | BoorishBears 4 days ago | parent [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I should have realized that my comment relies on too much nuance for the average person who's crying themselves sick over RTO to engage with in any reasonable semblance of what it actually says. If you want to try reading it again with a clear head and not engage with the strawman you're building, you'll notice it doesn't make any claims to the effect of: - why offices work - that offices work for everyone (it claims the opposite) - that no one does better at home (it claims the opposite) - that no org can make WFH work (it claims the opposite) - that performance issues shouldn't be dealt with All it says it that empirically (and of course, limited to my experience and experiences shared with me), a lot of people, specifically in large companies, perform worse with significant WFH. "WFH" makes this special because it's organization wide, in massive orgs: like I specifically mentioned "significant WFH" and "large headcount" in the same sentence, can I really spoon feed this any harder? I think WFH can work for some people, but when it's significant amounts in large headcount companies, it starts to fall apart. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|