A big chunk of most software is about component assembly. You use frameworks and libraries. Stitch things together and make things work.
Contrary to what most people say, 80 hours a week is not abnormal or counter-productive. It is probably counter-productive like if you do that for 2 years. But for a week? 3 months? 6 months? For most people who really are interested in things, this is no problem. I can vouch for this personally. When I am interested in things, I can work on code for months and I don't even keep track of time. And all of my projects don't even involve money.
Back to my first paragraph, super-duper-brain work can be very draining and I cannot imagine working 80 hours a week in that case. But for most pulp software (like I do - hack on node.js, Qt, WebKit, HTML5..) bring it on. I can easily do things at a stretch with no fall in productivity. In fact, I find it counter-productive if I don't work on these problems in a stretch since I lose context. (WebKit debugging anyone?)
Comments
A big chunk of most software is about component assembly. You use frameworks and libraries. Stitch things together and make things work.
Contrary to what most people say, 80 hours a week is not abnormal or counter-productive. It is probably counter-productive like if you do that for 2 years. But for a week? 3 months? 6 months? For most people who really are interested in things, this is no problem. I can vouch for this personally. When I am interested in things, I can work on code for months and I don't even keep track of time. And all of my projects don't even involve money.
Back to my first paragraph, super-duper-brain work can be very draining and I cannot imagine working 80 hours a week in that case. But for most pulp software (like I do - hack on node.js, Qt, WebKit, HTML5..) bring it on. I can easily do things at a stretch with no fall in productivity. In fact, I find it counter-productive if I don't work on these problems in a stretch since I lose context. (WebKit debugging anyone?)