In June, I learned how to change diapers and convinced myself that 5 hours of sleep is a luxury. Somewhere in between, I also shipped iOS for Kombine — which was absolutely not on the roadmap. The roadmap said Android → Backend → Webapp → iOS sometime later. It was a good plan, and that’s exactly the kind of plan a pet project doesn’t have to follow.

I find myself with a fresh golden hammer in hand every now and then, only to realize a screw would’ve been better. Following principles blindly doesn’t automatically render ‘better code’—there are always tradeoffs, and managing them is a sign of seniority and actual craftsmanship.

A chance encounter at the airport leads to insights into the real nature of technical debt in software development. Through the lens of Stoic philosophy and Lord of the Rings metaphors, this post explores how better communication between engineers and management can prevent our own Mines of Moria situations. Practical tips included for both technical leads and managers on how to discuss, document, and decide which technical dragons are worth slaying.

I had several chances to try a few ways of multiplatform software development. However, I was curious about the Kotlin Compose Multiplatform way. So I could use the technology I already know to build Android, desktop, and iOS apps, sharing internal logic, and UI elements. How hard can it be?

‘I did not study computer science to work with people’—sounds familiar? Well, I’ve got news for you: you’re still working with people, you just communicate not in the way you might think. Your code speaks volumes about your intentions and ideas. Design Patterns can amplify your coding ‘voice’ when used wisely.

Have you ever thought that your project needs to be rewritten completely from scratch? I share a story of a mobile app rewrite, that didn’t went well on few levels, and it got me thinking how other companies approach this topic. And why you shouldn’t think about it, there are other ways to address the issues.

I recently made observations on my limitations due to my ‘develper dependencies’. Anything outside my comfort zone feels bad, and I don’t like that. My plan is to create a developers survival kit and stick to it. Reducing dependencies and distractions, focusing on craft.