Tales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
summary
Teams standardize on a git host, issue tracker and wiki, adopt a git feature-branch workflow with peer-reviewed PRs, and enforce formatting with an IDE or CI code formatter so PRs stop dying over style. Dependabot or Renovate runs produce one-click dependency-update PRs that pass tests, saving daily upgrade toil. A fragile C background service gets replaced by ~10 lines of Java tray-code, tests document behavior, and small, steady process changes raise the bus factor and reduce outages.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 1:50Understanding the bus factor
- 4:23Standardizing workflow for teams
- 12:09Solving code formatting wars
- 17:19Automating dependency updates
- 23:27Documenting behavior with tests
- 27:21Using standard tools over custom solutions
- 32:04Benefits of open-sourcing solutions
- 34:32Rotating responsibilities in teams
- 39:48Q&A session
related talks
35mQuickly and Safely Refactoring Legacy Code
33mKeep your dependencies in check
32mContinuous Integration and Deployment: Five Lessons Learned
50mEmbrace the Pitfalls (Our stop start journey to Change)
47mCode review beyond code style
20mJourney Of Devops Teams in a Corporate Environment
32mTales from the DevOps Transformation Trenches
37mKeep Your Dependencies in Check
