Simplify. Optimize. Control.

Over the years, these three ideas have gradually become my default way of building things.

They are not rules. More like biases.

Simplify

Complexity is easy to add and hard to remove.

I prefer systems with fewer moving parts, fewer unnecessary abstractions and fewer dependencies.

If two approaches solve the same problem, I will usually choose the one that is easier to understand, operate and change.

Simple does not mean simplistic.

It means keeping only the complexity the problem actually needs.

I enjoy making things work better.

Sometimes that means performance: less latency, less memory, fewer resources.

Sometimes it means less code, less manual work, fewer steps or a better structure.

Optimization is not about chasing benchmarks for their own sake.

It is about removing waste.

I like understanding the systems I depend on.

What runs.
Where the data lives.
What the real dependencies are.
What happens when something fails.

That naturally draws me toward transparent tools, understandable infrastructure, self-hosting when it makes sense and fewer black boxes.

Control is not about doing everything yourself.

It is about knowing what you depend on and being able to make deliberate choices.

Build something first.
A working system teaches more than endless planning.

Consistency beats intensity.
Good systems — and good work — are built over time.

Explain it.
If something cannot be explained clearly, it is probably not understood well enough.

Break the rules when it makes sense.
Rules are useful until they stop serving the problem.

Share what you learn.
Knowledge becomes more useful when it circulates.

Knowledge is multiplied when shared.