Ask HN: What is the best code base you ever worked on?

Article summary

The article asks about the best code base people have worked on and what made it good. Commenters share their experiences and opinions on what makes a code base great, including code ownership, simplicity, and familiarity. Some mention that having complete control over a code base is a key factor, while others highlight the importance of standard practices and a well-organized structure. The discussion also touches on the role of advanced language features and the trade-offs between simplicity and complexity.

Main themes

• Code quality
• Code ownership
• Simplicity vs complexity
• Advanced language features
• Code maintainability
• Team dynamics

What commenters say

• Having complete control over a code base is essential for making it great.
• A simple and well-organized code base with standard practices is more important than using advanced language features.
• Advanced language features can make a code base worse if used unnecessarily, but can also be useful when applied judiciously.
• Code ownership and familiarity with the code base are crucial for making changes and reducing technical debt.
• Over-engineering and using complex patterns can lead to maintainability issues and make the code base harder to work with.
• The use of advanced language features should be balanced with the need for simplicity and readability.
• A good code base is one that is easy to understand and maintain, with a focus on simplicity and standard practices.
• The quality of a code base is influenced by the team's dynamics and the presence of experienced developers who can make informed decisions.