Moving fast and staying aligned how automation powers progress
summary
Claims a platform team keeps 300 engineers across 35 teams moving fast over 5 million lines of code by centralizing a 3,000‑line Maven parent, managing ~200 dependencies, and releasing monthly. Tools actually used: Google Java Format, Renovate, Maven Enforcer, ArchUnit, OpenRewrite and errorprone support with 9,950 refaster rules. Concrete outcomes: a summer intern automates the TestNG→JUnit migration (95% annotation swaps) and four engineers migrate Spring Boot 2→3 across 70 repos and 3M lines in weeks.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:53Code quality at scale
- 3:38Reducing bike-shedding with automation
- 5:21TestNG to JUnit migration
- 8:10Picnic’s platform team
- 9:35Developer productivity pillars
- 11:20Maven config benefits
- 12:22Code formatting with Google Java Format
- 13:05License compliance with Maven License Plugin
- 14:06Build profile optimization
- 14:49Maven dependencies and Renovate
- 15:11Dependency conflict prevention
- 15:54Cleaning unused dependencies
- 16:38Shared monitoring/testing libraries
- 18:48Checkstyle and SonarCloud
- 19:31Git history with Git Blame Ignore Refs
- 20:11Architectural rules with ArchUnit
- 21:59Error Prone bug detection
- 22:43Refaster rules for patterns
- 23:47Error Prone Support rules
- 24:51SLF4J logging fixes
- 25:31OpenRewrite refactoring
- 26:16Spring Boot 2 to 3 migration
- 27:18Tools and rollout strategy
- 28:22Smoothing upgrades with CI
- 29:46Rolling out Error Prone Support
- 32:55Recap
- 33:37Q&A
related talks
48mWeeding Your Micro Service Landscape
13mModernize your money-maker
43mThe Engineering Playbook for Growing Android Teams
36mThe Impact of App Platform Teams
39mMobile Developer Productivity Panel
38mScaling Automated Testing & Architecture from Startup to Enterprise
51mFrom Developer Pain to Impact: Establishing Large Scale Refactoring at SAP
12mHow we automated code maintenance