You’ve just
inherited a legacy C++ codebase, now what?
You were minding your own business, and out of nowhere something fell
on your lap. Maybe you started a new job, or perhaps changed teams, or
someone experienced just left.
And now you are responsible for a C++ codebase. It’s big, complex,
idiosyncratic; you stare too long at it and it breaks in various
interesting ways. In a word, legacy.
But somehow bugs still need to be fixed, the odd feature to be added.
In short, you can’t just ignore it or better yet nuke it out of
existence. It matters. At...
Read more at gaultier.github.io