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.

Devoxx

A conference talk analyzing why poor code quality is often a systemic and organizational problem rather than purely a developer's fault. Using a real-world courier tracking system as a case study, the speaker explores how unwanted code duplication, miscommunication between developers and stakeholders, knowledge silos, and lack of documentation all contribute to degraded code quality. Practical remedies discussed include using diagrams to bridge communication gaps, pair programming, byte-size architecture sessions, decision logs, and principles from Domain-Driven Design such as ubiquitous language and bounded contexts. The core conclusion is that code quality is a shared responsibility that begins in conversations long before any code is written.

Why Bad Code Quality Is Not (Only) Your Fault by Annelore Egger