I've noticed over the years, that my progress tends to be highly seasonal. From... oh about this time of year... until October, when the days start becoming dramatically shorter and I start rediscovering hot apple cider, I really don't make much progress. That's because I'm out running, mountain biking, hiking, planning hikes, on vacation or planning vacations. I'm simply not inclined to sit for hours at the computer during the warm season.
Then there is my photography; which is often combined with my hiking. I've got about 300 pics in google earth and another 50 or so queued up and ready to upload to panoramio (from where they go into GE).
http://www.panoramio.com/user/1275355?show=best
Oh and I've discovered something new, which will probably also be a time vampire for a while.
[YouTube]https://www.youtube.com/watch?feature=p ... gR6jbiD2yA[/YouTube]
Edit: Does anyone know why the linked youtube clip does not work?
Why Cayle's progress is seasonal
-
Jackolantern
- Posts: 10891
- Joined: Wed Jul 01, 2009 11:00 pm
Re: Why Cayle's progress is seasonal
Typically I would say "cut out the distractions", but that is a hard sell when the distractions are keeping you healthy lol. Maybe try to schedule a time each week where you will sit down and at least do something during your "off-season".
The indelible lord of tl;dr
Re: Why Cayle's progress is seasonal
The outdoors stuff seems a perfectly valid reason.
But I'd say, for example while riding, think about when you're going to start programming next - work out an actual date. And start thinking of each part of programming you're going to work on next and how many days you assign to it. Write down all these dates.
So when it finally gets back to programming season* you're not going to spend your time planning then.
You're mind is going to have alot of free time as you do physical stuff - so do some planning in advance, if not actual programming. Because planning for coding is pseudo coding in a small way - which all helps.
That's my advice!
* No! Rabbit season! No! Duck season!
But I'd say, for example while riding, think about when you're going to start programming next - work out an actual date. And start thinking of each part of programming you're going to work on next and how many days you assign to it. Write down all these dates.
So when it finally gets back to programming season* you're not going to spend your time planning then.
You're mind is going to have alot of free time as you do physical stuff - so do some planning in advance, if not actual programming. Because planning for coding is pseudo coding in a small way - which all helps.
That's my advice!
* No! Rabbit season! No! Duck season!