10 reasons to write code at home
Do you write code when you aren't at work? Do you create much off work time or is work your only outlet?
If you are a programmer writing websites and web site coding at work, do you even want to touch the stuff and do a personal or even worse a friend's webpage?
How about folks that program on the AS/400? Do you even have access to do that kind of coding at home? Or do you sneak a peak at other coding realms, like C++ or C#? Perhaps Perl or Ruby is your language of choice for playing around?
For me, here are 10 reasons to code when not at work...
1) No one needs to approve me to work on it.
2) I can control the environment.
3) I can work in a language I don't have available at work.
4) I can try out features and fun stuff in code that we don't have time to explore at work.
5) Lots of fun tools and the tools I choose.
6) Playing music while I work.
7) Lighting I can control.
8) Noise I can control.
9) Snacks close at hand...hey a guy has to keep his shape...no comment. :)
10) I control the machine - worth a fortune.
So what about downsides or determents for coding at home? Burnout? Boredom? Hate programming for a living?
What do you think?
Tojosan
3 thoughts:
I've done some Visual Basic programming, I'm not that good at it, but I've made quite a few simple programs. To see my programs, go to this page of my website: http://www.freewebs.com/compnerds2/monkeymoosesoftware.htm
I've programmed a few pet projects at home but I've basically let programming be a worktime activity. When I win the Power Ball and retire as a professional programmer, I'll go back to coding strictly for fun. Probably I'll start with Cocoa (Objective-C) and move on to Ruby on Rails!
As one or more of you know, I dabble with coding at home. :)
This last weekend was Ruby on Rails weekend! Woot, it too more than the advertised 15 mins though. Ha.
Hey, maybe I'll do one programming adventure each weekend that I do a food adventure. Heck of a plan.
Post a Comment