Tuesday, 17 April 2018

Code review 7 - Code Reviewers Checklist

›
So you've just agreed to be a code reviewer for another developers work. What should I check is available before the review can go ahead...
Monday, 18 December 2017

Observations of software development

›
These are some observations of mine of various software development teams that I've been in or seen working over the past 18 or so years...
Thursday, 14 December 2017

Team Trotters

›
Let's explore some of the good qualities of and bad qualities of a well formed team, by debriefing a video of the team in action. The t...
Wednesday, 22 November 2017

A format for Release Planning

›
Summary Output: An estimated backlog. A likely release date for the plan. Overview: Start with creating understanding and clarifying the...
Friday, 10 November 2017

Testing definitions

›
There are lots of test terms bandied about. I find there is general inconsistency among software development practitioners in what each one ...
Saturday, 21 October 2017

What's released trumps what's documented

›
What is released and is working in the live system, is what counts. Not what's written down. A while back I had to do some Fault Slipp...

The benefits of Pair Programming

›
In this post I will outline some of the benefits I have witnessed of Pairing. Pairing is not limited to just programming and can be applied ...
Saturday, 23 September 2017

"I need my unit tests for code coverage..."

›
Fundamental point: Tests must only exist to test the product/component. All other types of "test" are waste. The following conve...
Thursday, 18 May 2017

Code review 6: Code Review Flow

›
In this post I outline the optimal flow for good code reviews. It is important to strictly follow the process to prevent dysfunctional cod...
1 comment:
Friday, 21 April 2017

Code Reviews 5: Good articles on code reviews

›
Let me start by saying "good" is subjective and it's based on my opinions of how code review must be done, if we are working t...