We have learned that "clean" unit tests might not be as clean as we think. We have done our best to make our unit tests as clean as possible. Our tests are formatted properly, use domain-specific language, and avoid excessive mocking. Nevertheless, our unit tests are not clean because: When we make changes to the […] Read more

If our code has obvious faults, we are very motivated to improve it. However, at some point we decide that our code is "good enough" and move on. Typically this happens when we think that the benefits of improving our existing code are smaller than the required work. Of course, if we underestimate our return […] Read more

Yesterday I published the list of the most popular blog posts that I wrote in 2014. I also promised to choose my favorite blog posts and publish that list on my blog. This year I decided to select blog posts that helped me to learn something new. Here are my favorite blog posts that I […] Read more

The year 2014 is almost over, and this means that it is time to publish the most popular blog posts that I wrote during this year. I selected these blog posts by using Google Analytics. I selected all blog posts that were published during 2014 and picked the blog posts that had the most page […] Read more

When we write tests for our data access code, we use datasets for two different purposes: We initialize our database into a known state before our data access tests are run. We verify that the correct changes are found from the database. These seem like easy tasks. However, it is very easy to mess things […] Read more