Why I Am Documenting the Next Seven Years

Most records we keep online are curated for public consumption—curriculum vitae, launch announcements, polished portfolio summaries. They document outcomes, not the friction that preceded them.

This journal is built on a different premise. It is the unvarnished record of the next seven years.

01The Core Intent

When I look back at pivotal decisions made in years past, memory has a tendency to soften the uncertainty. We rationalize our choices after knowing how they turned out. We pretend we had a master strategy when we were merely responding to immediate constraints.

By maintaining this journal, I want to preserve:

1. **The unfiltered context**: What the stakes felt like in the moment before the outcome was known. 2. **Technical & creative convictions**: Why specific architectural, engineering, or design trade-offs were made. 3. **Failures and recalibrations**: The experiments that yielded nothing and the lessons distilled from the rubble.

02Why Plain Text and Decadal Longevity?

Web frameworks come and go. Platforms shut down, databases corrupt, hosting providers change their business models.

For a journal intended to outlive transient technology trends, the medium must be indestructible. Plain Markdown files in a Git repository require no proprietary database to read. Thirty years from now, even if every modern JavaScript framework has vanished, any basic text reader can open these words.

This journal is organized as a knowledge graph. Through backlinks like [[building uniui from a university dorm]], ideas, people, and projects will interlink over time.

Here begins the seven-year chronicle.