~/talk

Branch By Abstraction

slides:none on file

Branch By Abstraction is a concrete technique for trunk‑based development: introduce an abstraction + toggle, implement both old and new implementations in the mainline, keep every commit build‑green, add unit tests for each implementation, and flip the toggle when the new path is fully tested. It lets long, multi‑release migrations (message format and bus changes at a bank; a C++→Java rewrite at an airline) be pausable and resumable, avoids noisy merges from long‑lived branches, and permits safe removal of the old code after a successful rollout.

AI-written summary · about

  1. 0:00Start
  2. 3:28Trunk Based Development facilitates lots reca
  3. 5:10Bad Branching Models /2 (recap)
  4. 10:35Big to change thing - our intenton
  5. 11:39Big to change thing - our fear
  6. 12:41Big to change thing - our nightmare
  7. 14:47Reminder of the nightmare
  8. 15:40Idealized life on the trunk
  9. 17:53The big change in trunk alongside regular work
  10. 18:56Branch by Abstraction - first commits
  11. 20:43What other devs see at the start
  12. 21:49Part way through, for the dev doing the BbA we
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.