The #{list.size) Maxims of Highly Effective Coders

  1. If it ain't broke, it hasn't been submitted to QA
  2. (alternate #1) If it ain't broke, it hasn't been deployed to production.
  3. (alternate #2) If it ain't broke, it lacks a unit test.
  4. "It worked in the testing environment" means it worked in the testing environment. Nothing more, nothing less.
  5. If it's stupid and it works, it's still stupid and you should refactor now.
  6. "We've tested enough to go live" = "We logged on and then surfed Facebook for an hour"
  7. A test plan doesn't guarantee it's right, but no test plan guarantees it's wrong.
  8. Your product is only as strong as your weakest user; and if your dev team is the only user well then...
  9. A 'quick fix' is not an acceptable substitute for a pull request.
  10. A bug report outranks a feature request.
  11. Ad copy covereth a multitude of sins.
  12. Weeks of programming can save you hours of planning
  13. Any sufficiently advanced technology is indistinguishable from an 11th-hour hack.
  14. There is no "overkill". There is only IllegalArgumentException or NullPointerException. Your choice, bub.
  15. Just because it's a one-liner in Perl/Ruby/Python doesn't mean it should be.
  16. Everybody has a testing environment. Some people are lucky to have a totally separate environment to run production in.  (Origin unknown, but so true...)
Comments