We held our sprint retrospective last Friday. One of the positive items that appeared was the newly introduced AAA style unit tests (Arrange-Act-Assert). I noticed that Jan Van Ryswyck just posted about this style of tests. This is kind of an extension to his post. What we're doing is very similar. There really is added value to this AAA style: Tests tend to become more readable. Test boundaries are explicit. You only test what is under test. You actually design the system first. When the test is ......
Bart Deleye pointed me to this nice site called Shelfari. This site allows you to share the books you've read, the books you liked, ratings, reviews, ... I know this has been done before. I just liked the application's smoothness. Visit shelfari and tell me if you liked it. My bookshelf can be found here: http://www.shelfari.com/o15... I also have this bookshelf widget on the side of my blog ......
I find it important to have a common development environment in our team. This allows us to easily switch seats during the sprints. ReSharper has a lot of customizable features, and we just figured out how to share these. Code conventions If your team agrees to name all local variables with a prefix of "local" (which I wouldn't advise, but hey, the team decides), you can set that in Re#. This will not enforce anything, it will just provide you with default choices. The result will look like this: ......
I preordered a book from the Pragmatic Programmers on a whim. Back then it was called "Refactor your Wetware". I regularly got PDF updates through my email. Now it finally came out, and I'm reading it with much pleasure. Although it talks about the development process, this is a not a technical book. You are used to working with software and hardware, but what about your wetware - your own brain? In this book you'll learn how to: Use the Dreyfus Model of Skill Acquisition to become more expert Leverage ......
Part 1: The problem I have a need for a regular coffee break when I'm working. Most people from our team share that need. I'll describe a typical situation. I'm doing my day job, pair programming a component that will probably save the world. After a while, a feeling of drowsiness starts dulling my senses. Time for a cup of coffee. I look up to the table where the coffee thermos is supposed to be. No coffee! Someone must have made coffee. But who? When? Should I go and get the coffee now, or is it ......