The Design Patterns book came out over 25 years ago. Are patterns still relevant today, especially for Swift developers?At Quality Coding we train iOS developers in technical agile practices—such as refactoring. Recently I refactored a fully tested view controller to MVVM, model-view-view model. The example stopped at an interesting place. Here’s the code:There will be
What does refactoring actually look like? Let’s continue an example based on a real iOS view controller. I gave a talk for CocoaHeads NL called “Real Refactoring” where I demonstrated refactoring a view controller from MVC (model-view-controller) to MVVM (model-view-view-model). At least I started to, but for the sake of time, I cut the demo
What is refactoring? Like most of the technical agile practices, seeing the final code doesn’t help. That’s because refactoring is a process; it’s hard to grasp until you see someone do it. So I gave this 27-minute talk showing what real refactoring can look like for iOS developers. You’ll see several refactoring practices in action that I
Refactoring is moving in small steps, with each step verified by unit tests. As I demonstrated last time, these steps are much smaller than most people are used to. Let’s continue the same example to learn some new things about refactoring. Reading is not as good as doing. I learned from the folks at Big Nerd
Refactoring remains a much-misunderstood discipline. Even when folks do have unit tests to back their changes, how long does the code stay broken? Let’s return to the idea that refactoring happens in very small steps. No, even smaller than that. Table of Contents Motivating ExampleTake Smaller StepsMove Field RefactoringReducing the Amount of ChangeA Sequence of Very
Page [tcb_pagination_current_page] of [tcb_pagination_total_pages]