- Thou shalt not worry about bugs.
- Thou shalt not fix abort conditions.
- Thou shalt not handle errors.
- Thou shalt not restrict users.
- Thou shalt not optimize.
- Thou shalt not provide help.
- Thou shalt not document.
- Thou shalt not hurry.
- Thou shalt not revise.
- Thou shalt not share.
Bugs in your software are actually special features.
Your user has a better chance of winning state lottery than getting the same abort again.
Error handing was meant for error prone people, neither you or your users are error prone.
Don't do any editing, let the user input anything, anywhere, anytime. That is being very user friendly.
Your users are very thankful to get the information, they don't worry about speed and efficiency.
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.
Documentation only comes in handy for making future modifications. You made the software perfect the first time, it will never need modifications.
Only the cute and the mighty should get the program by deadline.
Your interpretation of specs was right, you know the users' requirements better than them.
If other programmers needed some of your code, they should have written it themselves.
Posts
