How I learned Swift

Published Nov 23, 2017
How I learned Swift

About me

I'm a back-end dev and iOS programmer! I've put a lot of work into teaching myself various technologies and covering them comprehensively.

Why I wanted to learn Swift

I've owned an iPhone since the 5s came out and had been previously exposed to Objective-C. I was curious about Swift because it had very Python-like syntax but seemed really powerful.

How I approached learning Swift

My process for learning Swift was, like most of the other languages I know, to sit down and write an application. I began by building a basic understanding of the syntax from Apple's official guide, then moved on to writing very basic apps.

As I progressed, I came to understand other technologies related to Swift (such as CocoaPods and fastlane). As the language continues to develop, I become even more enchanted by its ease of use!

Challenges I faced

With this particular language, I had to completely rely on resources provided by Apple and my ability to find them. With most other languages, there was somewhere for me to turn and someone to ask when I ran into problems. Because I started Swift when it came out, this obviously wasn't very viable!

Key takeaways

I learned very quickly that Swift, like most other languages in development, had some issues. Nevertheless, it still possessed a power equal to Objective-C. Understanding Swift and some of its structures allowed me to grasp other technologies later on. I had never used closures or delegates before, and now I prefer to implement them wherever I can! I was able to take many things I'd learned from it and apply them in many other places.

Tips and advice

As with any language, when learning Swift, you should always have an end-goal in mind. Remember to practice the material. Particularly with Swift, pay attention to enforced coding guidelines and principles.

Final thoughts and next steps

Learning Swift was one of the most eye-opening experiences in the world of code I'd gone through. I'm looking forward to spending more time working with it and scripting in it!

Discover and read more posts from Mason Phillips
get started