From a9074ad47fb928bde2475bac2cac63f9ebcc168e Mon Sep 17 00:00:00 2001 From: Pejman Ghorbanzade Date: Thu, 28 Sep 2023 22:51:33 -0700 Subject: [PATCH] [cppcon23] update slides --- slides/cppcon23/pages/01_intro.md | 51 ++++++++++++++++--------------- slides/cppcon23/slides.md | 2 +- 2 files changed, 27 insertions(+), 26 deletions(-) diff --git a/slides/cppcon23/pages/01_intro.md b/slides/cppcon23/pages/01_intro.md index e1cc6fe..2164350 100644 --- a/slides/cppcon23/pages/01_intro.md +++ b/slides/cppcon23/pages/01_intro.md @@ -69,11 +69,11 @@ slide: Maintaining Software
  • Writing documentation
  • Resolving technical debt
    • -
    +
    -
    +
    The only constant in life is change. - Heraclitus
    @@ -89,8 +89,6 @@ what would meet those requirements, our preferred way of solving a given problem have changed. Either way, we change code to tend to our software, just like a gardener tends to its garden. -click - After all, software is much like a living organism. It is constantly evolving until it ceases to deliver value. --> @@ -111,11 +109,11 @@ slide: Types of Change
  • Changing system configuration
  • Updating build system toolchain
    • -
    +
    -
    +
    Software engineering is programming integrated over time. - Titus Winters
    @@ -126,13 +124,15 @@ more efficient. To make the code simpler, more readable, easier to understand and change in the future. We make these changes with good intentions. Some changes are easy and limited -in scope, like improving a function implementation, and some are hard and may -require large-scale refactoring, like supporting a new compiler. But regardless -of their type, every change to our software runs the risk of breaking it. - -click - -Managing this risk is the art that makes our craft interesting. +in scope, like fixing a compiler warning and improving a function +implementation. And some are hard and may require large-scale refactoring, +like supporting a new compiler. Or even larger, they could be rewriting a +legacy system component that could take months if not years to complete. +Like this Indiana Bell building here on the screen that was rotated in 1930 +without ceasing operations, to make room for a new city projects. + +But regardless of their type, every change to our software runs the risk of +breaking it. Managing this risk is the art that makes our craft interesting. --> --- @@ -180,21 +180,21 @@ section: '' In the next hour, we are going to cover what Continuous Regression Testing is and how it is useful. -Then we will have a live demo of a free and open source -Continuous Regression testing system to understand how it can be used in -practice and for real-world use cases. +Then we will showcase a free and open source Continuous Regression testing +system to understand how it can be used in practice and for real-world use +cases. -Then we will see how that system works and review some of its design decisions +We will see how that system works and review some of its design decisions that could be helpful for building other similar systems. Next, we will cover how to use a regression testing tool effectively and how to navigate the common pitfalls that lead to slow and flaky high-level tests. -Then we will have another series of live demos to see how Continuous Regression -Testing can help us identify other types of regressions such as changes in -performance, and output binary size. +Then we will also see how Continuous Regression Testing can help us identify +other types of regressions such as changes in performance, and output binary +size. -And lastly, I hope to convince you that no tool or method could serve as a +Next, I hope to convince you that no tool or method could serve as a silver bullet and efficiently building safe systems requires a culture of safety that combines a variety of tools and methods to mitigate the risks of everyday code changes. @@ -282,10 +282,11 @@ software systems. I started my career at a cyber-security company acquired by VMware, then moved to Canon to build medical imaging software for four years. -A part of my talk today showcases the software that I originally built for my -team at Canon, and then sold to other companies when I got the IP rights and -started a startup. What I am sharing today is the story of this adventure -that I've pursued with passion for the past five years. +A part of my talk today showcases the software that I originally built as a +side project for my team at Canon. And and then sold to other companies when +I obtained its IP rights and left Canon to start a company around it. +What I am sharing today is the story of this adventure that I've pursued +with passion for the past five years. --> --- diff --git a/slides/cppcon23/slides.md b/slides/cppcon23/slides.md index c332169..d8837b4 100644 --- a/slides/cppcon23/slides.md +++ b/slides/cppcon23/slides.md @@ -37,7 +37,7 @@ sectionDefault: '' --- src: ./pages/02_demo.md -sectionDefault: Live Demo +sectionDefault: '' --- ---