Documenting my indie development journey and related experience. Honestly - it could be anything, but I do my best to keep it more indie development business oriented.
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
I was afraid even about thinking of starting an independent solo journey years ago. However, the amount of frustration that I have accumulated for pure leadership, dirty managers games and simple lies and
“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
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
Starting a solo journey requires adjustment of the tooling to the current needs. High availability and the degree of how “cool” software is does not matter anymore. Today I am sharing my way to get aware of what's going on with the traffic and uptime at (almost) no costs!
