6 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
This article details the 18-month development journey of the project management application Fizzy, highlighting key commits and name changes along the way. It captures the iterative process of design and coding, including major contributions from David Heinemeier Hansson and the philosophical shifts in the codebase.
If you do, here's more
Fizzy, an open-source project from Basecamp, was officially released on December 2, 2025, with its entire development history available for public viewing. The project began on June 21, 2024, with the first commit made by Kevin McConnell, establishing a new Rails app. Over the next 18 months, the team made 8,152 commits, involving over 25 contributors and resulting in significant code changes. The naming process for the app went through multiple iterations, starting as "Splat," evolving to "Bubble," and ultimately landing on "Fizzy," reflecting its playful, effervescent design.
The development process included various phases, with notable contributions from Jason Zimdars, who introduced the core concept of "Splat" and then pivoted to the "bubble" metaphor. This shift happened just a week after the initial identity was set, demonstrating the fluid nature of the project. The team also wrestled with terminology, transitioning from "Projects" to "Buckets," then "Collections," and finally settling on "Boards" to align with existing tools like Trello. David Heinemeier Hansson, co-founder of Basecamp, became involved in October 2024, emphasizing performance improvements and a philosophy against "anemic" code, which he defined as thin wrappers that offer no substantial value.
DHH's influence is marked by his focus on clean, efficient coding without unnecessary complexity. His commitment messages repeatedly targeted "anemic" elements, pushing the team to refine their codebase. By April 2025, the project underwent a major refactoring, likely in line with his principles. The entire journey of Fizzy—from its inception to the architectural refinements—illustrates a responsive development process driven by team collaboration and a clear vision of the end product.
Questions about this article
No questions yet.