Chess TDD 56: Threatened Pieces
In this episode of the Chess TDD series, I start working on implementing check by implementing the more general concept of threatened pieces.
-
-
The Case for a Digital Notebook
I have a lot of different posting threads that I try to juggle simultaneously, but one that I’m thoroughly enjoying and should probably try to do more of is the reader submissions. A while back, I added a resources page (since removed) to the site and made brief mentioned of it. That prompted this reader question:…
-
Chess TDD 55: Got the Hang of Castling
In this episode, it seems I finally got the hang of castling. It’s been a relatively long journey with it, but I can now successfully detect castling situations that involve any combination of rook/king prior movement, as well as interceding pieces. The only thing left to go is the relative edge case of a castling…
-
Our Job Titles: Developer, Programmer or Software Engineer?
If I look at the desired length of blog posts across the sites of customers for whom I’d write, it’s around 1,000 words. Given the length of Monday’s wildly popular post, that means I’ve got about 500 words left for the week. So today’s will be relatively short and sweet, lest I deplete the world’s…
-
Chess TDD 54: Castling Acceptance Tests
The last few episodes featured heads down implementation around this new CastlingStatusChecker class. It was nice to spend some time writing relatively simple unit tests to restore some sanity and get away from an overly-coupled Board class. But, it was time to come up for some air and get back to proving some business/domain value….
