I build backends in Ruby and Elixir, combining engineering thinking with design principles — from an idea and a prototype to a working system.
What draws me is not so much the code itself as what can be made from it.
I am interested in how a few simple rules — if, for, functions, data structures — gradually give rise to systems with behavior that none of the elements has on its own. From simple building blocks you can assemble an operating system, a neural network, or an application.
What draws me especially is the moment these elements start to interact and something new appears: a property, a behavior, or a whole system that can no longer be understood by looking at its parts separately.
So it matters to me not only to build a working system, but to understand where its behavior comes from. What in it is truly necessary? What simple ideas lie at its foundation? Which connections produce what we observe?
Peter Naur’s idea of programming as theory building feels close to this. For him, programming is above all the making of knowledge about how a system is put together and why it works the way it does. Code becomes an expression of that knowledge, not an end in itself.
Which is probably why I see development as an act of making, rather than as the production of code.
I am interested in the moment an idea becomes a system — and the system begins to do what none of its elements did on its own.
In the end, what interests me is not how much code I have written, but which idea it managed to express.