10 Sep '13, 7am

Avoid the hidden cost of Null Objects with good unit tests:

georgebrock September 10, 2013 test-driven development patterns null object A Null Object is a drop in replacement for one of the other objects in your system that provides sensible defaults when the other object is unavailable. For example, I recently wrote about returning the path to a blank partial as a sensible default for to_partial_path . Null Objects remove respond_to? and nil? checks, and make code cleaner and easier to understand. It almost seems like there’s no downside. Almost. Too good to be true As with everything else in software development, there is a trade-off involved in introducing a Null Object: Whenever we change the public interface of the real object, we have to make a corresponding change in the Null Object that shadows it. If the interfaces diverge, then the Null Object ceases to be useful; instead of hiding complexity, it hides the potential for u...

Full article: http://robots.thoughtbot.com/post/60829368839/testing-nul...

Tweets

Array Objects Along a Path Curve in AutoCAD | C...

cadalyst.com 10 Sep '13, 3pm

If you're still using the Divide or Measure commands to array objects along a path curve, then you're working much too har...

@guipdutra and how this pattern can help you in...

robots.thoughtbot.com 12 Sep '13, 4pm

feature 'Manage todos' do scenario 'view only todos the user has created' do sign_in_as '[email protected]' create_todo_ti...

Just posted to

onestepback.org 14 Sep '13, 2pm

At the time of writing the original text (sometime in 2000), I was doing a lot of DbC and Eiffel programming and had just ...