You are just putting bandages on your wounds. So far, the things you read and tried are what I call the first aid kit. Swift hits 2.0 and iOS 9 is released next month. How that is supposed to help you write unit tests.īut you are still not doing it. You read a lot about design patterns and how to refactor your view controllers. If this sounds familiar to you, you may have already attempted to fix the situation. Thanks to Massive View Controller.įailed Attempt at Solving the MVC Problem This same vicious cycle happens every time you need to fix a bug or add a new feature. Because there is no unit tests to prevent regression. While doing all of these, you fear you may break something else. Make a change to see how it behaves differently. Trace through various conditionals and loops. Navigate through 50 classes, protocols, and methods. If only they had asked me to do that 2 months ago while the code was still fresh, it would have taken less time. They should focus on functions, not UI first.They need to stop changing requirements.They don’t know how complicated that thing is.Maybe the problem lies in the client? They just don’t understand how development works. To make matters worse, as developers, we have a tendency to underestimate how long something will take. “I thought you said it would be done in a couple hours.” If it takes longer than your guesstimate, it comes back to bite you. But you know deep down in your gut that you just aren’t sure. Your client asks for an estimate to fix a bug. Check out the handbook for even more bonus materials. It also works with the latest versions of the Clean Swift templates, Xcode, and Swift. The Clean Swift Handbook is an updated version of this blog post, plus additional chapters to cover the entire CleanStore sample app.
0 Comments
Leave a Reply. |