oo the burn
BlitzMax Forums/BlitzMax Programming/oo the burn
| ||
| Been doing a lot of blitz programming the past 2 months. Like 5 hours a day well into the night sometimes for 2 months. It's fun creating something, so hence the will to do it. But feel a bit of a burn now, not from the idea of doing it, but from sitting behind a screen hours upon hours. I live in the tropics, its hot and my work space is kinda cramped at home too, probably need a nice desk and space :) What do you do if you ever get a burn like this? Take a break from seeing code for a week? Do more theory or design work? I should mention that in between I have been doing nothing recreational, I have been devoting all available time to programming. Which because like I said it IS therapeutic in a way for me. But right now just feel a bit burned. I also have this thing, sometimes at the end of a marathon session of like 5-8 hours, I'll be stuck on something. I'll finally give up on it and come back the next day and in like 10 minutes ( I swear no longer) the issue that had me stuck is resolved, or the bug or quirk has been found. It has happened to me countless times now that it cannot be a coincidence, does your brain or mind just shutdown after a while of staring at the code? |
| ||
| Yup, that's all pretty common. Although I'm sure that the tropical temperatures would make it happen faster. :-? |
| ||
| I gave up coding outside of work because it was unhealthy for me. After years spent writing games in my spare time and waking up late on Sunday afternoons feeling as if I was wasting my life after having spent all of Friday evening and Saturday in front of the machine I realised there were better things to spend my time on and that I really was wasting my life sitting in front of a machine all day. Enjoy it while you can but don't let it master you. |
| ||
| damn, that sounds pretty bad Matty. I don't program for a living in my case. I recently made a transition from shift work to day work. Off weekends. I been doing just that. Friday evenings, all day saturday and all day sunday thing. So not for years yet :) |
| ||
| I also have this thing, sometimes at the end of a marathon session of like 5-8 hours, I'll be stuck on something. I'll finally give up on it and come back the next day and in like 10 minutes ( I swear no longer) the issue that had me stuck is resolved, or the bug or quirk has been found. It has happened to me countless times now that it cannot be a coincidence, does your brain or mind just shutdown after a while of staring at the code? Pretty normal. It's called "can't see the forest for the trees". Taking regular breaks is the best thing. If five hours is burning you out, try 18 hours. Actually, don't. |
| ||
| Have found the same thing... sometimes when you start staring at the trees you become too fixated to step back and see the bigger picture, and it's usually the bigger picture that you need to see the solution. Take a break man! Do some things totally off the computer for at least a few days. |
| ||
| I tend to program in stints, working relentlessly for a week or two and then stepping back, playing guitar (very badly), catching up on TV and playing the odd computer game. However, even during stints I make sure that at least one night a week is set aside for socialising - you have to stop some time. |
| ||
| I tend to program in stints I tried that once but I couldn't reach the keyboard.....oh, STINTS! Sorry, thought you said stilts. |
   |