Pillar Three: Boundaries of Change

#56 - Refactoring–The Discipline for Writing Good Code - Christian Clausen

Topic 10 of 18

Published Sep 20, 2021 · Clip 24:54–25:57 (1:03)

Christian explains the boundary of change principle: draw a line around the code you own, and anyone outside that line (library users, front-end users, other teams, database owners) must not be affected. You can't change public interfaces or things outside your control, but you can change the layer right after code enters your boundary. Outsiders should never be able to tell whether you refactored.