The three most prevalent themes in the discussion are:
-
Skepticism Regarding the Research Quality and Conclusions: Many users questioned the validity and generalizability of the study, noting its limited sample size and reliance on potentially biased software engineering metrics.
- Supporting Quote: User "jacquesm" stated, "Imnsho this paper is very low quality" and criticized the sample size, concluding, "They looked at one entity... Imnsho this paper is very low quality."
-
The Trade-off Between Short-Term Output and Long-Term Development/Mentoring: A central point of consensus mirroring the paper's abstract is that while proximity aids long-term growth (especially for junior staff), it can come at the cost of immediate productivity due to increased interaction/distraction.
- Supporting Quote: User "delichon" summarized the core finding: "We find being near coworkers has tradeoffs: proximity increases long-run human capital development at the expense of short-term output."
-
The Role of Remote Work in Employee Management and Accountability: The discussion heavily featured arguments about how remote versus in-office setups affect management practices, especially concerning trust, onboarding new hires, and preventing fraudulent work habits (like holding multiple jobs).
- Supporting Quote: User "Aurornis" argued that remote work requires new criteria for evaluating trust, stating, "In person accelerates onboarding for all the reasons I mentioned above. Itโs not a game of trust or โcarrotsโ." Conversely, user "AnimalMuppet" dismissed RTO mandates as control mechanisms, asking, "Did you ever hire any duds when you were not hiring remote?"