Hi, I’m Dmytro.

I have always been fascinated by systems.

By the way many separate pieces, layers, rules, and interactions can come together and produce something that works as a whole.

Almost everything can be viewed as a system.

A living organism is a system of organs, cells, chemical processes, and signals. An ecosystem is a system of organisms interacting with one another and with their environment. A society is made of people, institutions, incentives, laws, cultures, and economies. Even the universe itself can be understood through systems acting at different scales.

And when you zoom in, the pattern repeats.

Every entity becomes another system made of smaller components, governed by its own rules. Zoom out, and it becomes one component inside something larger.

I find that endlessly fascinating.

But there is an important difference between many of these systems and the ones I am most interested in understanding and building.

Most natural systems were not designed.

Nobody sat down and architected an ecosystem. Nobody wrote a specification for a living organism. Societies, markets, and cultures were not created according to one coherent plan.

They evolved.

What exists today is the result of countless interactions, adaptations, accidents, failures, and selections over time. In many cases, things exist simply because the alternatives did not survive.

Modern technology is different.

The Internet, communication protocols, power grids, operating systems, distributed systems, computers, and countless other technologies are products of human thought and engineering.

Someone had to decide how the pieces should interact.

Someone had to define the boundaries.

Someone had to choose the abstractions.

Someone had to think about failures, trade-offs, scale, security, reliability, and all the strange situations that appear when thousands or millions of individual components have to behave like one system.

That fascinates me.

I am a software engineer, but software itself is only one layer of what interests me.

I want to understand how complex engineered systems work across boundaries: software, networks, protocols, infrastructure, devices, physical processes, and the people operating them.

And the best way I have found to understand a system is to try to rebuild it.

Not because I expect my version to be better.

Usually it will be dramatically worse.

But rebuilding forces me to leave the comfortable surface of an abstraction and discover what actually makes it work.

That is how I ended up rebuilding a web server, cryptography, and TLS from scratch.

It is also how I became interested in the electrical grid, not simply as an energy topic, but as an enormous engineered system where physics, infrastructure, control, communication, markets, regulation, and software all have to work together continuously.

The scale is different.

The curiosity is the same.

This publication is where I explore those systems.

Sometimes I take a technology apart and rebuild a simplified version.

Sometimes I trace a system through its layers to understand how the pieces connect.

Sometimes I go deep into one protocol, mechanism, or engineering decision.

And increasingly, I want to build systems that cross several of those boundaries myself: software connected to networks, devices, infrastructure, and the physical world, especially where reliability and security genuinely matter.

I don’t expect to understand everything.

That is rather the point.

There will always be another layer underneath.

And that is what keeps me building.

Professionally, I’m a software engineer working in the energy sector, building software for critical infrastructure. Outside work, I keep following my curiosity wherever complex systems lead me.

This publication is a record of that journey and a place where I think, learn, and build in public.

If that sounds interesting, welcome aboard.

Let’s rebuild some systems together.

Dmytro Huz
Software Engineer · Complex Systems · Energy
dmyhuz@gmail.com