IMO, a more pernicious form the tech debt starts with one system. A second person comes along and builds their own system/software b/c of some real or perceived

IMO, a more pernicious form the tech debt starts with one system. A second person comes along and builds their own system/software b/c of some real or perceived issue with existing software (for example someone thinks something is poorly designed or not the right(tm) technology, etc). This second system then forces integration, APIs, TCP connections between apps. No big deal, right? But the next person comes along and says "I don't like those systems - I want to put tech3 on my resume (a little resume oriented architecture, anyone?) and they build a 3rd system. Now it's really hard to develop features across those apps. One has to be an expert in all those techs. Integration becomes 80% of the work. Now ppl have to create new or buy software just to get anything done. And so it goes. There's a name for this, used a lot on this site.