Dexcom

Codable is a new feature in Swift 4 that dramatically improves the process of converting between objects and their representations. Join us as Mattt (@mattt) shows us how to take advantage of Codable in our own projects, and shares interesting tidbits about the feature's history, underlying implementation, and how its performance stacks up against the alternatives.

Show up around 6:30 for networking and the like. The presentation will begin at 7.

Bring a project you've been working on and want some feedback on, or a problem you've been struggling with and need help on, or maybe you've got something you'd like to pair with somebody on, or just something you want to show off. We'll have people there with a mix of experience levels and knowledge about all kinds of different technologies and aspects of our field. So, whether you want to be there to help answer questions and share your experience, or reap the benefits of other's experience the goal is to create a space to just make some progress on something, whether it's your project or someone else's!

As usual there will be plenty of opportunity for just networking and catching up time if you don't have a specific project or anything, please do come, we'd love to just talk shop with you too.

Also, thanks to Jay for prompting this idea! If you're available for it he's doing an Ask a Dev tomorrow afternoon (3/8) at Palio, check it out: https://www.meetup.com/Ask-A-Dev/events/248354898/

With ARC and Swift, memory management isn't nearly as difficult as it used to be, but I think every app developer has bumped up against problems with memory management at some point in their career, whether that shows up as crashes or poor performance or just plain weirdness at run-time. This month I'll go over a few tips 'n' tricks I've collected over the years about how to find and fix problems which stem from the mismanagement of memory using the tools built-in to Xcode and Instruments.

Hope to see you there!
Ryan