4 ms·
The larger a product gets, the risk and customer impact of regressions increases, so even "simple" changes require significant engineering and QA effort. There
by twblalock 7y ago
The larger a product gets, the risk and customer impact of regressions increases, so even "simple" changes require significant engineering and QA effort. There are also so many feature requests that prioritizing them is a full time job.
- degenerate 7y agoThat, and, as people move on - their code remains... so part of adding new features means sifting through the codebase to learn what everything does and be very careful not to add new bugs.
- idoh 7y agoI'd say customer impact, even without regressions. As an example of something that I'm currently working on: - there is a need to add a single link to a page - some percentage of the customers will not like this change (perhaps 5%), because it links to a non-whitelabeled area of the product - as a result, a list of customers that will be upset has to be assembled, and then each one reached out to, which a different department, that doesn't really care if the link is there or not, has to do I'd say that doing the above will take a month or so. All for a link.