Understand what existsExplore what's possibleBuild something real
Each project started as a question I could not answer by reading. Open a folder: every page inside says what the problem was, what I contributed, what runs today — and what is still missing.
It is one loop, not three steps. Building is what teaches me the thing I had not understood yet, so the loop runs again with a better question.
Why does this problem exist, how does the system actually work, what explains the decision? I do not start building until I can explain the mechanism out loud.
I try the idea in the smallest form that is still able to be wrong. Exploring is not a detour on the way to the plan — it is how I find out which possibility deserves the next two weeks.
Ship the thing you can open, use and break. A rough version that exists tells me more in a day than a specification that is still theoretically correct.
I like taking a complex problem apart, understanding how its pieces interact, and building the solution one layer at a time. Prometheus is that habit made visible: recognising techniques in a fight, understanding how they chain into sequences, and reading the decisions a fighter makes on top of that.
Being driven, for me, means building: try the idea, ship a first version, put it in front of real use, improve it. Exploration is part of that process rather than a detour — it is how I find possibilities I had not considered, and how I work out which ones deserve the next two weeks.
I use AI tools to research, design, develop and create. I care about results that are visible and testable, and I move through attempts, feedback and adjustment — with attention to the small details that decide whether a product is understandable and pleasant to use.
Video editing, 3D, camera movement, rhythm, writing, poetry and painting shape the way I look at things. So I think about how to make an idea land — and about the curiosity and the emotion it can set off, not only the information it carries.
Curiosity is the engine. Why a problem exists, how a system holds together, what explains a decision, what makes one experience interesting and another forgettable — that is what decides which projects I start and which ones I drop.
I care about the whole product — how it works, how it is presented, how it feels to use, and how it finds the people it is for. Not one layer of it.
I am most useful where a product has to be understood, prototyped and shipped by the same person.