2026.08.18

Memory Arenas in Game Code: Fast Scratch Space, Not a General Allocation Strategy

How I use arena allocators for frame-local scratch data, why they beat per-object frees, and why they are not a replacement for pooling or the GC.

2026.08.14

API Programming Through HTTP: The Rules I Lean on in Game Code

A practical guide to calling HTTP APIs from game code without making retries, auth, or failure handling a mess.

2026.08.10

Zero-Allocation LINQ in Unity: Keep the Query Style, Lose the Garbage

A practical look at LINQ in Unity, where the allocations come from, and when a zero-allocation alternative like ZLinq is worth using.

2026.08.06

Native Collections and Burst for GC-Heavy Projects

A practical way to move hot data off the managed heap with NativeArray, NativeList, jobs, and Burst without turning the project into DOTS cosplay.

2026.08.02

Event Buses in Unity Architecture: Keep Systems Talking Without Tight Coupling

A practical way to use event buses in Unity without turning them into hidden global state, leaky subscriptions, or another way to avoid design decisions.

2026.07.29

Hierarchical State Machines in Unity: Keep the Top Level Boring

A practical way to keep Unity state machines readable when several states share the same rules.

2026.07.25

Command Pattern in Games: Queue the Intent, Not the Button

A practical look at the command pattern in game code, with examples for input, undo, replay, and when a direct call is still better.

2026.07.24

Raycasting: How Wolfenstein 3D Fakes 3D With 2D Math

A practical rewrite of Lode's raycasting tutorial, with the same core ideas and images explained in cleaner prose.

2026.07.23

Cancellation Tokens in Unity: Stopping Async Work Before It Outlives the Scene

A practical follow-up to async in Unity: how cancellation tokens keep loading flows, delays, and background work from hanging around after the object is gone.

2026.07.21

Mirror Multiplayer, Part 1: Authority First, RPCs Second

A practical way to structure Mirror games so the server owns the rules, clients send intent, and state sync stays boring.