3 ms·
> the article also implies there's a lot of "here be dragons" code Agreed, fine if enough of the core developers are around, but if the company merged, the app
by helsinkiandrew 6y ago
> the article also implies there's a lot of "here be dragons" code
Agreed, fine if enough of the core developers are around, but if the company merged, the app needed to be extended or altered significantly, or some of the underlying technology stack is deprecated/becomes unsupported keeping things working will be very expensive.
- ed_elliott_asc 6y agoI think that they are in the situation where it can't be altered significantly which ironically is probably a good thing for stack overflow - they don't have reams of features.
- kthejoker2 6y agoReminds me of "tech debt as a lack of understanding" https://daverupert.com/2020/11/technical-debt-as-a-lack-of-understanding/ https://daverupert.com/2020/11/technical-debt-as-a-lack-of-u... > If there’s been enough organizational turnover or enough feature creep in a product, then maybe doing a rewrite is the best option so your team has a collective understanding of the code. You can’t expect people to be productive in something that was a culmination of [complicated "here be dragons" code] made by people who no longer work there. At that point your technical debt balloon has popped, you are in possession of a toxic asset.