Beyond engineering, I’ve always gravitated toward creative disciplines. Art has long been a parallel interest in my life, one of those things that becomes part of you and cannot be separated. At first glance, it may seem like a completely different world from software, yet it has shaped how I think about structure, growth, and intention. Art is inherently abstract, and so is software. At its core, it is about creativity. It becomes particularly important in projects without established patterns or prior solutions.

Creativity serves as a reliable engine for me.

This is not an original idea, but I’ve come to see two complementary mindsets that shape how people approach engineering.

One sees the system as something that grows — an evolving structure that gradually gains coherence, internal logic, and character. It requires care, consistency, and long-term thinking.

This perspective can sometimes feel almost parental — as if the system were something being raised rather than merely built.

At first, this was something I had only encountered in theory. Over time, I began to recognize it in practice, and it has since proven itself to be real.

Whether that instinct feels more maternal or paternal is ultimately irrelevant. Both can be equally strong. Similar patterns can be observed across many disciplines where people create something complex over a long period of time. A certain sense of ownership begins to emerge — almost a parental stance toward what is being built.

In some cases, this can even extend to a need to protect and care for that “creation” (which, at times, can become a limitation — making it harder to maintain objectivity when guiding its evolution).

The other approaches it as a sequence of constrained problems — a mindset driven by the urge to confront and ultimately overcome challenges. It reflects a more archetypically masculine mode of engagement: direct, confrontational, and oriented toward resolution. This is not limited to men, and can be expressed by anyone, especially in a modern context.

At times, it can feel almost like a duel with complexity, where each obstacle stands in the way and must be dealt with. It can even take the form of an ongoing confrontation — moving from one problem to the next, resolving each in turn.

Each obstacle must be understood, reduced, and resolved. Precision matters. One wrong assumption can cascade.

It is not a fight for survival, but the tension is real, and anyone who has worked through complex systems has felt it, at least at times.

I recognize strong influences of both in myself.

This duality is not accidental.

Architecture — in the physical sense — was a recurring theme in my family environment. Large structures demand correct foundations, thoughtful load distribution, and patience. They evolve gradually, and their integrity must be maintained throughout. Scale does not forgive improvisation. Much of this carries over to distributed systems.

As a child, I admired some of the greatest inventors in history. I played with discarded machines and tried to build some of my own. This eventually led me to pursue mechanical engineering in school. Building physical machines is unforgiving: material limits, manufacturing constraints, irreversibility. Later on, after a few formative milestones, discovering software felt like stepping into Alice in Wonderland. It revealed an entirely different kind of leverage. Code allows immensely complex mechanisms to come to life, to be reshaped and evolved with comparatively lightweight tools — yet the structural responsibility remains just as real, if not greater.

There is also the layer of pure logic. I was never a professional, but I played chess seriously for many years. Over time, I became a strong player, occasionally challenging club-level opponents and making them genuinely uncomfortable.

A long game requires sustained concentration, positional thinking, and respect for compounding consequences. Large-scale systems feel similar. You move from one constraint to another, building a position that must hold under pressure.

It is the combination of these influences — creativity, structural awareness, engineering discipline, and strategic thinking — that allows me to remain grounded in large, complex projects.

I do not see software as just implementation.

I see it as something that is designed, constructed, and gradually brought into structural integrity. It takes time and effort to do it well.

System engineering leaves little room for complacency.

Without a certain degree of internal drive and emotional investment, truly excellent systems are rarely created.