New Year’s Resolutions for Java Coders
0 Comments Published by Tahir on Tuesday, July 31, 2007 at 12:07 AM.
An interesting article I found on [1]. Here I have pasted some of the points, making myself how many I can implement. Which ones if any would you adopt from this list...
I will realize that design patterns are a guide, not a religion.
I will bother to research the security issues relevant to my work.
I will spend an hour teaching a child the rudiments of programming, even if it's just "Hello World" in JavaScript.
I will learn how to use Unicode.
I will not respond to requests for help by informing the questioner that they are not only asking the wrong question, but should change the language they program in and/or their OS to Linux distribution.
I will create one bona-fide playable game, even if it's Tic-Tac-Toe 2007.
I will recognize that not all programs are self documenting, and that this is why comments were invented.
I will contribute to an open-source project because they need my skills, not because I like the project.
I will explain my grep patterns in comments.
I will be nice to the people who pay me.
I will go back and do something interesting with all my failed, half-finished projects.
I will not use the term "Alpha" when what I really mean is buggy, untested, crap-tastic software.
I will always write Ajax that degrades gracefully (or I will realize that Ajax site navigation is the new "skip intro" of internet design).
I will not try to learn a new language. Instead I will surprise everyone by programming something completely unexpected in one I already know.
I will write ten lines of code everyday for someone I love.
I will stop writing apps that are just giant, nested loops and releasing them as popular software packages. (Here's looking at you, Wordpress theloop.php.)
I will learn how to write a script that emails me errors instead of sending everything to /dev/null.
I will finally pay for all of the shareware apps that I use daily. No, really.
[1] blog.wired.com/monkeybites/2007/01/new_years_resol.html
Compiled by Rob Beschizza, Mike Calore, Scott Gilbertson and Joel Johnson
I will realize that design patterns are a guide, not a religion.
I will bother to research the security issues relevant to my work.
I will spend an hour teaching a child the rudiments of programming, even if it's just "Hello World" in JavaScript.
I will learn how to use Unicode.
I will not respond to requests for help by informing the questioner that they are not only asking the wrong question, but should change the language they program in and/or their OS to Linux distribution.
I will create one bona-fide playable game, even if it's Tic-Tac-Toe 2007.
I will recognize that not all programs are self documenting, and that this is why comments were invented.
I will contribute to an open-source project because they need my skills, not because I like the project.
I will explain my grep patterns in comments.
I will be nice to the people who pay me.
I will go back and do something interesting with all my failed, half-finished projects.
I will not use the term "Alpha" when what I really mean is buggy, untested, crap-tastic software.
I will always write Ajax that degrades gracefully (or I will realize that Ajax site navigation is the new "skip intro" of internet design).
I will not try to learn a new language. Instead I will surprise everyone by programming something completely unexpected in one I already know.
I will write ten lines of code everyday for someone I love.
I will stop writing apps that are just giant, nested loops and releasing them as popular software packages. (Here's looking at you, Wordpress theloop.php.)
I will learn how to write a script that emails me errors instead of sending everything to /dev/null.
I will finally pay for all of the shareware apps that I use daily. No, really.
[1] blog.wired.com/monkeybites/2007/01/new_years_resol.html
Compiled by Rob Beschizza, Mike Calore, Scott Gilbertson and Joel Johnson
0 Responses to “New Year’s Resolutions for Java Coders”
Post a Comment