Introduction

After years of building apps and solving problems in many different companies, I’ve decided that the time has arrived for writing some things down. I’m currently in a phase of great change in my career: since the advent of AI, things are moving fast. What was valid 6 months ago might not be valid anymore in one year. I understood that the way we’ve been working for years will inevitably change.

AI is not just a vibe coding tool that produces useless and low quality slop and internet memes: it could be used as an incredible knowledge amplifier: it can help write better code, learn new concepts faster, explore ideas and knowledge fields we wouldn’t have considered otherwise, and significally expand the range of individual possibilities, in multiple scenarios and disciplines. It improves productivity by expanding our vision behind our simple specialization, enabling multidisciplinary knowledge and removing obstacles to the access of new platforms, technologies, languages and frameworks that were previously out of reach because of time constraints. So, yes, this is exactly what’s happening. The change is noticeable, significant, and should be embraced and utilized to the fullest. Division of labor in the digital world is becoming obsolete: the future belongs to the multidisciplinary, the versatile, the adaptable.
The scent of inevitability.

What I’ll write about

I’m not particularly interested in rehashing common topics like coding practices or highly specialized architectural learnings: the panorama is already well saturated, and after the advent of AI it won’t matter very much. But please, don’t misunderstand me: the main focus of my posts will always still be technical, but, I’ll also try to incorporate genuinely personal and multidisciplinary aspects. Human aspects. Something that AI can’t replicate, can’t imitate, can’t generate. I will write about a journey: the journey of a Man, who slowly discovers how to use the Fire of Prometheus

Titan Prometheus bringing fire
"This place is ours. This place belongs to us, Equality 7-2521, and to no other men on earth. And if we ever surrender it, we shall surrender our life with it also." - Ayn Rand ~ Anthem

I’ll focus on documenting the changes that are happening, starting with my own experience, discoveries, and solutions, from a human technical perspective. The arguments I am going to cover aren’t strictly related to iOS or the Apple ecosystem. I’ve been using Arch Linux and Hyprland for years, and once you try this combination, you can’t go back. Everything else will seem outdated.
I’m already hearing someone saying:

But you’re an iOS developer, you should be using iOS and macOS!!1!

Well, not necessarily. I believe in using the right tool for the job, and sometimes that means stepping outside of the Apple ecosystem. Plus, I enjoy the flexibility, composability, minimalism and control that Arch Linux paired with Hyprland offers.

Extreme productivity and ease of use, tailored to your specific needs, and the feeling of having complete control over the system

And someone else now will surely say:

But for developing iOS apps you should use Xcode and macOS

Well, theoretically yes, but practically no: there could be other ways to do it, without directly relying solely on Xcode and macOS. There are other tools, other approaches, other workflows that could be explored. Open source tools, cross platform solutions, and more. This for sure could be an interesting argument for a future blog post :)

Until next time,