Overview
The article discusses the creation and purpose of the #dead-code-society Slack channel at Pinterest, which serves as a space for engineers to commemorate code that has been removed. It highlights the importance of managing codebase growth and the cultural shift towards celebrating the retirement of code.
What You'll Learn
1
How to celebrate the retirement of code in a software project
2
Why managing codebase growth is essential for software teams
3
When to consider removing dead code from a project
Key Questions Answered
What is the purpose of the #dead-code-society Slack channel?
The #dead-code-society Slack channel was created to provide a space for engineers to remember code that has been removed, specifically focusing on diffs that contain only deletions. It serves as a cultural tool to celebrate the retirement of code while managing the growth of the codebase.
How does Pinterest manage the growth of its codebase?
Pinterest manages its growing codebase by encouraging the retirement of unused code through the #dead-code-society channel. This initiative helps maintain a cleaner workspace and build systems, allowing engineers to focus on active code while still retaining historical context in source control.
Key Statistics & Figures
Average messages per day in #dead-code-society
a little over one
This statistic reflects the ongoing engagement of engineers in discussing code removal, particularly during refactoring projects.
Changes produced weekly by software engineers at Pinterest
thousands
This highlights the scale at which Pinterest operates and the need for effective code management strategies.
Key Actionable Insights
1Establish a dedicated channel for discussing and documenting dead code within your team.Creating a space for engineers to share and reflect on removed code can foster a culture of cleanliness and efficiency, helping teams to manage their codebases more effectively.
2Regularly review and refactor your codebase to identify and retire unused code.This practice not only reduces clutter but also improves overall code quality and maintainability, allowing engineers to focus on active development.
3Encourage team members to share their experiences with removing dead code.Sharing stories and lessons learned can help build a collective understanding of the importance of code maintenance and inspire others to participate in similar initiatives.
Common Pitfalls
1
Neglecting to remove dead code can lead to increased complexity in the codebase.
As more code accumulates, it becomes harder for engineers to navigate and maintain the project, which can slow down development and introduce bugs.