SonarSource: The Power of Clean Code
summary
Live demo shows Sonar tooling catching real C++ problems: lambdas copying vectors (performance), insecure OpenSSL ciphers (crypto risk), memset being optimized away for secrets (use memset_s), and unspecified argument evaluation order (UB). IDE linting offers SonarLint in IDE with quick fixes; CI/merge checks enforce a quality gate on new code only. Product claims 500+ rules for C++ and says about 20% of code changes per year means roughly 40–50% clean after five years if teams block new issues.
AI-written summary · about
chapters (18)
- 0:00About SonarSource
- 1:22The Power of Clean Code
- 4:00Major roadblocks
- 6:43No fun
- 7:13The problem
- 9:26The approach
- 11:20Propagation
- 13:40Performance
- 15:10Security
- 16:38Memory
- 19:50Solution
- 23:35What happens next
- 24:40Pull requests
- 25:25Issues
- 27:05Release
- 28:12Quality Profile
- 29:25Wrapup
- 32:45Integrations
related talks
52m“Tools from the C++ eco-system to save a leg”
44mClean as You Code Your Projects
42mThe top 5 JavaScript issues in all our codebases
56mC++ Code Smells
06mKeynote: Thrive with Clean Code
46mIn search of Clean Code with Sonar, 20,000 leagues under an ocean of code!
25mClean Code, is it really worth it?
47mAdventures with C++ Legacy Codebases: Tales of Incremental Improvement