4 ms·
"If you actually believe this, then you're not spending enough time coding. I'd say more like 50 to 80%." If you don't include debugging and thinking in that f
by j_baker 16y ago
"If you actually believe this, then you're not spending enough time coding. I'd say more like 50 to 80%."
If you don't include debugging and thinking in that figure (as the author does), 20% doesn't seem unreasonable. I seriously doubt that it's possible (or even preferable) to spend 50-80% of your time literally typing text into your text editor.
- bmj 16y agoI think it depends on the size of the team (and related teams) and the sorts of dev cycles you experience. I'd say in my case, including testing and debugging, I code roughly 50% of the time. That doesn't mean, however, that I spend four hours everyday coding and another four going to meetings, etc, etc. The pattern is often more like: code 85% of the time for several weeks, then drift into a period of considerably less coding as we review releases, work with other teams for product hand-off, offer training, and review bugs and issues.
- drunkpotato 16y agoIt's also true that we (humans) are terrible at self-reporting information like this. Not that you are lying, simply that you are most likely incorrect.