Swift

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.

Code

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 / Podcasts / Books

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?

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!