Sessionize
Aviva Solutions
Fluent AssertionsRecent Posts
An opinionated definition of a unit test
During the same C# code reviews that triggered last week’s blog post about writing great unit tests, another discussion tends to pop-up, in particularly with new joiners (both experienced and junior):
12 tips to write unit tests that don’t cripple your codebase
Over the last months, I’ve been involved in more and more code reviews, mostly because we’ve increased the level of quality required for code changes to our code base. While doing that, I started to track my most frequently used review comments intended to improve.
9 simple practices for writing better object-oriented code
Consider a fantasy game that must track a collection of items, each having a certain amount of quality (or value) that increases or decreases after time passes. This collection contains the following six items:
The real challenges of building the right thing right
Suppose you're in the following situation.You and your team are supposed to start working on some important architectural changes that were long due.Your team is then asked by your manager to help build an important feature that requires the unique skills of your team, and ...
My thoughts on documenting your code
A recurring topic in every project I’ve been involved with is when and where you should use XML comments and/or annotate classes and members with proper documentation. I’ve always been very specific about this, but in real live I meet a lot of developers who don’t seem to care about this, or wors...
How architecture and the constraints that apply to it cannot be seen as separate things
In a previous project, I observed a typical communication mismatch. One team was demonstrating the technical details of architecture that, on first glance, was supposed to be a replacement for an existing architecture. The team demonstrated all kinds of technical solutions and showed us how much ...