Code quality is often seen as the developer's responsibility, but the reality is that many roles influence the quality of code—starting with business decisions. In this talk, I will share a real-world example where simplifying redundant business rules, identified by a business analyst, led to cleaner, more maintainable code. We will dive into how collaboration between developers, business analysts, product managers, and other stakeholders can shape code quality from the ground up.

By understanding how business logic, requirements, and communication impact the codebase, teams can avoid unnecessary complexity and create software that is simpler to maintain and scale. Whether you are a developer, product manager, or analyst, you will leave with a new perspective on how your role plays a part in building high-quality software.

If you have ever thought code quality is solely a developer's problem, this talk will show you how it truly is a shared responsibility.

Recently I was approached by the business analyst of our team to some changes in a story I was doing a refinement for. He showed me that he had found some duplications that were unnecessary and also led to more actualisations inside the application, making the performance worse. Even though the performance is not an issue in this application, simplifying the business logic also led to simplified code. At the moment there are a lot of bugs in this particular part of the application and introducing the simplification that the business analyst proposed will lead to better code and most likely to less bugs in this part of the application.