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.

Most software teams are split up by technical layers—backend, frontend, and mobile. This seems logical, but it often creates bottlenecks, delays, and frustration. Mission teams flip the script: cross-functional developers own features end to end, from idea to release. This approach speeds up delivery, builds real ownership, and cuts down on endless handoffs. Too perfect to be true? It demands more upfront effort in communication and shared knowledge, but the payoff is worth it.

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.

I went to a meetup in my city last week and a guy I just met there popped a question after a while of conversation: with my experience, would I go for mobile software development again or pick a different area?