Comments on: DoubleDawg 3: Follow The Data http://anarchycreek.com/2009/08/26/doubledawg-3-follow-the-data/ Towards a Way of Excellence Sun, 05 Sep 2010 11:44:25 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: sam http://anarchycreek.com/2009/08/26/doubledawg-3-follow-the-data/comment-page-1/#comment-195 sam Thu, 27 Aug 2009 11:43:33 +0000 http://anarchycreek.com/?p=624#comment-195 Should you not have a test in place that ensures that the processAnnotations method does not return null? After all someone could refactor it to return null, and now the changes you made would break. With a test at least they would know that it was not supposed to return null... Should you not have a test in place that ensures that the processAnnotations method does not return null? After all someone could refactor it to return null, and now the changes you made would break. With a test at least they would know that it was not supposed to return null…

]]> By: Joakim Ohlrogge http://anarchycreek.com/2009/08/26/doubledawg-3-follow-the-data/comment-page-1/#comment-191 Joakim Ohlrogge Wed, 26 Aug 2009 21:20:32 +0000 http://anarchycreek.com/?p=624#comment-191 Useful advice! Isn't it annoying when null is returned rather than an empty array? "if(whathever == null)" is probably my least favorite code to find around. Especiall if whatever is a collection (or array). It would also feel safer with immutable collections I think but you can't have it all can you :) Keep it up and be careful with the hardware :) Useful advice!

Isn’t it annoying when null is returned rather than an empty array? “if(whathever == null)” is probably my least favorite code to find around. Especiall if whatever is a collection (or array).
It would also feel safer with immutable collections I think but you can’t have it all can you :)

Keep it up and be careful with the hardware :)

]]>