4 ms·
These stories are great, and totally resonate with me at the moment. I'm managing a team working on a 30 year old codebase. It is in technical debt, like many c
by shoobs 4y ago
These stories are great, and totally resonate with me at the moment. I'm managing a team working on a 30 year old codebase. It is in technical debt, like many codebases that old. That being said, the codebase is full of so much good stuff from hard learned lessons over 30 years, and that's where its value lies.
I'm convinced that the way forward is not to refactor or rewrite it, but to produce something new and different that draws on the 30 years of experience learned during the development of the original product. And, like Basecamp, run them side-by-side and allow users to chose what they want.
- kqr 4y ago> produce something new and different that draws on the 30 years of experience learned during the development of the original product. Are the original authors still there or do you have insanely good documentation?
- shoobs 4y agoMost of the key authors are still with the team, though some of the old crew will start retiring shortly.
- sohnakukkar 4y agoWhat is the domain and tech stack of this project?