Hacker News new | past | comments | ask | show | jobs | submit login

> Any company that forces programmers to work in open-plan environments is either ignorant, or just doesn't care.

I'll agree with everything you stated but this as the terminology you use makes it sound malicious. Instead, I can imagine consulting firms with plenty of talking points convincing a decision-maker they were right. Furthermore, we cannot assume any particular environment will be optimal for all employees for all companies. "Productivity" was studied, but has branched into more concrete terms, rather than been solved. Even with a company that is open to helping improve conditions, what should they do, how long will the ROI take, etc.

While I accept the assumption of being more productive in an enclosed space, could you point me to a specific paper? Mostly because "productive" is not as well defined and is more a generalized term (respectfully, many terms can fall under the "productive" umbrella). I ask about the paper because a) I'd be curious to see how they define and measure productivity, and b) it may be beneficial for student learning (another knowledge-specific domain)




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: