- Writing Code (programming, coding, hacking away)
- Overhead (Building, Deploying, Hardware, Software)
- Communication (Meetings, Chats, Teleconferences, etc)
- Problem-Solving (Debugging, Profiling, Performance Tuning)
- Firefighting (Crashes, Slowdowns, Security, etc)
- QA (Manual & Automatic Testing, Code Reviews)
- Strategy (Architecture, Refactoring, Thinking)
- Process (Bureaucracy, Reporting, Time-keeping, etc)
- Procrastination (slashdot.org, reddit.com,. Twitter, Facebook)
It means that
- Devs spend less time writing code than you might think. The median is 15 hours, programmers spend about 3 hours each work day writing code.
- Devs spend more time on non-development activities than you might think. For each coding hour, devs spend nearly 30min in meetings, reporting, writing emails and dealing with timesheets
- Devs spend more time fighting fires than building solutions
Information is taken from
http://zeroturnaround.com/blog/developer-productivity-report-part-1-developer-timesheet/