Posthog's code review tips: 30 lines or less

PostHog published a practical list of code review tips — the kind you actually use instead of the ones you pretend to read. The gist: keep PRs under 300 lines, write the commit message before the code, and call out risky changes explicitly. It's a reference sheet, not a manifesto.

The ones worth remembering are the boring ones. A clear title and description save more time than any linter. Reviewer comments should be actionable — not "this looks off" but "this function touches the DB in a loop". And if you're the one writing the PR, resist the urge to defend the code in the thread; just fix what the reviewer asks for and push again.

Why this matters for us: it's the kind of discipline that keeps small teams from drowning in bloat — and the kind you can steal from anyone, no Silicon Valley gloss required.