Posts Tagged "dead code"
As I said in my previous article, Software maintainability. The ‘Poor Cousin’ in the Technical Quality Family, code is usually not designed for change. Right.
Now, what can you do so your software maintainability is not the ‘poor cousin’ of technical quality anymore?Read More
Code is usually not designed for change. Thus, while code meets its operational specification, for maintenance purposes it is poorly designed and documented. Symptoms are well known: understanding code that needs to be changed is hard, testing is too difficult and takes excessive time and resources, too many regression defects after simple functional changes or refactoring (it is difficult to reliably implement changes). You suffer from this, wouldn’t you?Read More
I still recall when my dad woke me those Sunday mornings in early spring and said: gear up, we are working in the garden today! That was far from what a teenager had in mind for a Sunday morning. Yeah, it was sunny and I got to spend some time with my dad chatting away, but it was still cold and it was hard work. It wasn’t a big garden: a bunch of grown trees, a small orchard with tomato plants, bushes around the fence, flower mounds and lawn.Read More