Incremental legacy refactoring
You need to improve the structure of a massive ViewController in a live UIKit order feature without rewriting it all at once. If you split the work into small shippable steps, which seam would you create first?
You need to improve the structure of a massive ViewController in a live UIKit order feature without rewriting it all at once. If you split the work into small shippable steps, which seam would you create first?
Start at the points that touch the outside world, like the payment API call, order persistence, and navigation: pull them behind protocols that wrap the existing code as is to create seams, and with the testability those seams give you, move the internal logic over.
ArchitectureShort answerAdvanced
You've been asked to move a 5-year-old MVC app (150 view controllers, almost no tests) to…
#refactoring #legacy #migration
ConcurrencyShort answerAdvanced
You have an old networking layer built on completion handlers, called from hundreds of…
#legacy #migration
ArchitectureShort answerAdvanced
You said you chose MVVM for this feature. When does MVVM actually hurt?
#refactoring
ArchitectureShort answerAdvanced
In an existing UIKit shopping app, the UIViewController handles the API calls, the cache…
#migration