Why this site is organized by project
Designer, developer, writer, and product owner used to be separate jobs. This site is built around projects instead of job titles, and every post belongs to the work it documents.
AI erased a lot of the line between designing something and building it. The question used to be which job you had. Now it’s which problem you’re solving, and how much of it you can carry yourself.
So this site is organized around projects, not roles. Each project gets a page with the problem it solves, a status that shows where it stands, and a build log underneath. Every log entry belongs to exactly one project, so you can read any project from its first idea to wherever it is today.
A few rules I set for myself:
- Status is always visible. Idea, building, shipped, or paused. If something stalls, the page says so.
- Writing and video are two forms of one post. When a video goes up, its written version lives here. At least that’s the goal. Video production takes a long time. I want move fast and still document my process.
- Reviews get a design read. When I review a product, I end with why its design works the way it does.