In this installment, I’m looking to start defining the concept of “blocking” on a chess board. So far, I’ve been defining piece moves in a vacuum — put a rook down in (1, 1) and the rook can go anywhere in column 1 or row 1. But, what about when there’s a pawn at (1,…
In a comment on my post about how to resign from your company, I was asked about advice for a situation where you don’t like your job, but they’re paying more than any other competitors in the industry. In other words, what to do when leaving the company would mean that you’d personally take a…
In the last bunch of installments of this series, I’ve implemented methods for pieces to determine where they can move on a board and/or done some refactoring. But I’ve ridden that train as far as I can, now having implemented all of the pieces, so it’s time to shake things up a bit. Another thing that…
This post started out as a response to a comment on this post, but it started to get rather long for that venue, so I’m making it its own post. The comment concerns my habit of pulling instantiation logic for the class under test into a common setup method executed by the test runner prior…
This is one last post of loose ends and looking at what I’ve done so far before I move on to new functionality. It wasn’t necessarily my finest hour as a programmer and TDD practitioner, but I’m including the good with the bad because nobody is always on when programming. Also, I wasn’t insanely on…
