Final thoughts
Our learning journey in this book comes to an end, and now you have mastered Swift's techniques for creating high-performance applications. Let's have a quick recap.
By now, you have learned how to use the power of Swift and optimize your Swift code, but you should remember the main rule of optimization—optimize only when needed, not upfront.
Solid architecture and well-structured and clean code are two of the most important characteristics of a good application. We have been expressing this throughout the book, and an entire chapter (Chapter 2, Making a Good Application Architecture in Swift) was dedicated to it.
Performance optimization doesn't always have to bring much complexity to the source code. Sometimes, applying small changes, such as adding the @noescape attribute, removing a few print statements, using the correct data structures, and other techniques presented in the book, could improve performance with no negative effect on the source code. Sometimes, the source...
