Building things.
Following curiosity.
Leaving a trail.

I want to get better at letting the awkward first attempts exist. The first photograph, the first paragraph, the first implementation: they are evidence of contact with the thing, not evidence that I should stop. A useful practice is small enough to repeat and honest enough to show me what I do not yet understand.

Software teaches me to make systems explicit. Photography teaches me to notice what is already there. Music teaches timing; writing helps me discover what I think. These interests do not need to become one personal brand story. They can simply make me more observant, more capable, and more alive to the world around me.

After learning something new, make a smaller version without following the original steps. Write down what is confusing, look it up, then try again. The point is not to avoid tools or documentation. It is to make sure they support your understanding rather than quietly replace it.

Not every experiment needs to become content. Some things can be made privately until they are ready; others can be shared because the act of explaining them helps. The measure is whether publishing serves the work, the reader, or the connection between us—not whether the process looks impressive from the outside.

We spent a decade flattening interfaces into interchangeable utility. But the web can feel like good stationery—warm paper, considered margins, ink that settles into the fibers. Taste is not ornament; it is the discipline of making something feel human and durable in an era of relentless algorithmic sameness.

Complexity in tooling often disguises procrastination. When beginning a new exploration—whether an EVM contract, a Next.js experiment, or an ambient chord progression—start with the simplest primitive that works. You can always add scaffolding later, but momentum lost to configuration rarely returns.