> In the layoff notice, which doubles as a note about Zuckerberg’s ongoing “year of efficiency,” Zuckerberg devoted an entire section to the question of “in-per

> In the layoff notice, which doubles as a note about Zuckerberg’s ongoing “year of efficiency,” Zuckerberg devoted an entire section to the question of “in-person time.” His conclusion: In-person work trumps remote work for productivity, at least for new employees. I can understand this argument. With regards to productivity, new employees, especially when young, might not have the discipline to focus on remote work while working from home. When I started working remotely as a try-out, I certainly didn't perform on my best, and I regret this. At the same time it was a lesson learned and at subsequent companies I performed better as a remote worker each time. So it's also a learning process. As such, perhaps it's a good idea to allow part-time remote work for new employees, optionally growing to full-time remote work if possible after many years. For example: - First year: work full-time from the office, if performing well ... - Second year: allow a day for remote work, if performing well ... - Third year: allow two days for remote work, if performing well ... - Etc... I think experienced (older) developers who've already worked remotely for various companies should however be able to start working at least part-time remotely, if the work allows for it. For people that just graduated it might be a bad idea. With that said, after working many years remotely, I'll soon be working again on location. The company that I interviewed prefers to keep everyone in office every day. However, for me they did make an exemption for 1 day a week, due to circumstances (girlfriend and daughter living a couple of hours away from the city and not willing to relocate). So I'll be the only employee working 1 day a week from home.