Building a Secure and Maintainable PaaS Leveraging eBPF to Scale Security and Improve Platform Support Bradley Whitfield October 28, 2020 2 Dragon - Internal Platform as a Service TIP: To change

else at PickNik Thanks to:Bilal Gill Leveraging a Functional Approach for More Testable and Maintainable ROS 2 Code Thank you! All code and the presentation are available at https://github.com

convinced our solution (especially if the code is going to live a long time) is: ❏ Flexible ❏ Maintainable ❏ ExtensibleQuestion to Audience: ● How well do you think I as a developer can predict at each type) 32 ● So is this code (‘makeObject’ specifically) ○ Flexible? ❏ (your thoughts?) ○ Maintainable ❏ (your thoughts?) ○ Extensible ❏ (your thoughts?)Question to Audience: ● How well do you think ObjParamsType and use inheritance for the types (okay interesting idea...needs to be worked out more) ○ Maintainable? ❏ Not really ❏ If I remove an object type, do I renumber? ❏ What about the parameters? ❏ How

Abstract Design Patterns are reusable elements of design that may help aid in making software more maintainable, flexible, and extensible. The term 'design patterns' can be traced back to at least the 1970s blueprints’ for developing software. ● Design patterns can help make programs more: ○ Flexible ○ Maintainable ○ Extensible 22Design Pattern (2/2) ● A common repeatable solution for solving problems. ○ blueprints’ for developing software. ● Design patterns can help make programs more: ○ Flexible ○ Maintainable ○ Extensible 23 These are very likely things we want on large, collaborative software projectsOrigins

Replicable Accurate Precise 46Rule 0 Write unit tests 47Part 2: Good Code Three Aspects: Readable Maintainable Documentary Good Tests Good Code 481) Readability Unit Tests must be correct by inspection Tell a story (three-act) Correct-by-inspection (even if the reader doesn't know what it does) Maintainable Minimize changes to UT code under maintenance (BB wins) Documentation (BB) Max value of tests Tests: Replicable and Repeatable Accurate and Precise Falsifiable Hypotheses Good Code: Readable Maintainable Documentary Good Process Design TDD With a side helping of Black Box / White Box Philosophy

Reach common understanding of implementation policies in a team • -> To make readable and maintainable code © ����-���� BASE, Inc. • No absolute answer for any projects • We should determine a �.Common understanding of implementation policies in a team • -> To make readable and maintainable code We are not able to achieve “common understanding” ? © ����-���� BASE, Inc. �� Problem

specific jobs well, and connect them with channels. – In practice, this yields simpler and more maintainable code. • Think about the concurrency issues that matter: “Don’t communicate by sharing memory trade-offs that I’d normally worry about I no longer worry about. I bust out lots of fast, correct, maintainable testable code in very small amounts of time, without much code. I haven’t been this excited

allowing Wicket to build component hierarchy in Java automatically making your code simpler and more maintainable. This chapter should serve as a short introduction to what Component Queueing is and what problems by all descendant components. Thus, hierarchy on the Java side allows us to write succinct and maintainable code by making use of the parent-child relationship of components. 14.1.3. Pain Points of the having to define the hierarchy only once in markup we can make the Java-side code simpler and more maintainable. 149 Chapter 15. Internationalization with Wicket In chapter 12.2 we have seen how the topic

allowing Wicket to build component hierarchy in Java automatically making your code simpler and more maintainable. This chapter should serve as a short introduction to what Component Queueing is and what problems by all descendant components. Thus, hierarchy on the Java side allows us to write succinct and maintainable code by making use of the parent-child relationship of components. 14.1.3. Pain Points of the having to define the hierarchy only once in markup we can make the Java-side code simpler and more maintainable. 148 Chapter 15. Internationalization with Wicket In chapter 12.2 we have seen how the topic

allowing Wicket to build component hierarchy in Java automatically making your code simpler and more maintainable. This chapter should serve as a short introduction to what Component Queueing is and what problems by all descendant components. Thus, hierarchy on the Java side allows us to write succinct and maintainable code by making use of the parent-child relationship of components. 14.1.3. Pain Points of the having to define the hierarchy only once in markup we can make the Java-side code simpler and more maintainable. 142 Chapter 15. Internationalization with Wicket In chapter 12.2 we have seen how the topic