One particular point of developer inequality and technical debt that I see get ignored is people with the social credit or track that lets them only create new things as opposed to those that have to do maintenance.

I find the latter often appreciate the place and purpose of types more clearly than the former, even if the former would benefit as well from having concise encodings of intent in the design and creation phase.

This bias is prevalent in dyn-lang/consulting-oriented communities, often because they are churning out projects and dumping them on their clients/employers.