3 ms·
After recently joining a new company this was one of my big contributions, I went through the whole codebase and removed legacy/unused code, or merged code that
by aurbano 6y ago
After recently joining a new company this was one of my big contributions, I went through the whole codebase and removed legacy/unused code, or merged code that was slightly different into a more general version.
Spent a good 2 weeks on this but the result was around 120 files changed and over 4000 lines removed, it felt great! And it was also an amazing opportunity to understand the codebase and ask the right questions to other team members when figuring out what was outdated and what wasn't.
- secondcoming 6y agoDear god. I hope you were asked to do this?
- softawre 6y agoAhahhahh.. Yes, I hope so too.
- jacobush 6y agoI'm sure it was great, but always beware to change two similar codes into a more generic one, when what was originally two served two different parts of the system. In that case, what can happen is once the requirements change for one part of the system, now you must change a generic component in such a way as to not disturb the other part using the same component. That way madness lie. (Of course, cut-n-paste programming is also madness inducing.)