Alex Ozun

@alexozun
365 Followers
471 Following
246 Posts
Staff iOS Engineer | 
Writing: https://swiftology.io
Based in 🇬🇧 Born in 🇺🇦
All opinions are my own
Singapore is one of the most #vegetarian unfriendly metropolises I've been to.
Which is really unfortunate because it's pretty cool otherwise.

This is my reinterpretation of Kent Beck's old tweet.
But it accurately describes what my experience leveraging agents effectively has been like so far.

https://x.com/KentBeck/status/250733358307500032

Kent Beck 🌻 (@KentBeck) on X

for each desired change, make the change easy (warning: this may be hard), then make the easy change

X (formerly Twitter)
Make the AI agent’s job easy (warning: this may be hard), then give it an easy job.

I initially planned this as a short post on socials, but it quickly evolved into a blog. So here’s my recommended reading list to get you from Zero to Hero in Swift Concurrency. It’s mostly based on my personal learning journey, with some adjustments that work better for 2026.

Featuring works of:
- @pedro
- @mattiem
- @saagar
- ...and others
#swift #swiftlang

https://swiftology.io/articles/swift-concurrency-zero-to-hero/

Swift Concurrency from Zero to Hero | Reading List | Swiftology

In this short post I want to recommend an ordered reading list that will get you from Zero to Hero in Swift Concurrency

Swiftology
What's the future of library and framework development?
- Will it die out b/c AI will generate bespoke library code from scratch and on-demand faster than teams can vet and integrate external ones? No dependencies becomes a default.
- Will it grow b/c enterprises with de-skilled workforce will need a solid foundation of well-maintained libs and opinionated frameworks to keep AI variance in check. Frameworks become contracts for behaviour, performance, security, compliance, and enforceable SLAs.
Today at #fosdem #swift in Brussels.
Greeted with a perfect swag for a nippy winter day.

Why is it not an expectation that an AI, in addition to superhuman coding speed, should also have superhuman software design capabilities? What's even the point of it being able to hold entire systems in context if it's not gonna use this power to infer, create, and maintian the perfect design?

When I think of a system designed by AI, I imagine mesmerising fractals, the music of spheres, a perfect engine. Not a blob of slop that AI can maul into desired shape because it's got the biggest club.

I find the juxtaposition of AI being so good that we no longer need to look at the code, and it being so bad that we can't expect it to write maintainable code, so very funny.

Like, I would expect an advance AI that can load, read, and comprehend (whatever it means) entire systems, along with all related documentation, to also be able to create perfect abstractions that accurately model the problem space. And do so continuously.

It's silly that #ios doesn't allow to turn off unused app offloading for specific apps.
Like, I don't want to reinstall and recover access to a tax app every year during the tax season.
#Swift Effect is now in public preview! It's an architecture-agnostic effect system that makes side effects (such as I/O, networking, and concurrency) controllable and testable while keeping application code linear and procedural (no UDF!). Effect Handlers enable natural composition of behaviors. Mock-less testing with step-by-step execution by catching and resuming effects with just-in-time test data. No invasive scaffolding and test-only abstractions common in DI libs.
https://github.com/Alex-Ozun/swift-effect