The Fallacy of Productivity in Software Development

When I started my first job as a software developer, I envisioned it to be movielike — perhaps something like working for NASA. I pictured myself collaborating on whiteboards, discussing architecture, and reviewing code with other likeminded people. However, the reality was quite different. I found myself surrounded by people sitting with headphones on, quietly, and barely exchanging messages via IM.

Over a decade later, not much has changed. The only noticeable difference is that code reviews became standard. As a matter of fact, many developers will openly state that they are most productive when left alone, without unnecessary stand-ups, questions, or meetings.

Yet the questions stand:

• Are they really productive?
• Is working in isolation the best way to build quality software in the long run?

First, it’s worth exploring what is meant by development productivity. While there is no consensus, most sources (including Wikipedia) point toward a similar definition: