Automated quality gate — a rail guard to support the continuous quality

A first step to improve the code quality

In my career, I have been multiple times onboarded in the middle of a project. Ironically, every project starts as a “green field”. But somehow sooner or later, they end up poor or very poor of quality. Over time, it piles up more and more technical debt. The codebase becomes the one we would not like putting our fingers on. It also becomes more difficult to deliver business value to our customer. We would rather start a new revamp it from scratch, right? But no! No stakeholder would pay multiple times to build the same software. There are many reasons why we would end up with such heavy, yet accumulated over time, technical debt.

Quality Gate — Continuous quality checks

1. First, we work on quickies (quick wins), as we adopt a user centric approach to in software engineering, and that is just a natural way of doing things.
2. The design and delivery process is not yet industrialised, thus not having any standard, that also must be defined and spread globally across teams.
3. We do not having the right management and tooling to measure and control the quality.
4. Team’s standard is not putting the quality as top priority.
5. At last, coding (best) practices are more or less present to…