T

Rodin 9961f939c5 docs: pattern purity and codebase evolution analysis

How pure are these codebases? When do they break their own
conventions and why? Key finding: purity inversely correlates
with size. Ecto has 0 TODOs; CockroachDB has 1,048.
Neither is wrong — they're different kinds of systems.

2026-04-30 10:56:15 -07:00

analysis

docs: pattern purity and codebase evolution analysis

2026-04-30 10:56:15 -07:00

elixir

docs: Elixir patterns vs official guidelines with code examples + hypotheses

2026-04-30 07:58:31 -07:00

docs: enhance Go divergence analysis with code examples + hypotheses

2026-04-30 07:57:37 -07:00

README.md

docs: Go patterns vs official guidelines divergence analysis

2026-04-30 07:50:32 -07:00

README.md

Patterns vs Official Guidelines

Divergence analyses comparing our extracted-from-source patterns against official coding guidelines.

Reports

Ecosystem	Our Patterns	Official Guidelines	Report
Go	rodin/go-patterns	Effective Go, Code Review Comments, Google Style	go/
Elixir	rodin/elixir-patterns	CONTRIBUTING.md, Style Guide, HexDocs	elixir/

Philosophy

Official guides tell you what to do. Source patterns show what mature code actually does. When they diverge, neither is wrong — they serve different audiences and optimize for different things.

This repo documents where they agree, where they differ, and why.