3 ms·
50%, I'd say. Breakdown: - Reading code: 20% - Writing code: 10% - Debugging code: 20% - Meetings / administrata: 10% - Other productive tasks: 10% - Goofing o
by snicker7 6y ago
50%, I'd say. Breakdown:
- Reading code: 20%
- Writing code: 10%
- Debugging code: 20%
- Meetings / administrata: 10%
- Other productive tasks: 10%
- Goofing off: 30%
- daveslash 6y agoI'd say less than 2%. These are ball-park-guesses... -Reading Code: 3% -Writing Code: 2% -Debugging: 15% -Meetings/Administrata: 20% -Docmentation/Paperwork: 20% -Testing: 20% -Other productive tasks: 15% -Goofing off: 5% Note: When I say "debugging", it's often not debugging code. Sometimes it is, other times it's user-error, hardware malfunction, mis-understanding of the spec, etc.. A good chunk of debugging time is spent eliminating software as the failure. I work on highly regulated medical devices and their connected systems.