Introduction: What “Dies Only Sometimes” Really Means When Stage 2 began, we asked one question. Why does a program with two threads writing to the same variable die only sometimes? After ...

What this part covers This is the final installment of the series. It bundles two things together. Part 1 — Internals: the mechanism that makes the series’ infrastructure possible. How do two l...

What This Part Covers This part wraps up the entire operational flow that turns a Busan family-home laptop into an unattended 24/7 exit node, all in one go. The work splits into three phases. ...

What this series covers Living in Fukuoka for over a year, the moments when a Korean IP would have been useful kept piling up. Korean payments, banking, and some content services either don’t be...

Introduction: The Copy Cost Left Behind by the Boxing Episode Episode 1 (Value Types vs Reference Types and Boxing) closed with one debt unpaid. “Boxing is avoided, but the copy cost of the ...

Introduction: Why “stack vs heap” keeps misfiring Every C# textbook opens with this sentence: “Value types (structs) are stored on the stack; reference types (classes) are stored on the heap...

Introduction: Same IL, Different Fate The previous two episodes established that the Runtime layer of the .NET stack is divided into multiple implementations. This episode examines those impleme...

Introduction — Was Claude Really Nerfed? Claude Opus 4.6 was widely credited with raising the baseline of coding work by a full step for a period. You could throw an entire codebase at it and it...

Introduction: Why Knowing the History Is Practical This episode answers three questions. Why was “.NET 4” skipped? — Why does the version after .NET Core 3.1 jump to 5 instead of 4? Why wa...

Introduction: The Question of “Who, and How Much” The previous post showed what processes and threads are and how the OS abstracts them. A natural follow-up question arises. If 100 threads a...