p.volve makes refactoring easy with CodeSee.
How the massively popular fitness app refactors with ease.
This codebase has well over 80K lines of code—it’s a monolithic repository. I initially used CodeSee personally, just to understand what was happening in the code—to see the relationships across the codebase. I didn’t know the codebase, and there was no documentation. I had to make one massive change at first—a pull request. It was successful, and a huge relief. So, how am I supposed to pass off that massive refactor to someone? It’s unreasonable. So, what did I do? I held a 30-minute meeting with my team using CodeSee and a Review Map Tour to showcase the breadth of relationships we are working with in the codebase.
We completed a 13.5K line refactor; a huge shift. Because I used CodeSee, the CTO finally understood the complexity of what we are taking on. Maps make large refactors possible.
“I am able to visually see the changes in a pull request and begin to create a phased solution for staggering deployments. CodeSee now provides my primary method to identify differences in the code and where to make changes.”
Senior Software Engineer, p.volve