Socoder -> Off Topic -> The 10 Commandments (Stressfree programming) !
|Posted : Friday, 17 August 2007, 08:08|
Ten Commandments for Stress Free Programming
Thou shalt not worry about bugs.
Bugs in your software are actually special features.
Thou shalt not fix abort conditions.
Your user has a better chance of winning state lottery than getting the same abort again.
Thou shalt not handle errors.
Error handing was meant for error prone people, neither you or your users are error prone.
Thou shalt not restrict users.
Don't do any editing, let the user input anything, anywhere, anytime. That is being very user friendly.
Thou shalt not optimize.
Your users are very thankful to get the information, they don't worry about speed and efficiency.
Thou shalt not provide help.
If your users can not figure out themselves how to use your software than they are too dumb to deserve the benefits of your software anyway.
Thou shalt not document.
Documentation only comes in handy for making future modifications. You made the software perfect the first time, it will never need modifications.
Thou shalt not hurry.
Only the cute and the mighty should get the program by deadline.
Thou shalt not revise.
Your interpretation of specs was right, you know the users' requirements better than them.
Thou shalt not share.
If other programmers needed some of your code, they should have written it themselves.
Project Dollhouse on Github - Please fork!
|Posted : Friday, 17 August 2007, 09:42|
Seems reasonable to me, from now on I'll start following this
|Posted : Saturday, 18 August 2007, 12:52|
These are very stress-free... until your boss calls you in for a "short meeting".
|Posted : Saturday, 18 August 2007, 19:49|
or till you come back in a week and forget what you had wrote and then end up killing your OS
real stress free!!
i like green haired girls...
|Posted : Saturday, 18 August 2007, 23:27|
Evil Roy Ferguso
Commandments(11) = "Thou shalt perform bounds checking."
|Posted : Monday, 20 August 2007, 22:58|
I like these, especially when you consider that software only starts to get bugs when people start using it. Therefore they must be the fault of the consumer, not the developer.