The 15 worst ways to kill programming productivity

Meetings, know-nothing managers, productivity metrics -- here's what's threatening to slay the next generation of great software
  • 1 of 17

Credit: Real-illusion

15 programming productivity killers

The product had to ship yesterday. Users are screaming about a missing feature. The boss's boss says we better get moving or the ax will fall. Nothing ever works as well as it could.

Everyone wants the code to flow like water from a fire hose, but no one wants to give developers what they need to get the job done. The same boss who wants the job finished yesterday won't hire more people, buy faster machines, or do any of the dozens of things that make it easier for programmers to get work done.

Here are 15 roadblocks to programming progress. Our informal survey was surprisingly easy. When the developers suspected they were talking with a sympathetic ear, they poured out their complaints.

Return to slideshow
Additional Resources
Join the discussion
Be the first to comment on this article. Our Commenting Policies