You spoke. The world is shifting. It’s time for Quality Coding to go Swift!
Better late than never.
I want to thank everyone who participated in my 2016 reader survey. Your number one request was clear: “More Swift”.
When Apple first announced Swift, my Twitter feed was filled with folks struggling with the basic tooling. I need to get stuff done, so I waited while the early adopters took the hard knocks. You paved the way. Thank you.
I have yet to work on a team that uses Swift for production code. But I watched Apple’s WWDC 2016 announcements with interest. I’m still playing catch-up on the sessions, but “Swift API Design Guidelines” was noteworthy. An entire session on clean, readable code, and how Swift 3 changes the experience… I’m in! I want that!
So let’s try this. I’m going to start a new version of the Marvel Browser—this time in Swift. I’ll give the Swift version higher priority than the Objective-C version. This will have the following effects:
- My posting frequency may decrease. I’ve been trying to keep up a weekly cadence this year. Expect bumps in the rhythm.
- I’ll need your help! My initial attempts at Swift will come from an Objective-C mind. As I write stuff, please don’t hesitate to suggest ways that are more Swifty.
Do you have any tips or suggestions for me as I start? I value your input, so please leave a comment below.