Why Build?
The case for building things in a world that seems content to consume.
There's a question that keeps surfacing in my mind, in conversations, in the quiet hours between finishing one thing and starting the next:
Why build?
Not why build this particular thing, but why build at all. In a world overflowing with content, with products, with noise -- what's the case for adding more?
The world we inherit vs. the world we make
We're all born into a world we didn't choose. The structures, the systems, the stories that define what's possible -- they were here before us. But that doesn't mean they're the only options.
Building is the act of proposing an alternative. Every essay is a new way of seeing. Every piece of software is a new way of doing. Every song is a new way of feeling.
Building as thinking
I don't build to have built. I build to think. The act of making something forces clarity. You can't be vague when the compiler is watching. You can't hand-wave when the sentence needs to land.
Writing is thinking made visible. Code is logic made executable. Music is emotion made audible.
The homestead
That's why this place exists. Not as a portfolio -- a trophy case of finished things -- but as a living workshop. A homestead where ideas are planted, tended, and sometimes harvested.
Some things here will be seeds forever. That's fine. The point isn't completion. The point is cultivation.