software
Is there a name for the stage of maturity/complexity where making a change to fix an individual bug introduces an average of at least 1 other bug, so making progress requires careful review by a knowledgeable maintainer, and a thorough test suite that gets updated to verify the bugfixes (and therefore prevent the same bug from coming back)?
software
@recursive That sounds a bit too vague to me?
software
@madewokherd Yeah, I don't have anything more specific I can think of.
software
@madewokherd You say "mature" and I think that's a reasonable way to put it? Maybe "established"?
I also think "legacy" can sometimes apply but not always.
(I think for me in terms of considering the care required for changes, it's also about the number of people using the software too? Earlier/smaller projects can ignore more edge cases and breakage has less impact, and later/bigger projects have more requirements and use cases to juggle and preserve.)
software
@madewokherd a lot of technical debt?