The thing about churn (of developers/contributors) rings <i>so true</i> to me from my career, and I think is really under-appreciated. In "the industry", or just among "people who make things in teams" (including open source).<p>> Constant churn in a software development team, both among the programmers and designers, is absolutely devastating. It is the death knell for a software project. Makes deadlines meaningless. It turns software into a disposable, single-use product like a paper towel. Anything that increases team member churn threatens the very viability of the project and the software it’s creating.<p>From an essay that is worth reading in full, "Theory-building and why employee churn is lethal to software companies": <a href="https://www.baldurbjarnason.com/2022/theory-building/" rel="nofollow">https://www.baldurbjarnason.com/2022/theory-building/</a><p>I think it's exactly right about the importance of "mental models" and "theory building", and if we could keep that in mind we could build better more maintainable software. ("More maintainable" over the long-term I think is almost synonymous with "has easy to grasp mental models that are sufficient to guide your work with the system")