Metaprogramming in Swift talk
You can watch the talk online:
You can watch the talk online:
I like using composition and dependency injection, but when you need to inject each entity with multiple dependencies, it can get cumbersome fast.
As the project grows and you need to inject more dependencies into your objects, you will end up having to refactor your methods a lot of times, as we all know Xcode doesn’t help with that.
There is a more manageable way.
Closures in Swift are extremely useful, they are interchangeable with functions and that creates a lot of opportunities for useful use-cases. One thing we have to be careful when using them is to avoid retain cycles.
We have to do it so often that it begs the question:
Can we improve the call-site API?
I’ve been interviewed at Swift Coders podcast:
I’m definitely investing into a better Microphone next time I’m doing any audio recording.
People use different words to classify Engineer skill, some companies give you more senior role just based on a number of years you have been working there, but what does it mean to be Senior?
In this article, I composed a complete and final list of API’s that you need to know to classify yourself as Senior Engineer.
Here’s a list of all the APIs you must know:
Writing tests in iOS apps is a touchy subject. Not everyone is so privileged to be able to write tests full-time, for different reasons.
Some people have full control over their development process and choose not to write tests, maybe because they have had a bad experience with it or they just don’t see the value in them.
I would argue that if you are part of a smaller team, tests can even be more helpful than in big corporations.
A big corporation might have dedicated QA team, but if you are one of 2 developers, then you are often responsible for ensuring quality and reliability of your work, its considerable pressure because each feature you write might break something else in your app.
Let us look at practices and tips for writing maintainable tests in your iOS Apps.
Iterating over design that needs to be reflected in code can be tedious and time-consuming.
Typically the designer works in graphics editing software and then submits flat art to the developer who implements the design in code. Refining the design requires going through the same laborious process.
Even harder if we want to support multiple themes in our apps. How would we even approach that if we were using Interface Builder?
Let’s look at how we can approach implementing a simple library that could solve all of the above concerns.
Swift has very limited runtime support and no meta-programming features.
I created a new tool that changes that, it’s called Sourcery
Using it offers many benefits:
Even if we are writing pure Swift code in our app, we still deal with Objective-C Frameworks like UIKit.
Let’s take a look at how we can improve our MVVM architecture by leveraging a little bit of Objective-C runtime and Protocol Oriented Programming.
As I open source another framework this week, I wanted to share few thoughts about building developer tools.
Developers are lazy creatures, we like to automate stuff, we write scripts, use File Automation to get rid of repetitive work.
One would think that we’d use the same principles in our jobs, yet I’m constantly surprised how few developers actually invest their time into building tools and setting up processes inside their app to ease their day to day work.