Culture Teams need to foster ownership and accountability for software quality. reward continuous improvements and actively share about technical debt. Commitment Teams need to commit to continued investment Effective communication about software quality helps improve it. Reward and promote continuous improvements. Continuously measure developer experience and productivity.67 Aurora Innovation Proving business assumptions about individual test inputs. Extensible Good tests are easy to change. Optimize for low maintenance cost. Single use-case test frameworks have the same cost as production code. Measure test coverage

continuously. Steve Barr steve.barr@csgi.com @srbarr1 Overall Quality improvements, “it” goes in better, and with less issues.  Maintenance window changed from once a week to everyday  Expanded Sphere of Advice  Do embark on a agile self-improvement effort.  Do mix in or schedule your recurring maintenance.  Do define a primary purpose and measure it.  Do process map.  Do focus on Quality first

our metrics 1. All production deployments should be visible on graphs 2. Similarly useful are maintenance, backups, and other activities. 3. Ch. 15 – Analyze Telemetry to Better Anticipate Problems and A/B testing helps reduce zero or negative value add features to the baseline that also increase maintenance costs and identify opportunity costs. d. INTEGRATE A/B TESTING INTO OUR RELEASE i. A/B testing approval ii. Peer review help improve overall quality, provide cross-training, learning, and skill improvements. iii. Keep batch sizes of reviews small iv. 4 simple Peer Review Guidelines 1. Everyone must

Diversion of resources from C++ to other languages • Discouraging people from learning C++ • Massive improvements are possible in many areas • C++ has a massive image problem (“C/C++”) • And it is getting worse type-and-resource safe C++ • And more, e.g., safe arithmetic • Paths to gradual adoption • Major improvements can be achieved today, e.g., consistent range checking) • This is not just about safety • better US • So, the cost would be 550*5*$500,000 == ~$1,400,000,000 • Vs. ~$125,000,000 for normal maintenance and development • Roughly $1B added cost Stroustrup - C++ safety -CppCon - October 2023 58 For

semi-borderless capital…all driving massive change. Sport provides a good analogy for AI’s constant improvements. As athletes continue to wow us and break records, their talent is increasingly enhanced by better Breakthroughs in large models, cost-per-token declines, open-source proliferation and chip performance improvements are making new tech advances increasingly more powerful, accessible, and economically viable algorithms, based on how much computing power you'd need to reach top performance without any improvements. Source: Epoch AI (3/24) Impact of Improved Algorithms on AI Model Performance – 2014-2023, per

2. Code Safety 3. Cross-platform development 4. Developer and Team ProductivityBuild Time Improvements • 16.6 • Optimized symbol lookup. • ~2X better time to enter break state while debugging. local box Easy onboarding for new contributors Replicate an environment in 2 clicks, reduce maintenance time Wed 9/16 14:10 – 14:40 Effective Remote C++ Development with Codespaces Nick Uhlenhuth –

building software! 9So here’s the deal 10 ● You are hired as a programmer to perform some maintenance ○ The software is a very exciting screen saver software! ○ You’re going to get lots of $$$ to enforced the order of our traversal as well ○ It doesn’t look like it, but we have made some improvements! ■ (Next slide) 81A First Take at the Iterator Pattern (2/2) ● Each time we iterate, we are

libraries, GitHub Expanding Implementations DPC++ ComputeCpp triSYCL hipSYCL neoSYCL Regular Maintenance Updates Spec clarifications, formatting and bug fixes https://www.khronos.org/registry/SYCL/ Parallel Reductions adds a built in reduction operation Work-group and sub-group algorithms Improvements to atomic operations Class template argument deduction (CTAD) and deduction guides Simplification

checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1879 105.19 Proper maintenance and care of multi-threading locks . . . . . . . . . . . . . . . . 1881 105.20 Arrays with custom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1986 108.3 Compiler/Runtime improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.4 Command-line option changes dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1991 108.12 Tooling Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1992Part I Manual 1Chapter

checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1879 105.19 Proper maintenance and care of multi-threading locks . . . . . . . . . . . . . . . . 1881 105.20 Arrays with custom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1986 108.3 Compiler/Runtime improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.4 Command-line option changes dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1991 108.12 Tooling Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1992Part I Manual 1Chapter