Clean Architecture: Stories of Pain and Joy From the Codebase [ukr]
Imagine you decide to save an old, worn-out ship by replacing its engines with the most advanced ones. But instead of “sailing into a bright future,” it starts sinking even faster.
This is a story about how Clean Architecture can become either a life buoy or a stone tied to a project’s neck.
The first part is a chronicle of pain: the attempt to bring architectural elegance into the chaos of legacy code, where even successes felt accidental — and why “We’re just doing Clean Architecture” doesn’t always work.
The second part is a story of “triumph”: when a mature team and the right approach turned Clean Architecture into the foundation of a scalable, flexible, and truly alive system.
Two stories from real practice that show why the same approach can both sink a project and save it.

- 14 years in software development. Held roles as R&D Tech Lead and Competence Development Lead
- Contributed to the development of various types of applications on the .NET platform – Web, Desktop, and some Mobile. Worked on building a Low-code ETL platform
- Doesn’t engage in debates about monoliths vs. microservices — it’s just not worth it
- Mentor and trainer of educational courses in Python at Sigma Software University. Lecturer of the Python Intensive course for the IT Generation project by the Ministry of Digital Transformation in partnership with the Binance blockchain ecosystem and the Lviv IT Cluster
- Participant in charitable initiatives with Star For Life Ukraine.