What kind of content and writing style does Win Tech Blog use?

Win Tech Blog publishes short, hands-on engineering notes: "Today I Learned" (TIL) posts, debugging write-ups, and concept explainers drawn from the author's own work. The writing is practical rather than tutorial-formal — it usually starts from a specific problem, error, or question and works toward what was learned. Content is mostly in English, with some posts in Burmese, and topics skew toward Linux, operating systems, databases, and web development.

Content formats

The blog relies on a few recurring formats rather than long-form guides:

• TIL notes — a single problem and its resolution. The clearest example is the post on why unshare --pid throws a "fatal library error, lookup self," which ties the error to the proc file system and the unshare command.
• Debugging logs — posts such as "Debugging SQL Fanouts," which examines join fanout behavior in SQL.
• Concept explainers — for instance, a piece on how the JavaScript event loop and its task queue work, aimed at making asynchronous code easier to reason about.
• Explanatory series — a set of Linux process and memory management notes ("How Linux Processes were created," "Linux Process & Memory Management Notes").
• Practical fixes — "Reclaiming 160 GB from WSL2's Hidden Disk File," which notes that deleting files inside WSL2 doesn't shrink Windows disk usage and that one PowerShell command addresses it.
• Occasional non-technical posts — a personal account of an immigration college experience, filed under Life/Canada.

Writing style

The style is first-person and experience-driven. Posts are framed as something the author encountered and worked through, which is why titles often read like a discovery ("Today I Learned…") rather than a syllabus. Explanations assume a working developer but not a specialist: the cloud networking post states explicitly that it targets software engineers, noting the material is easy for networking experts but often hard for engineers whose organizations leave that work to DevOps or cloud engineers.

Two language tracks coexist. Technical posts are generally in English; some posts, including the cloud networking piece and the JavaScript event loop piece, are written in Burmese. A reader who only reads English will still find most of the technical archive accessible, but not all of it.

Topics covered

Who it's for

This is a working notebook, not a structured course. It suits developers who want a quick account of a specific error or mechanism — especially Linux, process, and SQL topics — and who are comfortable with posts that assume context instead of building it from scratch. If you need sequential, beginner-oriented tutorials, the format here will feel fragmented; if you want to see how someone else diagnosed a concrete problem, it's a good fit. Expect uneven coverage across topics and a mix of English and Burmese depending on the post.