The text analysed
Why remote work is destroying our industry
I have now managed remote teams at three companies, and the pattern is unmistakable. In every case, the engineers who worked from home shipped less code, attended fewer design discussions, and were the first to leave when things got difficult. Remote work simply does not function for software teams.
Consider the evidence. Yahoo ended its remote work programme in 2013. IBM recalled thousands of remote staff to offices in 2017. Best Buy abandoned its results-only work environment. Three of the most recognisable names in technology looked at the data available to them and reached the same conclusion. That is not a coincidence; that is a verdict.
The studies claiming productivity gains deserve little weight. Most of them are produced by researchers who themselves work remotely, or funded by the very companies selling video conferencing software. It is hardly surprising that people whose comfort depends on an answer manage to find it.
The most vocal advocate of remote work in our own organisation is a junior developer who has never managed anyone, has been with the company for eight months, and by his own admission has not been in the office since March. It is difficult to take seriously a theory of team management advanced by someone with no experience of managing a team.
None of this is to say people should never work from home. An occasional day is fine. But the idea that a serious engineering organisation can be run without a shared physical space is, on the evidence, wishful thinking.