Worked walkthroughs

Editorials.

5 worked LeetCode editorials. Each is a chapter-companion: brute force, optimisation, the duplicate-handling trap that catches most submissions, and the four-language reference code. Written in the same voice as the curriculum, with the same widgets that animate the chapter, applied to one problem at full fidelity.

Editorials
5
Signature problems
5
Words
9,413

Part 1 — Linear Data Structures

1 editorial

Part 3 — Pointers, Window, Prefix

3 editorials

Part 9 — Dynamic Programming

1 editorial

What an editorial is

One LeetCode problem, taught at full fidelity. Brute force first, named for what it costs. Then the optimisation, derived from a single sentence about why the inner loop is replaceable. Then the bug that catches most submissions on the hidden tests. Same voice as the curriculum, just zoomed in on one canonical example instead of a family of them.

How to use them

Pick the problem you have not just solved. Read it before opening the LeetCode page. Write the brute force, name its complexity, then ask the follow-up out loud. The editorial format is the order an interview wants you to use; reading them sideways teaches that order without you having to discover it under pressure.

Missing a problem?

Open an issue "Add editorial: LC NNN — title" on GitHub. Editorials earn their place by being canonical: the problem most candidates meet first when they encounter the pattern, with a non-obvious correctness argument or duplicate-handling rule worth slowing down for.