Category Archives: guidelines

How does the DRY Principal relate to a heavily layered architecture?

Today I’ve been thinking about how the DRY Principal (Do not Repeat Yourself) applies to an SOA or heavily layered architecture. A colleague of mine pointed out that our architecture violates this principal quite a lot, we didn’t really get … Continue reading

Posted in development, guidelines, Uncategorized | Leave a comment

Branching build scripts for production branches

At work we recently switched to using Team Foundation Server with a ‘proper’ branch/merge strategy. We also have improved our build process so that although it’s still a partly manual process, a document leads you through the process, and the … Continue reading

Posted in build, guidelines, methodology | Leave a comment

Supporting plural and singular parameters

This problem relates to all APIs I would say, but I’ll give an example. You have a service layer, a business layer, and a data access layer. An operation on the service layer for getting instances of a class by … Continue reading

Posted in guidelines, web service | Leave a comment

Why do our code reviews take such a long time?

Kevin E. Schlabach has posted in response to my post on code reviewing. I almost decided to respond on my own blog, but thought it was more polite to comment there and just link to his post (and my reply) … Continue reading

Posted in agile, comments, guidelines | Leave a comment

Code review, before or after check-in?

Recently I’ve been thinking about our code review process, and how it could be improved. We’ve recently moved from a simple VSS based source control to a more feature rich TFS based approach. We now have the majority of feature … Continue reading

Posted in agile, development, guidelines, methodology, techniques | 5 Comments

Defensive coding, interfaces and code noise.

Today I’ve been trying to balance several factors in my code following a code review. The first 2 are defensive coding and code noise; some people suggest that wherever an object is used it should first be checked for null, … Continue reading

Posted in development, guidelines | 2 Comments