Practise the standard verbs for porting code and bridging old and new APIs during a migration.
0 / 5 completed
1 / 5
Fill in: 'We plan to ___ the codebase from the old framework incrementally.'
We 'port the codebase' — the standard collocation for moving code to a new language or framework. 'Carry', 'haul' and 'ferry' are not idiomatic for software migration.
2 / 5
Fill in: 'The team will ___ legacy modules one package at a time.'
We 'rewrite modules' — the standard collocation for replacing old code with new implementations. 'Redo', 'remake' and 'reform' are less idiomatic in engineering contexts.
3 / 5
Fill in: 'We use a compatibility layer to ___ old and new APIs during the transition.'
We 'bridge APIs' — the standard collocation for connecting old and new systems during migration. 'Link', 'join' and 'tie' are weaker and less idiomatic here.
4 / 5
Fill in: 'Automated codemods help us ___ syntax changes across thousands of files.'
We 'apply changes' — the standard collocation for running automated transformations. 'Put', 'place' and 'set' don't collocate naturally with syntax changes.
5 / 5
Fill in: 'Once the migration is stable, we ___ the old code path entirely.'
We 'strip out' old code — the idiomatic phrasal verb for removing it cleanly. 'Peel', 'scrape' and 'clear off' aren't standard for removing code paths.