Latest Posts Under: Quality

I hate it. You change something and you can’t tell if your change broke something in the system. If you’re lucky, you did not break anything. Or nobody noticed it. Next to that, on the same scale of luck, the potential bugs are found in the manual testing phase. But often there is no time to do all the regression testing by hand. It will take days and days, and the change you made looked so insignificant. It should go live. What could possibly go wrong?. Then it happens. You’re live, your changes work, but… Read Article →

Recently I have been experimenting with a Code Kata, and in this post I’d like to share my experiences with it. Code Kata? Code Kata’s have been around for a while, but it really came into my attention while reading Chapter 6 from the book The Clean Coder by Robert C Martin. This chapter makes an anology that at your work you’re a performer like a musician and outside work you (should be, like a musician) practicing. (Of course, you will learn while at work, but that is not the point). But what is a… Read Article →

Not too long ago, Martin Fowler pointed out a nice blog post by Jay Fields. Jay Fields refers to a nice talk he had about accidental complexity and essential complexity and how this has impact on your estimates. He found that not all developers consider the accidental complexity and therefor have lower estimates. I found this a very interesting thought. It got me thinking how I estimate and how far I’m off. I found that, especially with larger solutions, I’m most of the time under estimating. Even with more complex things, and adding some ‘unforseen… Read Article →

As I have promised in my previous post, I would post an example of small refactorings in order to greatly improve the readability and understandability of code. I own a little project called Dune II – The Maker, and I started writing it a little over 10 years ago. In those years I have learned a lot. I did not have much time in those days to apply my new knowledge to the project. You could say the software was rotting. In order to make it better I need to refactor a lot and I… Read Article →

More and more I am being intrigued by the power of a small code refactorings. The positive impact it has on the readability, the maintainability and understandability of your code is great. It keeps code clean(er) and since the changes you make are really small (I’ll demonstrate how small), the chance they will break things is small. Of course, with unit tests (you are writing them right?) making sure you did not break anything: a small refactoring is a low-risk high-benefit practice. In my experience, small refactorings are undervalued. In fact, I undervalued them much myself since… Read Article →

Scroll To Top