Swift and Memes

Have you ever wondered what your developer skills are actually worth now?

You’re deep in a tricky bug when Slack pings: a colleague needs a code review.

Imagine a quarter-long refactor: turning a big ball of mud, held together by RxSwift and 1500-line view models, into a modular, fully testable codebase.

It’s Monday morning.

So, you’ve finally convinced stakeholders to raise the deployment target from iOS 15 to iOS 17 – and the first thing on your mind is @Observable.

If you’ve cared about code quality and consistency before AI-assisted coding became standard, you surely understand the pain of setting development standards in the team.

Imagine you’ve just built an amazing iOS app for a restaurant.

How much time have you spent staring at an empty mailbox after applying to numerous positions?

After tackling the Single Responsibility Principle and Open-Closed Principle, it’s time to explore the Liskov Substitution Principle (LSP) and how it can help us write better code.

Over the years, we’ve been told to use dependency injection to help our apps scale better.