Skip to content
zeljkofilipin edited this page Mar 23, 2012 · 2 revisions
  • one thing in a commit...
  • the method name describes what the method does...
  • write unit tests (tdd?)...
  • use your brain (learn how to think/debug)...
  • never trust the test you did not see fail...
  • code, refactor, rinse, repeat...
  • make sure you can debug on your machine...
  • make sure the code actually works...
  • take a look at the code you are about to commit...
  • when reporting a problem or asking a question, read it and make sure that people not able to read your mind could understand what the problem is...
  • run unit tests before you commit...
  • fix unit tests if you break them...
  • have fun while you test (if testing is boring, you are doing it wrong)...
  • do not commit commented code (I do not mean code comments, use version control to keep track of deleted code that could be useful one day)...
  • report bugs so they could be reproduced easily...
  • write commit message when editing wiki pages...
  • do not commit IDE files...

#... or I will kick your ass! :)

Clone this wiki locally