4 ms·
>The primary task of a programmer is writing code, which involves sitting at a desk and thinking and typing This is most definitely is not the case for most de
by fudisgud 13y ago
>The primary task of a programmer is writing code, which involves sitting at a desk and thinking and typing
This is most definitely is not the case for most development positions.
Oh yes, there's plenty of code to write if your a developer. But there's communicating with management/qa/business dev/other developers/support as to what to work on, progress on tasks, clarification of requirements, bugs discovered, issues raised, tests to run, ways to program, etc. Open spaces will encourage these conversations to happen more organically instead of scheduled strictly around meetings.
At the end of the day, companies wants developers to crank out code as much as possible, but what they need is development to communicate effectively - among themselves and across teams. Hence, open floor plans, even if it reduces the quality of code.
- JoeAltmaier 13y agoAnd that's where the disconnect happens. I assume you are a manager? Because status meetings are useful for you, but absolutely a disruption to the developer, a time sink and a sap to energy and productivity. To imagine we want our work environment structured around Reporting what we do, and not around actually Doing the work, is the tragic mistake of our industry. And its largely why I became a consultant/contractor instead of a corporate employee.