Leads a team of three on a release tool for small teams. Merge-to-production went from forty minutes to eighteen.
正在加载页面 · Loading page
正在加载页面 · Loading page
Full-stack engineer · Shenzhen
Inventory tools for three shops, a request line for a campus radio, a refund path that could not be late. Now leading three people on a release tool. Below is what each of them changed.
By the numbers
These figures come from release logs and the ticket system. If a log does not show it, it is not here.
Each of the six rollbacks has a write-up, so that no mistake happens twice.
5
Companies
Experience
31
Features shipped
Changelog
4k
Daily users, latest product
Own analytics
92%
Test coverage on the critical path
CI report
18
Minutes from merge to production
Pipeline median
3
Open-source packages
npm
Experience
Most recent first. Each opens to what was actually done there.
Leads a team of three on a release tool for small teams. Merge-to-production went from forty minutes to eighteen.
Owned the refund and reconciliation path. Nineteen months, zero money incidents.
The only engineer in an eight-person design studio. Eleven client sites shipped in fourteen months.
Built the request system and the live page for the campus station. Two thousand concurrent listeners at peak, and it never went down.
Small stock and order tools for three small shops. All still in use.
Work
Three tools built on weekends, all still in use. Each has a page of its own.
Release tool · 2025
A release tool for small teams: one command from merge to production, with every step visible and re-runnable.
View project →
Command line · 2024
A plain-text ledger. The book is one file, lives happily in version control, and will still open in ten years.
View project →
Web app · 2023
A focus timer with one ring and one button. Built to learn how not to add features.
View project →
Weekends
Hills, sea, a city and a road, all of them places I have walked.