Speed up the TDD feedback loop with better assertion messages
There is a rather widespread TDD practice to have a single assertion per test. The goal is to have faster feedback loop while coding. When a test fails, it c...
Recent posts
20 Bad Excuses For Not Writing Unit Tests
I guess we always find excuses to keep on with our bad habits, don’t we? Stephen King
From apprentice to master, how to learn TDD (Test Driven Development)
I started to learn Test Driven Development a long time ago. Since then, even though I’m still not a master, it’s been my most useful programming skill, by fa...
Most Scrum teams are not agile
Being agile is about adapting to change and continuously improving. I’ve seen (and been) in too many teams blindly following Scrum (Scrum Zombies) without fi...
A Straightforward Way to Scale to More Than 1 Scrum Team
How come the “agile scaling” landscape seems so daunting and bloated ?
Incremental architecture, a cure against architecture astronauts
Back in 2001, when I started to code for a living, fresh out of school, I was mainly doing a form of cowboy coding. After a few months of maintaining my own ...
How to get your team to do code reviews
As software developers, we very always often get to work in code bases that are not perfect. In this situation we have 3 choices : leave, grumble, or make so...
A seamless way to keep track of technical debt in your source code
I eventually stumbled upon a way to keep track of technical debt in source code that is both straightforward and already built-in most tools : simple TODO co...