No tool can address software quality issues more effectively than fostering a culture of continuous improvement. AI-generated65 Aurora Innovation Improving software quality Culture Teams need to foster accountability for software quality. reward continuous improvements and actively share about technical debt. Commitment Teams need to commit to continued investment in maintaining software quality and continuously culture Maintaining software quality is a collective effort. Shift-left testing reduces development cost and improves ef�ciency. Effective communication about software quality helps improve it. Reward

highest quality C++ standard libraries” – Beman project mission 17 David Sankel Richard Powell© 2024 Adobe. All Rights Reserved. “ Support the efficient design and adoption of the highest quality C++ Powell© 2024 Adobe. All Rights Reserved. “ Support the efficient design and adoption of the highest quality C++ standard libraries through implementation experience, user feedback” – Beman project mission Powell© 2024 Adobe. All Rights Reserved. “ Support the efficient design and adoption of the highest quality C++ standard libraries through implementation experience, user feedback, and technical expertise

STATEMENT A] This material has been approved for public release and unlimited distribution. C API: Quality of Life Issues - For each predefined GraphBLAS operator, the C API requires a separate C function STATEMENT A] This material has been approved for public release and unlimited distribution. C API: Quality of Life Issues - For each predefined GraphBLAS operator, the C API requires a separate C function STATEMENT A] This material has been approved for public release and unlimited distribution. C API: Quality of Life Issues - For each predefined GraphBLAS operator, the C API requires a separate C function

intended Documented ReviewsReliability Efficiency Security Maintainability SizeHigh quality software is cheaper to produce! –Developer FrustrationFrustration Points Major % Managing libraries NULL pointers, part 1: https://lwn.net/Articles/342330/Why code analysis – ● Improve software quality ● Lower developer frustration ● Avoid UBLanguageLanguage helps! – ● Lifetime safety: http://wg21 Standard to everyone Depends on the toolToolingWhat do you use for guideline enforcement or other code quality/analysis? –Code Analysis: CI – https://www.sonarsource.com https://rules.sonarsource.com/cpp

improve code quality in your organization, I would say, take all your coding guidelines and replace them with the one goal. … No Raw Loops. This will make the biggest change in code quality within your improve code quality in your organization, I would say, take all your coding guidelines and replace them with the one goal. … No Raw Loops. This will make the biggest change in code quality within your

Quality Functional Non- functional InternalFunctional Correctness Completeness Accuracy Precision Test coverageNon-functional Regulations Mandatory standards adherence Efficient Optimal Up Leaking abstractionsQuality Functional Non- functional InternalIs this the only concern?Quality Ownership Knowledge Evolution Innovation TransformationWhat-If? Did you consider? Suggest Better n Resistance low with others Contagious Mindset Each others’ support Let’s try it out!Quality Ownership Knowledge Evolution Transformations InnovationDo try this at home!

• Serious design constraint • There are billions of lines of C++ • Much critical • Much high quality • Gradual adoption is essential • Partial adoption is essential (“safety critical code only”) • deliver better than average developers • Once the number of users of a language increases, their quality and enthusiasm converge towards the industry average Stroustrup - C++ safety -CppCon - October of system that’s critical in some way • A good developer completes N lines of tested production-quality code a day • What is N? 5?, 10?, 100? • Say – optimistically – 2,000 lines/year • Say – optimistically

Core Guidelines Checker docs.microsoft.com/en-us/cpp/code-quality/quick-start-code-analysis-for-c-cpp docs.microsoft.com/en-us/cpp/code-quality/code-analysis-for-cpp-corecheck devblogs.microsoft.com/ Victor Ciura | @ciura_victor - 2020: The Year of Sanitizers? docs.microsoft.com/en-us/cpp/code-quality/code-analysis-for-cpp-corecheck ...17 2020 Victor Ciura | @ciura_victor - 2020: The Year of

Non-linear/indirect interactions between components or systems ❖ Demand for complex systems outpaces quality standards ❖ Perhaps less restrictive than automative and avionic Think Safety Is Good Enough, Hooks Multi-platform Build Multi-compiler Build Test Build ASan TSan LSan UBSan MSan RTSan Quality Gate Code Review Merge Sanitizers Static analyzers/QG Use of AI tools Rich IDE ❖ No new

from 17 years of Cppcheck development Daniel MarjamäkiBefore I started Cppcheck ● Feeling that quality was not very good ● Our compilers would not find obvious bugs I was looking for off the shelf static