Become a better iOS engineer: why I'm learning in public

After 4+ years shipping production apps with Swift, UIKit and SwiftUI, I know something every experienced engineer eventually admits: shipping features every day doesn’t automatically make you better at the fundamentals.

So I built myself a study roadmap — the topics I want to truly master, from memory management and concurrency to the design decisions behind SwiftUI — and I’m going to work through it in public, one post at a time.

Why in public?

Three reasons:

1. Writing forces clarity. If I can’t explain a concept simply, I don’t understand it yet.
2. Accountability. A public series is harder to abandon than a private notes folder.
3. English practice. I work with international teams; writing technical English is part of the job.

What to expect

Short, practical posts. Each one takes a topic from the roadmap, explains it the way I wish someone had explained it to me, and shows real Swift code where it helps.

If you’re an iOS engineer sharpening your fundamentals — or a recruiter wondering how I think — this series is the most honest picture of me you’ll find. See you in the next post.