What we write about, and why

Four areas. Each one chosen because the existing discourse around it tends to be surface-level, and mechanical depth helps.

Patch reading

What changes in a patch actually mean — which adjustments have compounding effects, which are isolated.

Cycle timing

When dominant strategies become widely known, they start to generate counter-strategies. Tracking that cycle.

Bracket divergence

Why the same patch creates different metas at different skill levels — and how information filters through the playerbase.

System interactions

How game systems interact — cooldowns, hitboxes, animation windows, damage falloff, ability ranges.

Skill expression surfaces

Where different game formats create space for skill to matter — and where they constrain it.

Efficiency ceilings

The theoretical maximum performance for a given playstyle — and how close high-level play gets to that ceiling.

Economy and tempo

How resources — gold, health, cooldowns, positioning — accumulate and get spent across a match.

Spatial reasoning

Zone control, positioning trade-offs, the geometry of denial and access across different map formats.

Decision prioritization

When to take a fight, when to concede, how to evaluate whether a trade is worth it — across different game states.

Cognitive load management

How attention works under pressure — and how practice structure can reduce the gap between training and match performance.

Feedback interpretation

How to read your own performance accurately — which signals are informative and which are noise.

Improvement rate vs plateau

Why improvement isn't linear, and what distinguishes periods of plateau from genuine skill ceilings.


Out of scope, intentionally

Tier lists require constant maintenance, favor recency over understanding, and are widely available elsewhere. We'll reference tier context when it helps explain something mechanically, but producing them isn't what this site is for.
There are well-resourced teams publishing patch notes summaries within hours of release. We're not competing on speed. When we cover a patch, it's because there's something in it worth analyzing slowly.
Equipment affects performance at margins that rarely matter below a fairly high skill level. It's also a category that lends itself to affiliate arrangements, which we'd rather avoid.
Pro scene journalism requires access and relationships we don't have. We'll use pro play as evidence when it illustrates a principle, but covering the scene as news isn't in scope.