What you will find here
Technical essays, practical notes, interactive experiments, and enough personal context that the whole thing does not feel anonymous or PR-shaped.
About / start here
The plain-language version of this site.
I am Jason. I make software, like small hand-built corners of the internet, and still think a personal site should feel more like a place than a pitch deck. I like curiosity, clean systems, and the kind of humor that keeps technical rooms breathable. This site exists so I can keep experiments, writing, and whatever keeps sticking in my head without flattening everything into one professional sentence.
Orientation language
English and Chinese are available for the quick-start layer on key intro pages. 首页、About 和 Now 这些入门页面提供中英双语的快速说明，站内更深层内容暂时仍以英文为主。
Plain-language version
I build software, explain technical things clearly, and care a lot about making internet spaces feel human. This page is the shortest route if you want the person before the archive.
一句话中文版本
我主要做软件和技术系统，也很在意把复杂的东西讲清楚，同时希望互联网空间依然有人味。 如果你是第一次来，这一页就是最快认识我的入口。
What you probably will not
A content treadmill, fake certainty, or a homepage that assumes every visitor wants the same depth.
How I tend to work
The work itself usually lands in three lanes.
I like technical depth, but I also like making difficult things legible. Most of what I do ends up somewhere between systems, explanation, and direction.
Cloud, deployment, and practical infrastructure.
I am drawn to work where placement, reliability, and operational clarity matter more than shiny abstractions.
Turning technical complexity into something people can actually use.
I like explaining ideas across different levels of depth instead of performing expertise for its own sake.
Helping people get unstuck without making them feel small.
Teaching, guiding, and reducing friction all feel like part of the same craft to me.
Want the collaboration version?
If you care less about biography and more about how I think on a project, the work page is the faster read.
Open how I workWant something playful first?
The lab is the right door if you would rather click around than open a long technical piece immediately.
Open the labWant the deeper writing?
The archive is where the longer thoughts, field notes, and build logs live.
Go to the blog Editorial map
The writing splits into three modes because they come from different moods.
Keeping them separated helps the site stay readable. An essay is not the same thing as a field note, and neither should feel like a changelog.
Essays
Longer arguments about performance, architecture, and product trade-offs.
Field Notes
Operational patterns, lightweight checklists, and lessons from shipping small systems.
Build Notes
Implementation notes about the blog itself and the experiments running behind it.
What I care about here
Three rules quietly shape most of the site.
Readable beats impressive.
If a page needs too much decoding, it is already asking more of the visitor than it should.
Handmade beats generic.
I would rather leave a small specific fingerprint on the site than smooth it into another default tech template.
One site should allow different energies.
Some days I want to publish a technical note. Some days I want a quieter human post. The site should be wide enough for both.
Start with writing
If you do decide to read, start with these.
Teaching changed how I design technical things
Trying to help other people learn made me much less interested in showing off and much more interested in clarity.
I take software seriously, not solemnly
Reliable systems matter more to me than performative seriousness. Humor, calm, and clear thinking can live in the same room.
Why I still like personal sites that feel like rooms
A short note on wanting this corner of the internet to feel more like a place you can step into than a feed you have to keep up with.