If you put bad code in your pipeline, guess what comes out?
CI/CD pipelines were invented to find improvements for already very clean code. They don’t magically fix legacy code. Sticking a bunch of untestable code through it isn’t going to get the job done. Your company has committed to DevOps; now you need clean code for the pipeline.
We teach specific technical habits that cleans the code in the pipeline.
Tier 1: Getting the Foundations
Invest 6 weeks of Code by Refactoring Foundations to fundamentally change how developers leverage the new tools and abilities.
- Start Refactoring Safely (2 virtual weeks)
- Naming as a Process (2 virtual weeks)
- Know When to Stop (2 virtual weeks)
Tier 2: Fixing the Exploding Pipeline
Invest 18 months to get through these four critical milestones effectively with results that will stay for the long haul. Not only will you ultimately stop shoveling bad code into your pipeline, but you’ll see explicit and measurable results as you go!
Milestone 1: Prep Code for CI
Workshop Series: Test Untestable Code (12 virtual weeks)
Milestone 2: Escape the Monolith
Workshop Series: Ship from Crossover System (8 virtual weeks)
Workshop Series: Remotely Coupled Code (8 virtual weeks)
Milestone 3: Verify Hard to Test Code
Workshop Series: Advanced Testing (10 virtual weeks)
Workshop Series: Test Challenging Dependencies (12 virtual weeks)
Milestone 4: Teams Ship Independently
Workshop Series: Break a Services out of the Monolith (10 virtual weeks)
Workshop Series: Change Data Back-end (12 virtual weeks)