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.
"Run to the hills, run for your lives"
-
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.
"Run to the hills, run for your lives"
-
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.
"Run to the hills, run for your lives"
Quote:
You’ve just inherited a legacy C++ codebase, now what?
Now... say thanks... it could have been VB6 :rolleyes: :laugh:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
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.
"Run to the hills, run for your lives"
Depends, does it generate income?
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
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.
"Run to the hills, run for your lives"
This was pretty much my career. With few exceptions, two things I always did out of necessity were: 1) Fix the build. I once started a new job where the build required running multiple batch files including using the Visual Studio command-line. I was told it was impossible to simplify it. In three weeks, I fixed the build to where there was one batch file with one line launching a VS build (because the entire thing could now be build in VS.) At another company, various projects in the solution had wildly different settings including some DLLs statically linking the CRT and others dynamically linking it. 2) Crank warnings to most strict with a short list of exceptions and additions. At one job, the VS project built with over 2000 warnings at level 3! To find new warnings the previous team would do a diff on the output. Three of us moved the project to level 4 with no warnings. (What's amazing is how many of the warnings were about critical errors.)