I'm doing lots of coding and find that even when i'm well rested and in otherwise good conditions, after n hours of coding or studying hard (using pomodoro technique, going for high density rests and so on) I just get so spent/tired I'm unable to code or study hard until the next day. This is naturally quite inconvenient because it means I reach my objectives in slower fashion.
Is there anything wrong with me? How can I take the number of hours I can work on hard coding problems towards the number of hours I can be awake?
Thx for the Advice,
Santy
Advice 1: validate your assumptions. You seem to imply that maximising work hours maximises productivity. It could well be that you are above-average productive to start with, so you get more work done in a shorter amount of time. If that's the case, maybe you hit a limit that isn't mean to be passed.
Advice 2: validate your baseline. Are you in good shape and health? How does your productivity compare to peers? Are you working on harder topics than your peers? Is your work environment distraction-free? Is there something (health, personal life, financials etc) bothering you?
Advice 3: validate your motivation. Are you enthusiastic about the topic? If not, balance that against your goals and if you still think you need to do it, trick yourself into finding the work motivating [1].
Advice 4: experiment with different modes. I didn't know about the pomodoro technique before. After a short read, I don't think I would enjoy working like that. Breaking every half hour kills my flow, and 5 minute breaks are too short to get anything done.
[1] https://upload.wikimedia.org/wikipedia/en/a/ab/Simpsons6x13....