Learning by building
The fastest path to real understanding is making things that have to work. Even a small experiment should expose design trade-offs, failure modes, and next questions.
The trunk.
The trunk is the part that stays stable while projects, tools, and interests evolve. It explains how I learn, how I build, and how I turn work into reusable assets.
Trunk ├── How I think ├── Learning by building ├── From fundamentals to systems ├── Building public knowledge assets └── Connecting theory to shipped work
From fundamentals to systems
I want the site to connect foundations like math, physics, computer science, and electronics to applied work like games, AI infrastructure, and product engineering.
Public knowledge assets
Every useful outcome should leave behind something durable: a repo, article, template, diagram, demo, devlog, or case study.
Compounding credibility
The point is not to collect random projects. The point is to build a connected body of work where each branch strengthens the next leaf.
Simple explanation: the trunk is how I work. The branches are the capabilities and foundations I keep developing. The leaves are the artifacts I actually ship.
Why the tree analogy matters
Foundations are reusable
A concept like waves or vectors should be explained once at the foundation layer, then reused across games, electronics, AI infrastructure, and systems.
Applied work stays connected
Game development, embedded interfaces, homelab systems, and production AI no longer look scattered. They become applications growing from shared roots and branches.