Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.
  • Never tell name or location of the file you couldn't open, or what access rights you're expecting
  • Make sure an error message does not mention a possible cause or solution
  • Ideally produce no error message at all
  • When installing or updating a file, do not tell name or location, "installed" or "updated" is enough info
  • Never check if called variables are actually set
  • Never validate input; you can always trust a user to pass the correct option, feel free to explode if user passes unexpected parameters.
  • Do not document
  • Make sure "progname -h" crashes or at least spits out an error
  • Having a design is against the law
  • If you output an error, make sure to use a text that will produce at least 1000000 google hits
  • Do not check preconditions, just lemming of the cliff and throw a useless error or dump a core
  • Never use or check return values, that makes it too easy to determine where something went wrong
  • Use bugzilla or broken mailinglist managers to effectively discourage users from reporting issues
  • There shall be only one error value, and that value shall be -1.
  • Magic numbers give your code amazing powers
  • Always blame the user, he should have known better
  • Never check for an error condition you don't know how to handle
  • Golden rules for software developers
    Reposted fromelpollodiablo elpollodiablo viafin fin

    Don't be the product, buy the product!