D / DEVELOPER
Full Stack & Systems Developer
Nine years of building things to understand them — from first curiosity to distributed products, open-source tools, and the people behind them.
Not to get a job. Not because a course told me to. Because I kept wondering how things worked and could not stop making things to find out.
Nine years later the habit is still intact. The tools changed. The curiosity did not.
A progressive trajectory across procedural scripting, C++ low-level storage engines, object-oriented Java runtimes, hackathon embedded firmware, production full-stack systems, and open-source tooling.
I notice how good games teach without manuals: feedback, pacing, readable state, and progressive complexity. That lens carries into interfaces and tools.
complex rules, limited attention, fast feedback
“teach by state, not by explanation”
developer tools with visible progress, clear affordances, and low-friction recovery paths
The part that stayed consistent is simple: make the smallest useful thing, put it in public, then improve the experience deliberately.
Dive into full architecture case studies, browse system capabilities, or start a conversation.