Swift
Thoughts on Swift access control
The last few weeks have seen exhausting discussions on the Swift evolution mailing list about the proposal SE-0159 to fix access levels. With the proposal officially rejected, Jesse Squires went for a write-up of the entire story.
Escaping and Nonescaping Closures in Swift 3
Swift Unboxed is a gold mine of Swift knowledge, whether you're just starting out with the language or not. Make sure to check out also the articles about Map and Reduce!
Security
One Line of Code that Compromises Your Server
Simple mistakes can compromise your app and your users. Martin Fowler discusses secrets hardcoded in code.
Expect-CT
Scott Helme explains when and how to use Expect-CT, a new security header. If you didn't know, there are more security headers you should use in your HTTP requests.
Tools
Playground
A command line utility to create playgrounds on the fly, with or without dependencies! Very handy when you just want to try out some code!
Glamorous 💄
Kent C. Dodds and the team at PayPal has put together a library to more easily add styles to your React components.
Code
SOLID Principles Applied To Swift
Marco Santarossa explains Uncle Bob's SOLID Principles in Swift. What better use of your time? 😃
Modules vs. microservices
My current team at Just Eat and the team at Hotels.com have been preaching modularization as a fantastic way to split the typical iOS app monolith. Dividing the application this way comes with significant benefits such as the ability for teams to work independently on features, swapping parts of the application on-demand, and of course, encapsulating logic this way allows for an easier to manage and more stable codebase.
Could we use the same approach as an alternative to micro services on the web? This article explores that option. Once again, I invite you to check out also the self-contained systems architecture.
Video
Swift's Pointy Bits: Unsafe Swift & Pointer Types
Why is Swift a "safe" language? And could you do anything to put yourself in control and do "unsafe" stuff? You might know at this point that Swift has an Unsafe​Pointer type, but how far could you go with it?
ECMAScript 2017 and beyond
I've been holding this off for a while now, never having the time to see the video. JavaScript is constantly changing, and it's finally evolving into the language I always wanted to be, rather than the flawed language it used to be before of ES6. Watch this video to see what's coming next!