Subscribe And Get 4 FREE Power Swift Playgrounds With The Latest Swift 2.0 Syntax
You'll learn: Error Handling with Swift 2.0, Protocol-Oriented Programming, Reference vs Value Types, and Higher Order Functions
I've finally have little bit of time set aside this weekend to work on a fun side project. Ever since I saw my friend @chiuki's Fit Cat app on the Android Watch, I knew I needed to have it on my Apple Watch and @chiuki agreed to let me make it.
Of course when I started my new project, I opened the Assets Catalog, and was immediately tempted to create Fit Cat stickers. After all, wouldn't it be fun to share these with your friends?!!!
So today I’m going to talk about a topic that I’m completely uncomfortable talking about publicly - diversity in tech and in our community. Wish me luck 🙈
At the try! Swift Conference in Tokyo, @purpleyay gave a mind-blowing talk on Type Erasure (full video and slides here). I’m honestly still trying to wrap my head around it, and especially the use-cases, but for now, I wanted to write down the example from the talk to keep in my mind and refer to later when it suddenly fits the problem I’m solving.
I’m currently reading Refactoring to Patterns (affiliate link). Yesterday, when I wrote about the Creation Method for an object that has a lot of parameters, it made me think of @modocache‘s amazing talk on Swift Patterns in iOS API Design, specifically the part of about Parameter Objects. This has come up for me a few times since I initially saw the talk, so I wanted to document it here.
As I spoke at and attended several conferences last month, the book Refactoring to Patterns (affiliate link) kept coming up again and again, especially in my favorite talks. I finally have a little time to read it (before all the after-WWDC-announcement craziness ascends), and I’d like to document the patterns I like for future reference. I also found it better to remember the information by translating the Java in the book to Swift. The first pattern is the Creation Method.
It's a common pattern in Swift (and a really nice one!) to configure constants right when they are initialized in a closure vs later on in a viewDidLoad or another such method... but it can get awkward!
I recently gave a talk on Practical Protocol-Oriented-Programming(POP💥) in Swift. The video is still being processed. Meanwhile, here is the written-up version of the POP View part of the talk for reference (for me and anyone else!).
I recently gave a talk on Practical Protocol-Oriented-Programming (POP💥) in Swift. The video is still being made. Meanwhile, here is the written-up version of the POP Networking part of the talk for reference (for me and anyone else!).
Notice the thing! Since each View Controller would be injected with something specific – it could be text-based or number-based or array-based, anything! I didn’t know how to name the parameter. So thing seemed like the most fitting parameter name.
I read a comment by @cduhn on my I 💖 Storyboards & Nibs blog post that triggered an idea for a slightly better solution for this...