I hope that today you inched a little closer to understanding closures, and that you’re starting to see that they are really just a very special kind of function. Sure they have weird syntax, and yes the capturing thing makes them behave in all sorts of interesting ways, but ultimately they are just anonymous functions that you pass around as if they were data.
If you’re still not sure about closures, it’s OK: we’ll be using them again and again, and sooner or later they’ll click. You’d do well to remember the words of Patrick McKenzie: “every great developer you know got there by solving problems they were unqualified to solve until they actually did it.”
Anyway, you have another project under your belt, and I hope you feel happy with everything you learned. Of course, now it’s time to solidify your knowledge with a test and some fresh challenges – you need to go beyond just following along with me, otherwise you’ll have a hard time remembering anything in the long term.
Today you should work through the wrap up chapter for project 5, complete its review, then work through all three of its challenges. As you’ll see, there is also a bonus challenge today – you need to be a bug detective!
Once you’re done, tell other people: you’ve built your second game for iOS, and you’ve learned more about table views, alert controllers, and more.
You should be proud of what you’ve accomplished – keep going!
Need help? Tweet me @twostraws!
SPONSORED Catch bugs as soon as they happen and know exactly why a crash occurred. Instabug's SDK grabs all the logs they need to fix bugs, crashes and performance issues in minutes instead of days. Get screenshots, device details, network logs, repro steps, and tons of other critical insights needed to resolve issues and prioritize product backlogs straight from your dashboard. It only takes a minute to integrate!
Link copied to your pasteboard.