I've read Clean Code. I'm a believer. I think unit tests and clean code are very important disciplines for software development, and even moreso for C++.
But...
What do you do with a large, mature code base that was not made with unit tests and clean code?
And working with a team where those technical engineering practices do not have buy-in by the team?
Do you try to buck the trend, and incorporate them best you can? Or do you go with the flow (when in Rome do as the Romans do)?
I know what you mean, I've been there. I've done a conference talk and a series of blog posts about dealing with legacy code, e.g. bring it under test piece by piece, higher level first, lower level as needed.
Regarding the team that won't buy into good practices: I tried to change things, I suffered their unwillingness you change for some time, but inn the end I left.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've read Clean Code. I'm a believer. I think unit tests and clean code are very important disciplines for software development, and even moreso for C++.
But...
What do you do with a large, mature code base that was not made with unit tests and clean code?
And working with a team where those technical engineering practices do not have buy-in by the team?
Do you try to buck the trend, and incorporate them best you can? Or do you go with the flow (when in Rome do as the Romans do)?
I know what you mean, I've been there. I've done a conference talk and a series of blog posts about dealing with legacy code, e.g. bring it under test piece by piece, higher level first, lower level as needed.
Regarding the team that won't buy into good practices: I tried to change things, I suffered their unwillingness you change for some time, but inn the end I left.