I have not much more to add, but FWIW the people espousing the "boring is better" and "don't reinvent the wheel" mantras were experienced SV devs, 15 and 30 yea

I have not much more to add, but FWIW the people espousing the "boring is better" and "don't reinvent the wheel" mantras were experienced SV devs, 15 and 30 years experience. They said there is a business justification and it's one of risk, namely that the more home-grown or nonstandard solutions you have, the less likely other people on the team will know what's going on when one of them breaks. There's also the maturity value of an existing codebase in that it has been proven to do the thing it sets out to, whereas a new endeavor may encounter roadblocks that require a rewrite partway through, and also lack documentation and good error messages, don't have the same years of bugfixes, etc.