{CodeRoyale}
All challenges
Multiple ChoiceIntermediate 45s

Branch by abstraction

Which scenario best fits the 'branch by abstraction' refactoring technique?
Options
  1. 1Creating a separate git feature branch for each developer so their work stays isolated until merge
  2. 2Using a database migration tool to evolve the schema incrementally without downtime or data loss
  3. 3Swapping a large subsystem's implementation gradually behind an abstraction while both coexist
  4. 4Splitting a single repository into two smaller repositories so each team owns its own history
architecturerefactoringbranch-by-abstraction

Think you can answer under pressure?

Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.

Play this in a 3-minute battle