Reading List

Tuesday, April 30, 2013

Skill Assessment and Acquisition


Assessing your current skill level is very important so that you know what the starting point of your development is. The next step is to figure out what you need to study to strengthen your skills. 

Andy Hunt discusses skill assessment and skill acquisition in Pragmatic Thinking and Learning using the Dreyfus model of skill acquisition. In the Dreyfus model, skills are categorized as novice, advanced beginner, competent, proficient, or expert. Novices need rules where experts can rely on intuition. For example, a chef understands what a pinch of salt and season to taste means where a novice would need a recipe that calls for a teaspoon of salt. Experts also understand why the rules exist and in what situations they can be altered or broken. People who are proficient use maxims such as too many cooks spoil the broth.

Take some time to assess each of your skills and then look for rules, maxims, or perfect your intuition. If the cooking metaphors were too much, read Pragmatic Thinking and Learning or The Seven Stages of Expertise in Software Engineering.

Wednesday, March 20, 2013

Unit Testing on a tight Project Schedule

In our projects, we are always pressed for time to deliver. Usually, this pushes writing unit tests to be a lower priority. In their book, Pragmatic Unit Testing In C# with NUnit, Andrew Hunt and David Thomas give general principles on what to test. One principle is to test anything that could break. Prioritizing what gets unit tested is important when time is limited. Methods that can break, are complex, and important to the project should be picked as candidates to have unit tests. Another principal that can fit into a project with a tight deadline is to write unit tests for anything that does break. If unit testing is not part of the project plan, then testing anything that breaks could be a way to increase code coverage. This way of writing unit tests is not optimal as the rules for how the method should work has to be reviewed again. Additionally, the risk for completely skipping unit testing during bug fixes is high so this will take discipline from the project team to follow through. This, in turn, opens up the opportunity to prove to the client that unit tests are worth including in the project plan. Leave a comment if you have a tip on writing unit tests for a project with a tight deadline or introducing unit test to an existing project?