The Code Cleanup Revolution: How a Hackathon Cleared 4,195 Files in Just 9 Hours
September 1, 2024, 6:10 am
Location: United States, California, San Francisco
Employees: 201-500
Founded date: 2012
Total raised: $329M
In the fast-paced world of software development, clutter can be a silent killer. Legacy code, unused files, and outdated dependencies accumulate like dust in a forgotten attic. The challenge? How to tackle this digital mess without losing momentum. Enter the hackathon—a creative solution that transformed a mundane task into a competitive and engaging event.
Two months ago, inspired by a blog post about organizing a hackathon focused on generative AI, I decided to take a different route. Instead of another tech-focused event, I proposed a company-wide initiative to clean up our codebase. The idea was simple yet powerful: a competition to remove as much unused code as possible in a single day. We dubbed it "Cleanathon."
The goals were clear. We wanted to create an engaging event for the entire company, tidy up our work environment, and, most importantly, do no harm to our product. The stakes were high, but so were the potential rewards.
We assembled nine teams, each comprising three to four members from various departments: developers, AI specialists, support staff, testers, product designers, finance, and DevOps. The diversity of teams added a layer of excitement and competition. The objective? To eliminate as much unnecessary code as possible.
The results were staggering. In just nine hours, we removed 4,195 files and 4,747 lines of code. We closed 120 open pull requests and eliminated 2,851 unused branches. The financial impact was equally impressive, saving the company thousands in monthly expenses.
But how did we achieve this? The key was organization and enthusiasm. We established a clear set of rules to ensure stability and fairness. Each pull request required approval from two knowledgeable team members. Special branches were created for the event, and thorough testing was mandated before any changes were merged.
To keep spirits high, we infused the event with fun. Each team received unique names and logos, and we displayed their achievements prominently. This not only fostered a sense of camaraderie but also encouraged friendly competition.
However, organizing such an event isn’t without its challenges. The most significant hurdle was creating a fair scoring system. With multiple teams from different departments, comparing results was complex. We opted for a point-based system, where each action had a maximum score. This approach kept the competition intense and engaging.
As the day progressed, the atmosphere buzzed with energy. Teams raced against the clock, motivated by the prospect of victory. The final scores reflected the hard work and dedication of each group, with the top three teams earning 26,000, 23,000, and 17,000 points, respectively.
The aftermath of the Cleanathon was transformative. Not only did we declutter our codebase, but we also fostered a culture of collaboration and innovation. Regular cleanups became a part of our routine, ensuring that we wouldn’t fall back into the trap of neglecting our codebase.
Reflecting on the event, it’s clear that hackathons can serve as powerful tools for improvement. They can turn tedious tasks into exciting challenges, driving engagement and productivity. The Cleanathon was more than just a cleanup; it was a lesson in teamwork, creativity, and the importance of maintaining a healthy codebase.
In the end, the Cleanathon proved that even the most mundane tasks can be transformed into opportunities for growth and innovation. By harnessing the power of competition and collaboration, we not only cleaned up our code but also strengthened our team dynamics.
As we move forward, let this be a reminder: a clean codebase is a happy codebase. And with the right approach, even the most daunting tasks can become a source of inspiration and motivation. So, gather your team, roll up your sleeves, and get ready to tackle that digital clutter. The rewards are worth the effort.
Two months ago, inspired by a blog post about organizing a hackathon focused on generative AI, I decided to take a different route. Instead of another tech-focused event, I proposed a company-wide initiative to clean up our codebase. The idea was simple yet powerful: a competition to remove as much unused code as possible in a single day. We dubbed it "Cleanathon."
The goals were clear. We wanted to create an engaging event for the entire company, tidy up our work environment, and, most importantly, do no harm to our product. The stakes were high, but so were the potential rewards.
We assembled nine teams, each comprising three to four members from various departments: developers, AI specialists, support staff, testers, product designers, finance, and DevOps. The diversity of teams added a layer of excitement and competition. The objective? To eliminate as much unnecessary code as possible.
The results were staggering. In just nine hours, we removed 4,195 files and 4,747 lines of code. We closed 120 open pull requests and eliminated 2,851 unused branches. The financial impact was equally impressive, saving the company thousands in monthly expenses.
But how did we achieve this? The key was organization and enthusiasm. We established a clear set of rules to ensure stability and fairness. Each pull request required approval from two knowledgeable team members. Special branches were created for the event, and thorough testing was mandated before any changes were merged.
To keep spirits high, we infused the event with fun. Each team received unique names and logos, and we displayed their achievements prominently. This not only fostered a sense of camaraderie but also encouraged friendly competition.
However, organizing such an event isn’t without its challenges. The most significant hurdle was creating a fair scoring system. With multiple teams from different departments, comparing results was complex. We opted for a point-based system, where each action had a maximum score. This approach kept the competition intense and engaging.
As the day progressed, the atmosphere buzzed with energy. Teams raced against the clock, motivated by the prospect of victory. The final scores reflected the hard work and dedication of each group, with the top three teams earning 26,000, 23,000, and 17,000 points, respectively.
The aftermath of the Cleanathon was transformative. Not only did we declutter our codebase, but we also fostered a culture of collaboration and innovation. Regular cleanups became a part of our routine, ensuring that we wouldn’t fall back into the trap of neglecting our codebase.
Reflecting on the event, it’s clear that hackathons can serve as powerful tools for improvement. They can turn tedious tasks into exciting challenges, driving engagement and productivity. The Cleanathon was more than just a cleanup; it was a lesson in teamwork, creativity, and the importance of maintaining a healthy codebase.
In the end, the Cleanathon proved that even the most mundane tasks can be transformed into opportunities for growth and innovation. By harnessing the power of competition and collaboration, we not only cleaned up our code but also strengthened our team dynamics.
As we move forward, let this be a reminder: a clean codebase is a happy codebase. And with the right approach, even the most daunting tasks can become a source of inspiration and motivation. So, gather your team, roll up your sleeves, and get ready to tackle that digital clutter. The rewards are worth the effort.