Oftentimes, we as software engineers can get "bogged down" working on complicated legacy code. As a result, it may be hard to improve our system when it comes time to write new features that add value to the business. When is the right time to dedicate resources to a refactor? How do you solidify a system that may be difficult for your engineers to understand?
In this session, we explore Capsule's use case for refactoring by taking a closer look at managing rejected claims. We will evaluate reasons for performing a refactor by way of Test-Driven Development. Most importantly, we will highlight the value-add from coupling our code with key business outcomes in order to increase comprehension of the story our code tells us.