Shifting Left, Shifting Right
summary
Argues that evolution shifts work between code, tooling and collaboration with concrete examples: a working one-batch-file integration that auto-serves builds via Subversion, the era of CVS/SourceSafe where everyone once lost all the source, a 2009 commit of 4,000 edits to convert string handling, protocol buffers (2001) and IDL for cross‑platform RPC, and a year-long Docker unit-test effort that finally lands; concludes smaller commits, configurable runtime behavior and file embedding are what actually reduce merge pain.
AI-written summary · about
chapters (10)
- 0:00Shifting left and right intro
- 1:50Shifting left and right concept
- 3:58Build processes evolution
- 8:15File locking and DB deploy
- 12:03Interoperability with protobuf
- 13:26Smaller source code commits
- 16:16Large feature branch issues
- 18:23Shifting right with config
- 19:45Tooling for software changes
- 20:52Past practices and future
related talks
56mComputing From Creationism to Evolutionism
34mCode Review, Forwards and Back
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
45mPanel Discussion Refactoring
47mAdventures with C++ Legacy Codebases: Tales of Incremental Improvement
13mShift left the proper way
40mLegacy Evolution – The Innovation Opportunity!
35mQuickly and Safely Refactoring Legacy Code