3 ms·
I think it depends on the project. I've spent the odd weekend starting on Friday night and finishing on Sunday morning (although that doesn't happen now with a
by iuguy 16y ago
I think it depends on the project. I've spent the odd weekend starting on Friday night and finishing on Sunday morning (although that doesn't happen now with a wife).
Years back I started writing multi-format shellcode, which required me to learn 4 different OS and 3 different chip architectures to the point where I could get assembly running across all of them. That was an insane project that started out as get shellcode that worked on Linux and Freebsd/x86 and just ran and ran as I found more things to add in and tweak. Then I'd sleep through the whole of sunday and turn up for work on monday.
On the other hand I've worked on projects in my work time that are so mind numbingly dull that I've spent 4-6 hours a day actual programming, come home and collapsed in a heap.
It sounds to me like you're going past your wall and it's not flexible. You need to qualify and stick to your limits. The gym, diet and smoking side of things is a good idea, but not enough.
How's your sleep? I find that's the biggest factor in my day.
- netmau5 16y agoI can identify with you on boring stuff, even a few hours of work can be draining there. Not all parts of coding are equally interesting. I should probably work on my sleep schedule. I get about 5-6 hours a night on a weeknight and 10 on the weekend. I have a seriously difficult problem going to bed before 2am, but fortunately my job doesn't expect me in until 9 or so.
- iuguy 16y agoInteresting. How much caffeine do you get through in a day, and when is your last caffeinated drink?