☠️ How Not to Write Swift
updated about 1 year ago
This proposal has been withdrawn...
Swift gives us a dazzling array of features we can deploy to really screw up our code, so why use just one when you can have them all?
Sometimes it's easier to learn what's right by seeing what's wrong, so in this talk I'll walk through example code and fix the problems inside. Of course, you don't make these kinds of mistakes, but you have A Friend who does, so this talk is for you. Er, them.
Y̶o̶u̶ Your friend will learn:
- ✍️ Why protocols make composition easier but can often produce slower code.
- 💯 How keypaths, associated types, and generics can help you structure your code more naturally
- 👣 Three easy ways to avoid tight coupling using Cocoa design patterns.
- 😳 Why most people who write their UI in code are doing it wrong.
- ⚡️ When force unwrapping isn't as bad as you might think.
So, if your friend wants to put Swift design patterns to better use, make their MVC so good they don't keep feeling embarrassed when someone mentions MVVM, and use keypaths, associated types, and generics in the same code without their brain exploding, this is the talk for them. (And possibly you.)