Sometimes the rights steps to a refactoring are on a long and narrow path.
2010-10-27
Let's Code Dimdwarf #11: Reuse via Deduplication
We move towards a reusable utility class by eliminating the duplication between the existing classes for two different use cases.
2010-10-23
RECAP: Let's Code Dimdwarf #1-10
Recap of episodes 1 to 10, at 10 times the normal speed, with commentary. Watching this recap should make it easier to follow what is happening in the following episodes, even if you haven't had time to watch the previous episodes.
2010-10-18
Let's Code Dimdwarf #10: Add Synchronization
Now that ByteSink's synchronous tests are passing, it's time to implement the asynchronous behaviour. Unlike with EventSink, this time synchronization needs to be done manually.
2010-10-14
Let's Code Dimdwarf #9: Second Asynchronous Use Case
In order to get a reusable utility class for writing asynchronous tests, we re-implement it for another use case. After that it will be possible to extract the common parts into a reusable class.
2010-10-12
Let's Code Dimdwarf #8: Escape from Refactoring Hell
We finally figure out what was wrong in the code and manage to clean up the mess which had piled up during the last hour or so. The first draft of the asynchronous testing tool is now ready and in the following episodes we will be making it reusable.
2010-10-10
Let's Code Dimdwarf #7: Growing a Fluent API
Let's Code is back after a short pause due to the Software Craftsmanship 2010 conference earlier this week. In the concluding talk of the conference there was a fitting quote from The Mythical Man-Month, chapter 1: The Joys of the Craft
In this episode we refactor our test code by extracting a fluent API out of it, to make the test code more readable. There is some unnecessary work in re-inventing wheels, because of not being familiar with what features JUnit and Hamcrest already provide.
2010-10-05
Let's Code Dimdwarf #6: Tumbling with Exception Messages
We try to integrate with the Hamcrest library and make our utility class produce useful exception messages. I haven't written Hamcrest matchers before, so it's not clear that how to do it.
2010-10-02
Let's Code Dimdwarf #5: Asynchronous Testing Tools
In order to easier test our asynchronous system, we need some utility classes which take care of the concurrency issues. In this episode we begin writing them.
This episode can be a good "first episode" for someone evaluating his interest in this show, because here we are writing code which does not require being familiar with the system's architecture. If you like this episode, then you might want to later watch Let's Code Dimdwarf #1, where the current project and its architecture are explained, but where no code is yet written; the coding starts in episode #2.
Subscribe to:
Posts (Atom)