About CoderBlog — A Working Engineer's Journal

CoderBlog is a one-person engineering journal, written and maintained by Winson Yau from Hong Kong. New articles go out weekly, occasionally twice a week when something interesting ships. The cadence is irregular on purpose — I write when I have something to say, not to feed an algorithm.

What this is

This is a personal site for working engineers. Articles are deep, code-heavy, and grounded in production experience. When a benchmark is cited, the methodology is shown. When a library is recommended, the failure modes are discussed alongside the wins. When a model is compared, the price is shown next to the score.

What this is not

This is not a tutorial site. It is not a news outlet. It is not a content marketing funnel for some SaaS product. The closest spiritual relative is the personal blog of a senior developer who has stopped trying to impress anyone and started trying to be useful.

What we cover

• ASP.NET — .NET, C#, Blazor, EF Core, and the Microsoft stack, with a focus on production engineering rather than framework tours.
• Flutter — cross-platform mobile, Dart, widget design, performance, and shipping apps that survive real users.
• AI Tech — LLMs, agents, MCP, RAG, fine-tuning, and the new shape of software work in 2026.
• Hosting — cloud, Docker, CI/CD, edge, static sites, and the actual cost of running things in production.

Editorial principles

Every article is written from direct experience, not from marketing material. Code blocks are real and runnable. Benchmarks are reproducible. Conclusions are qualified. If I get something wrong, I will say so at the top of the article rather than quietly editing it out — the contact page is the fastest way to flag a correction.

Stack behind the site

The blog itself is a static site generated with Statiq and .NET 9, served from a small VPS in Hong Kong, fronted by Caddy as the reverse proxy. Comments run on a self-hosted Waline instance. No JavaScript framework, no React, no hydration, no CDN between the user and the bytes on disk. Source for the build pipeline is on GitHub.

A small request

If an article helps you ship something or saves you a week of debugging, the most useful thing you can do is forward it to one engineer who would also find it useful. That is the entire growth strategy. There is no email list to sign up for, no popup, no paywall. Just the articles, the RSS feed, and the search box.