In the last weeks I have written about the contents of my “Large C++ Legacy Applications” talk: I’ve written about how dealing with those applications is a team game, about the […]
In the last two weeks I have already written about legacy applications, about how it has to be a team effort and how to plan the refactoring. This week’s post […]
This is part 2 of my small series about cleaning up large code bases. After we get our team together and all are determined to clean up that mess, where […]
I have done another refactoring session in my last two blog posts. I have covered refactoring in other blog posts, but there is a thing that is really important about […]
Today I’ll pick up where I left last week with the refactoring with @vaughncato‘s inverse matrix multiplication function.
A while ago, Twitter user @vaughncato sent me the piece of code for this refactoring session. Since there is a lot of things to do on this code, I split […]
In my last post I showed the Visitor design pattern in its fully object oriented implementation. In the post before that I wrote about moving from enums to class hierarchies. I […]
When an enum controls the behavior of a class, that behavior can sometimes be expressed by class hierarchies.
Sometimes, a fixed set of string values is allowed as input. Often these string values are then stored, used for control flow etc. Enumerators are a better alternative.
I’ll try something new today: I pick a piece of code from the web and see what improvements I would make to it, using small refactoring steps.