Hello, world
Who I am, why this blog exists, and what I plan to write about here.
3 min read
I am Jason Yang, an engineering manager at Frontify in Switzerland. My team owns the media delivery path end to end: the engine that processes and serves every image and video for our customers, and the Kubernetes infrastructure and CDN caching it runs on. The mission we set ourselves is media processing and delivery that absorbs any customer’s spike without ever slowing another customer, at a cost we are proud of. I still design, review and ship code. That is a choice, not an accident.
Before Frontify I was co-founder and CTO of ImpactNexus in Berlin, an early engineer at Leapsome, and a backend engineer at Grab in Singapore, after starting out at two large internet companies in China where a hundred million users on one product is normal. The longer version, including the PHP profiler I ported to PHP 7 and why I still reach for gdb, is on the About page.
The thread through all of it is the same. I like building high-performing teams that build high-performing systems: teams where the path from a merged pull request to production is short, safe and boring, where the four DORA metrics are numbers people actually look at, and where knowledge lives in documents and paved paths rather than in one person’s head. Developer experience is not a nice-to-have in that picture. It is the mechanism. A good part of my job is explaining complex systems to founders, customers and people who do not build systems for a living, and I think being able to do that is part of what makes a good engineer.
Most of my working days end with a small pile of things I figured out: a flaky rollout that turned out to be a config default, a caching layer we decided not to build, an autoscaler that scaled at the wrong moment, a migration that went sideways for a reason nobody had written down. Almost all of that knowledge evaporates within a month. This blog is my attempt to stop the evaporation.
Writing a problem down forces me to state what I actually knew at the time, what I tried, and why the final decision looked reasonable. If it also helps someone who searches for the same error message at two in the morning, even better.
The topics will follow what I am working on, which right now means:
- Kubernetes platform work. GitOps, Helm, autoscaling, and progressive rollouts.
- Delivery discipline and developer experience. CI gates, preview environments for unmerged code, staged rollouts, DORA metrics, and what it takes to build a paved path a team trusts.
- Media and CDN infrastructure. Caching, media processing pipelines, and the cost and latency tradeoffs of serving a lot of traffic.
- Observability. OpenTelemetry, and getting to SLOs that a team actually looks at.
- Engineering management. Growing engineers, running a team through change, working with platform and infrastructure partners, and deciding what not to build.
- AI-assisted engineering. Where it speeds us up, where it does not, and what changes about code review when the diff was not typed by a person.
Expect mostly short posts, each about a concrete problem: the context, what I tried, what worked, and what I would do differently. Occasionally I will write something longer when a topic deserves it. Everything here is my own opinion, not my employer’s.
Posts are tagged and there is an RSS feed. If you spot a mistake or want to argue about a tradeoff, please get in touch. That is half the point.