2011-08-31
2011-08-30
2011-08-29
2011-08-28
2011-08-25
2011-08-24
2011-08-22
Let's Code Jumi #51: Actorified Runners (Part 1)
Converting the application to be actor-based. The TestRunCoordinator
class which remains from the walking skeleton (written in episode 33) needs to be replaced with actor-based suite and test class runners.
2011-08-21
Let's Code Dimdwarf #64: Asynchronous State Machine
When a collaborator can work both synchronously and asynchronously, it complicates things as the caller needs to make less assumptions. In our unit tests the authenticator is a synchronous fake (it keeps the tests simpler), but the production authenticator is asynchronous (because it does blocking operations). The state machine needs to be updated to work with both synchronous and asynchronous collaborators.
2011-08-20
2011-08-18
2011-08-17
2011-08-16
2011-08-15
Let's Code Jumi #46: Multi-Interface Actors (Part 1)
After starting to write the new actors, there comes the need for actors with multiple interfaces - or multiple actors in the same thread, however you want to think about it.
2011-08-14
Let's Code Dimdwarf #63: You Will Be Assimilated
The ClientSessions class will absorb most of the logic from NetworkController, leaving the controller just wiring things together and delegating all work to others. Let's first move the authentication logic.
2011-08-12
2011-08-11
2011-08-10
2011-08-08
2011-08-07
Let's Code Jumi #41: Dynamic Events (Part 1)
I had a short up-front design session to figure out what actors the system will need. Many new interfaces will be needed for actor-to-actor communication and the current way of writing the event classes by hand will not scale. I will at first write a reflection-based solution for producing those events, because I can do that faster than it would take to figure out how to do compile-time code generation.
2011-08-06
Let's Code Dimdwarf #62: Refactoring Domino
It's curious how sometimes with TDD the refactoring steps follow each other almost automatically, like dominoes. You make one small change and then just keep on fixing test failures until it all works again and the refactoring is done.