Some conventional wisdom candidates for most importance piece of technical debt across software engineering: complexity, memory unsafety, excess authority, form

Some conventional wisdom candidates for most importance piece of technical debt across software engineering: complexity, memory unsafety, excess authority, formal methods underutilized Probably not a candidate for "most" but maybe worth mentioning: pgp There's also lots of non-technical debt; indeed not even any of the above are purely technical, at the least getting solutions adopted likely requires a lot more than just serious hacking. Surely there are existing projects, or at least communities, that have formed around taking on what participants thought/think of the most importance piece of technical debt, at least that they were/are equipped to take on; perhaps [non-]reproducible builds, shotgun parsers (langsec)?