Software Design

At the very beginning, I viewed programming as the act of making things work. Nowadays, it's an integral part of me as an engineer.

Usually, when anybody asks me what kind of "programmer" I am, I always answer that I'm a "software design" kind of guy. It's something I always reflect on and try to get better at. My interest comes from the intolerance for ambiguity.

The biggest shift for me over the years is that I don't consider a codebase to be just a set of instructions anymore. My goal is to move away from implicit assumptions or "gut" feelings towards stable and logical rules (what I think of as mathematical guarantees for the system).

Main motivation for writing notes about Software Design is almost always rather personal — I get better at something when I'm trying to explain that "something".

You can find my notes related to the "Software Design" in "Linked mentions" below.