I am rebuilding my public home at jasonyu.dev.
For much of my career, the value I created lived inside companies: production systems, internal tools, delivery processes, and team knowledge. That work mattered, but it did not compound into assets I owned: public writing, reusable tools, small products, or a visible body of work.
I want to change that.
This site is where I want to make my work more visible, more reusable, and easier to reason about over time. Not by publishing polished essays from day one, and not by pretending every note is a finished opinion. The goal is simpler: write clearly, ship small things, and keep a trace of what I am learning and building.
Why This Site Exists
jasonyu.dev is meant to be a clear public surface for my work.
I want one place that can answer a few simple questions: what am I building, what kinds of problems do I care about, how do I think through engineering tradeoffs, and what am I learning as I work with software, tools, and small products.
That does not require a large site. It requires a site that is honest, current, and maintained.
What This Site Is For
I expect this site to focus on a few themes.
The first is software engineering in practice: backend systems, developer tooling, automation, operational habits, and the small technical decisions that make a system easier or harder to live with.
The second is AI-assisted development. I am interested less in vague productivity claims and more in the actual workflow: how agents fit into existing codebases, where they help, where they fail, and what kind of structure makes them more useful.
The third is local-first tools and personal infrastructure. I care about tools that stay close to the user, respect the working environment, and make daily engineering work more direct.
The fourth is small product experiments. I want to build more in public, even when the first version is narrow. A useful tool does not need to begin as a company. It can begin as a clear problem, a small interface, and a working loop.
What I Want To Build In Public
I want this site to make small projects easier to follow.
Some projects may become developer tools. Some may stay as experiments. Some may simply document a workflow that became useful enough to share. The important part is to keep the connection between the writing and the work.
When I write about a tool, I want to show the problem it solves, the constraints behind it, and the tradeoffs I made. When I write about a system, I want to preserve the operational details that usually disappear from polished summaries. When I write about AI-assisted development, I want to focus on the working loop: prompts, code review, verification, boundaries, and the places where human judgment still matters.
That is the kind of public record I want here: practical enough to be useful, specific enough to be trusted, and small enough to keep shipping.
How I Want To Write
I want the writing here to stay close to real work.
A useful post should preserve the context behind a decision: the problem, the constraints, the tradeoff, the result, and what I would watch for next. Some posts will be short technical notes. Some will be debugging stories, architecture decisions, product experiments, or reflections on tools I am building.
The standard is simple: clear enough to be useful, specific enough to be trusted, and honest about what is still uncertain.
Starting From Here
The first step is to keep the site simple and real.
From there, the plan is simple: ship small, write clearly, and let the site grow through real work.
jasonyu.dev starts here.