About Bohdan
I'm a CTO with more than 10 years in software development. I started out as a developer at an early-stage startup, the kind of place where one person writes the code, sets up the servers, and answers the first support emails when something breaks at 2am. From there I moved through product companies, outsourcing agencies, and large enterprise projects. Each one came with its own rules, but they all taught me the same lesson: behind every technical decision there's a real cost the business ends up carrying.
These days I lead engineering teams and own the technical direction of the products I work on. That means architecture and code reviews, but it also means budgets, hiring, and sitting in rooms where the technical answer and the business answer don't line up. I've learned to translate between those two worlds, and that's honestly the part of the job I enjoy most.
What sets me apart from a lot of technical leaders is that I don't treat engineering and business as separate problems. Code written without a clear reason behind it becomes a liability. A business decision made without technical context turns into an expensive surprise a few months later. I try to hold both at once, whether I'm choosing a tech stack, deciding what to do about technical debt, or explaining a tradeoff to a CEO who has never written a line of code.
Over the years I've built three products from scratch and helped scale systems that serve real users every day. I care about clean architecture, but I care more about whether the thing actually ships and works. On this blog I share what I've learned along the way, the honest version, mistakes included.
