public marks

PUBLIC MARKS from greut with tags code & test

November 2009

Pair Programming Ping Pong Pattern

  1. A writes a new test and sees that it fails.
  2. B implements the code needed to pass the test.
  3. B writes the next test.
  4. A implements it.

December 2008

Testing Will Challenge Your Conventions

1 comment (via)

Private makes less sense than it used to. You can’t test anything that’s private. You need to have ways to sense that your tests are working as intended, and you have to be able to test any method that is interesting. That means less private and more accessors. Get used to living in a more public world. If you need to hide something from users, don’t include it in the interface or abstract base class. “Implements”/”public inheritance” is the new “private”.

or documented is the new public

greut's TAGS related to tag code

agile +   algorithms +   amazon +   api +   as3 +   aws +   bad +   badge +   bdd +   blog +   bzr +   challenge +   company +   corelib +   couchdb +   css +   database +   django +   erl +   Erlang +   event +   exif +   extension +   facebook +   firefox +   framework +   gears +   geek +   generator +   geo +   gmail +   google +   greasemonkey +   hacks +   hg +   hiring +   html +   http +   iptc +   java +   javascript +   job +   jpeg +   JRuby +   js +   json +   l10n +   leak +   library +   localization +   MapReduce +   mobile +   mozilla +   msie +   netscape +   nokia +   opensource +   pair programming +   paper +   performance +   php +   pil +   presentation +   programmation +   programming +   py +   python +   rails +   review +   ruby +   scratch +   search +   server +   sha1 +   simpledb +   soft pairing +   software +   svn +   tdd +   team +   test +   theory +   tiff +   tips +   todo +   tool +   tools +   training +   troll +   use +   utils +   web +   web.py +   webhooks +   work +   wsgi +   wtf +   xbl +   xslt +   yahoo +