We’ve all been there: rushing to ship a feature, a colleague asks for a quick Merge Request review, and we rubber-stamp it with a light "Looks Good To Me." But temporary code has a habit of becoming permanent. Six months later, you're debugging a weekend incident caused by that exact piece of code. As engineers, our goal is to ship features fast without getting bogged down in rework. While standard tests and static analysis catch the easy bugs, the real threat to a codebase slips through during rushed, lightweight code reviews. Once a complex architectural code smell merges into production, it often stays there until it causes a late-night incident. How do you prevent this at scale when standard static analysis isn't smart enough? At Mambu, we went the extra mile when it comes to defining "code quality." Thus during the presentation, we will walk you through our three-pillar approach: 1. The Standards: Moving beyond basic linting to define deep, contextual technical requirements. 2. The Culture: Training and empowering engineers to prioritize maintainability over quick-and-dirty fixes. 3. The Tech: building and integrating an internal AI tool to automate complex code review checks. Whether you are an engineer tired of debugging legacy smells, or a manager trying to scale quality, you will leave with a practical framework to reinvent your code review process.

Session Speakers

Gytenis Mikulėnas

Mambu, Sr. Engineering Manager

Toni Noguera

Mambu, Sr. Software Engineer