8Proprietary + Confidential C++ Core Libraries 9Proprietary + Confidential Large Scale Refactorings & Automated Refactoring Tools 10 10Refactoring Tool Use Cases 02 11Proprietary + Confidential Consistent

restrictive (Automated) 1.1.12 Ensure that the etcd data directory ownership is set to etcd:etcd (Automated) 1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated) 1.1 file permissions are set to 644 or more restrictive (Automated) 1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600 (Automated) 1.1.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Automated) 1.1.2 Ensure that the API server pod specification file ownership is set to root:root (Automated) 1.1.3 Ensure that the controller manager pod specification

continuous delivery i. Create the foundation of our deployment pipeline ii. Enabling fast & reliable automated testing iii. Enabling & practicing continuous integration & testing iv. Automating, enabling, fixed forward, but changes not put back into version control. Focused on version control and automated environment creation – time reduced from 8 weeks to 1 day b. ENABLE ON-DEMAND CREATION OF DEV, environment specifications 1. Create a common build mechanism to create it on demand 2. Codified in automated environment build process iii. Environments will be stable, reliable, consistent, & secure c.

of TestingWhether or not you write an automated test, you need to make sure the code you are writing works.Test Everything on every feature Write Automated tests and run them continuously Test Everything on every feature Write Automated tests and run them continuously Test the change you just made Testing StrategiesTest Everything on every feature Write Automated tests and run them continuously Everything on every feature Write Automated tests and run them continuously Test the change you just made Testing StrategiesTest Everything on every feature Write Automated tests and run them continuously

Minutes 87What is an Error? 88Just a Notification: Nothing to See 89If Only Someone Told Me 90No Automated Monitoring 91Rollback??? 9293 Really Good Bugs94 How can we test it?95 How can we test it? •Code Review •Automated Tooling - part of CI106 How can we test it? •Reuse an existing "value" for completely different functionality •Um... Don't do that. •Code Review •Automated Tooling - part Enum Values (Version Control Tracking) 2. Enumeration/Constant Versioning and Deprecation 3. Automated Static Code Analysis for Renaming 4. Semantic Versioning for Enums 5. Refactor Scripts and Tools

engineers for every Google property d. SPREAD KNOWLEDGE BY USING AUTOMATED TESTS AS DOCUMENTATION AND COMMUNITIES OF PRACTICE i. Ensure automated tests demonstrate use and behavior of libraries and components possible; standardize and automate (rinse and repeat) ii. Collectively define handoffs, for non-automated work, as clearly as possible to reduce lead times and errors g. ENSURE TECHNOLOGY CHOICES HELP bad paths to effectively address QA, Infosec and related concerns. Incorporate these paths into automated tests 1. Static Analysis – inspect program code for all possible run-time behaviors and seek out

Software Reliability Association, 2008 • Continues to be the reference despite its age • For automated static analysis tools • Aimed for embedded domains • C++11/14/17/20 but not safe • High Integrity 54% CERT C++ 156 0 75 33 69% These are the 2 most important guidelines today C++ CG: Meta + automated checkable rule • Follow Bjarne’s talk on type+resource Safety on C++ CG • Aim for bug free code mutable data ○ Encapsulate messy constructs, rather than spreading through the code MISRA and Automated checkable rules with some meta ● Code will always have bug, but they must do no harm What is

contractors are required to develop program elements. Program can leverage test infrastructure and automated tests, and testers are active throughout development. Test Environment Extensive development code check-ins, integration, and builds can occur on a daily basis. Frequent code updates and automated testing create a high demand32 for managing the complexity of version control. If issues arise focuses on program/enterprise-level activities such as creating a CM strategy and tools.  Use automated tools to enable continuous integration, reduce delays in integration and testing, and provide CM

integration of big data, AI, robotic control, and device-cloud collaboration systems can deliver automated production, network-based collaboration, customization, and other service transformations. These provides tuning services for external systems, including intelligent decision-making (Analysis) and automated tuning (Tuning). By contrast, the backend service layer is an HTTP service layer executed by Python Technical White Paper Innovation Projects A-Tune delivers intelligent decision-making and automated tuning. Intelligent decision-making is to sample system data and identify the corresponding loads

are stored in Git. Furthermore, it should be automated to apply changes to the system automatically when they are approved. GitOps prefers immediate automated deployments to achieve the desired state quickly overall DevOps process by testing and deploying changes quickly with the help of: CI/CD tools Automated deployments Shorter feedback loops By having infrastructure as a part of the CI/CD pipeline, any not properly documented. Streamlined, automated pipelines GitOps translates all the manual, complicated infrastructure management tasks to a streamlined, automated pipeline. This declarative version-controlled