Writing

Technical battles are favorite approach how to talk about technologies for many software engineers, who are often “geeks”. It may happen on any level: hardware, operating systems, window managers, distributions, IDEs and text editors and of course - software technical stack. There is nothing wrong to discuss, disagree and prove your own point. The problem starts when rationality is replaced with beliefs. The perfect stack does not exist. Each and every decision is a trade-off: solving one probl

Building solo gives us complete freedom. Including freedom of choosing technologies. How to make best decision and choosing wisely - avoiding mistakes, keep the journey interesting and still deliver? In this article I will share my point of view on the technological aspects of solo building and share my perspective of making a choice. I will start with common advices, the ones you have most probably heard already. First of all: trendy, bleeding edge and hyped technologies are not meant for solo

“Trust me, I’m an engineer!” - this was used to be my favorite joke years ago. When I was following my gut feeling and people around me were in doubt. Later I started to notice people are doubting less. Maybe not really, but I was caring much less. This was directly related to my professional growth and complexity of the problems I was confidently solving. Analyzing detail, noting weak points and identifying missing information became my daily drivers. Everything requires structure, everything

Wandering around social medias I found myself in the buble of engineers, vibe-coders and many others who’s been sharing their positive experience with the latest AI models. I joined that voice, because upgrade to Claude Max last weak made me done so many great things within a week. Despite I got sick I can’t resist and use agents to do the coding part. With Claude Max plan I’m using Claude Code with Opus 4.5 and it works great. And now, when it can write quite a good code, only sometimes making

Early in my carrier I was trying to do as much as possible in a shorter period of time. It is a common pitfall for engineers and non-engineers. But the more complex is the mechanism and tools we need to work with the bigger is the impact of negative context switching. At the end of the day it’s exhaustion, not productivity. Human brain is single-threaded. We can’t process multiple ideas in our conscious mind at the same time. Moreover it is not enough to process just the idea. We must “load” in