Static analysis as an answer to raising code quality
summary
The talk explains how static code analysis can help detect and fix programming errors early to improve software quality and security. It discusses static analysis tools and their role in identifying bugs in high-load backend systems to raise overall product quality.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:48What is static analysis
- 1:51Errors in large projects
- 2:33Vulnerabilities and causes
- 4:18Static analysis goals
- 6:25Code error examples
- 13:22Why code training fails
- 17:20Regular analyzer use
- 21:15First analysis issues
- 22:19False positives and fixes
- 27:15Analyzer deployment method
- 28:23Cost savings on fixes
- 29:03Static analysis limits
- 29:33Q&A
- 31:01Code writing recommendations
- 33:29Analyzer speed
- 35:18Incremental analysis
- 37:04Languages and static analysis
- 38:57Multithreading and analysis
- 40:06Summary
related talks
53mStatic Analysis Tools: QA’s Best Friend
44mStatic analysis as an additional barrier against bugs
58mSecurity Static Analysis - Avoiding an Angry Mob of Engineers
47mHow Code Analyzers Find Bugs and Security Defects
25mTypes & static analysis are good in PHP
39mPractical Static Analysis for Continuous Application Security
01h 00mStatic Analysis and Program Safety in C++: Making it Real
43mEverything I learned about static analysis and program safety in C++
