Clean as You Code
A New Day Dawns for
Code Quality and Code Security
Clean as You Code means focusing on New Code for maximum Code Quality impact with minimum investment.
Traditional approaches to Code Quality face challenges
that the Clean as You Code method erases.
Focus on New Code
to maintain project health
The SonarQube project homepage highlights the Code Quality and Code Security of your New Code (changed or added) so you can focus on what's important: making sure the code you write today is solid.
Developers own quality
in New Code
As a developer your priority is making sure the code you write today is clean and safe.
Challenge | Feedback comes late in the process
The right feedback, the right time, the right place.
From SonarLint to PR analysis to the New Code Period in the project homepage, SonarQube gives you the tools to stay on track.
SonarLint in your IDE is your first line of defense for keeping the code you write today clean and safe. Connect to your SonarQube instance to make sure you're applying the same rules that will be used during SonarQube analysis.
PR Analysis DE Available on Developer Edition EE Available on Enterprise Edition DCE Available on Data Center Edition
Use SonarQube pull request analysis and decoration to make sure your code is top-notch before you merge - and maybe even before you ask for human review.
Challenge | No one owns quality
Personal responsibility, not heroics
With the Clean as You Code methodology, no one is responsible for cleaning up someone else’s code. You only have to do an okay job on the code you’re writing today.
And if you do add new issues, they’ll be automatically assigned to you, so no one is asked to clean up after someone else.
Developers own quality in their own New Code.
Challenge | Different standards for different projects
Consistent standards across languages, projects… the entire organization
By focusing on the New Code Period you can apply the same high standards to every project, regardless of age, language, or outstanding technical debt.
Every developer owns quality in her new code.
Challenge | Pushback from teams
Quality Gate™
Enforcing a Quality Gate focused on New Code metrics makes sure new features are delivered cleanly. Then all you need to do is keep your Quality Gate green to make sure each release is better than the last.
Foster high standards with New Code focus
There's no downside to setting - and enforcing - high standards in your Quality Gate if you're only applying them on New Code. Developers take pride in meeting high standards on their New Code and if the project doesn't pass its Quality Gate it's obviously not ready to release.
Teams embrace meeting high standards on their New Code.
