News for hackers. Stuff that matters.

A comment on /story/34366610. Parent comment

Re: by CuriouslyC on Friday January 13, 2023 @01:11PM (#34371580)
The guy who will clean up your code base isn't a viable role because then the team that works on the code day to day will have to re-learn where everything is. It can work when a company is acquiring new code to refactor during integration, since the refactor catches bugs and makes engineers become familiar with it, but that would be done by people staying with the code base as well.

Probably the closest things to that are test writer, technical documenter and build engineer.

[ Parent | on HN ]
Re: by orblivion on Friday January 13, 2023 @01:19PM (#34371706)
Yeah I don't think being on a team of people doing regular cleanups would really work well. I'm thinking more like "Oh, yeah we've had that code hanging around for a while. We don't really want to touch it because it's kind of a mess and we forgot how it works, but we have to make changes now and again. If someone could clean it up we'd be a lot more efficient".

This would likely not even be a software company as such.

[ Parent | on HN ]