Theory-building and why employee churn is lethal to software companies (baldurbjarnason.com)

Article summary

The article discusses the importance of programmer teams possessing a shared mental model or theory of a software project, and how employee churn can be lethal to software companies. It argues that software is not just code, but a living, evolving entity that requires continuous care and understanding. The article also touches on the concept of

Main themes

• software development
• employee churn
• tacit knowledge
• legacy code
• software maintenance
• project longevity

What commenters say

• Employee churn can lead to the death of a software project as new team members lack the mental model and understanding of the code.
• The concept of tacit knowledge is relevant to software development, as it highlights the importance of shared understanding and experience among team members.
• Some argue that minimizing churn is crucial for software development, while others believe that it is just one aspect of a larger commitment to maintaining a project.
• The decision to rewrite or update old software is often driven by business considerations, rather than purely technical ones.
• Old software can still be valuable and functional, even if it is written in outdated languages or technologies.
• The ability to understand and maintain old software is a valuable skill, but it may not be prioritized by businesses or developers.
• Software has a lifespan that can be measured in decades, and its longevity is often determined by its continued usefulness and support.
• The idea that software has a limited lifespan of 3-4 years is not supported by evidence, and many software systems remain in use for much longer.