Author Archives: Chris VanHoose

About Chris VanHoose

Principal Software Architect at CT Lien Solutions

Coding Dojo – Week 4

Posted on November 6, 2013 by Chris VanHoose

For our 4th coding dojo, we spent our time demonstrating various implementations of the Observer pattern as applied to the Tennis Kata problem.  Susheel implemented a version where the players were subjects and the scoreboard was the observer.  We had … Continue reading →

Posted in Software Architecture | Tagged , | Leave a comment

Coding Dojo – Week 3

Posted on October 30, 2013 by Chris VanHoose

For our 3rd coding dojo, we implemented the Tennis Kata from scratch.  Before doing the kata, I got a chance to show off a JavaScript implementation using dependency injection (okay, so I cheated and I used TypeScript).  For the record, … Continue reading →

Posted in Software Architecture | Tagged , | Leave a comment

Coding Dojo – Week 2

Posted on October 23, 2013 by Chris VanHoose

For our 2nd coding dojo, we worked through the JavaScript version of the Tennis Refactoring Kata 2.  For fun, we used the Icenium development environment and platform, and we were able to deploy the solution at the end of 1.5 … Continue reading →

Posted in Software Architecture | Tagged , | Leave a comment

Coding Dojo – Week 1

Posted on October 16, 2013 by Chris VanHoose

We held our first coding dojo this week and worked through the C# version of the Tennis Refactoring Kata.  We followed the Randori method and the agenda scripted out by Emily Bache in her book, The Coding Dojo Handbook, and it worked really … Continue reading →

Posted in Software Architecture | Tagged , | Leave a comment

Code Review: Should the results of a code review count against you?

Posted on June 5, 2013 by Chris VanHoose

Code Review: Should the results of a code review count against you? No. Quote: “Code reviews often start off on the wrong foot because they are perceived as an unnecessary step that has been forced upon the developers or, in … Continue reading →

Posted in Software Architecture | Tagged , | Leave a comment

Code Review: How do I prep for a code review?

Posted on May 31, 2013 by Chris VanHoose

Code Review: How do I prep for a peer code review? You should create a self-checklist with common mistakes that you have made in the past and use this to help remind you of things to look for in your … Continue reading →

Posted in Software Architecture | Tagged , | Leave a comment

Code Review: What do you review in a peer code review?

Posted on May 30, 2013 by Chris VanHoose

Code Review: What do you review in a peer code review? All changes made should be reviewed in a code review; however, it is normal to focus in on key areas. It is okay for the author to give some … Continue reading →

Posted in Software Architecture | Tagged , | Leave a comment

Code Review: How long is a peer code review?

Posted on May 29, 2013 by Chris VanHoose

Code Review: How long is a peer code review? The code review process has been researched and studied since 1976, and it has be established and re-established that the maximum product code inspection rate is 200 lines of code per … Continue reading →

Posted in Software Architecture | Tagged , | Leave a comment

Code Review: When do you do a peer code review?

Posted on May 24, 2013 by Chris VanHoose

Code Review: When do you do a peer code review? A peer code review can be done prior to check-in or after check-in. Quote: “I find most people come down strongly on one side or another; and since we make … Continue reading →

Posted in Software Architecture | Tagged , | Leave a comment

Code Review: Does the reviewee have to be present at a peer code review?

Posted on May 23, 2013 by Chris VanHoose

Code Review: Does the reviewee have to be present at a peer code review? A peer code review can be done shoulder to shoulder or pass around via e-mail/TFS. Over the shoulder reviews do require the reviewee to be present … Continue reading →

Posted in Software Architecture | Tagged , | Leave a comment