rodin/patterns-vs-guidelines
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
7 Commits 1 Branch 0 Tags
7e99faff599d6d3f6a859f725f66c3cffc5878f8
Commit Graph

7 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
Rodin 7e99faff59 docs: PR discussion analysis — how new patterns are debated and landed 
Real PR threads from CockroachDB, Prometheus, and Oban showing:
- Handle pattern (PR #142059): 2.5 months, trace span issues discovered in review
- slog migration (PR #14906): 'merge and iterate', 162 files, one commit for 3.0
- AppenderV2 (issue #17632): maintainer pushback defeated by 'it's not user-facing'
- Oban inline testing (PR #684): <24h, zero discussion, solo maintainer

Key insight: 'merge and iterate' beats 'perfect before merge' for
pattern introductions.
 2026-04-30 11:12:07 -07:00
Rodin ea9fa61d1e docs: pattern break archaeology — WHY (not just WHAT) is impure 
Git blame + commit messages reveal four categories:
1. Ship behavior, fix plumbing later (time pressure)
2. Better tooling exposed limitations (observability)
3. Removal cost > carrying cost (zero-interest debt)
4. Context needs different patterns (not actually a break)

Specific findings:
- CockroachDB Handle: introduced for profiling, not correctness
- Stale 22.2 TODO: struct field costs 0, removal touches many files
- Prometheus globals: startup constants read in hot path = correct call
- AppenderV2: unifies 4 type-asserted interfaces into 1
- Ecto zero TODOs: version-gated, cleaned on version bumps by José
 2026-04-30 11:07:12 -07:00
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
Rodin 76f4bcc33e docs: architectural analysis of top repos (CockroachDB, Prometheus, Ecto, Oban) 
Four documents examining codebases at module and ecosystem levels:
- architectural-analysis.md — internal structure, dependency flow
- ecosystem-analysis.md — consumer extension points, deliberate absences
- crosscutting-analysis.md — logging, config, retry, lifecycle
- testing-evolution-analysis.md — proof models, API evolution strategies
 2026-04-30 10:50:54 -07:00
Rodin 22e103ebfb docs: Elixir patterns vs official guidelines with code examples + hypotheses 2026-04-30 07:58:31 -07:00
Rodin 6c1fa35b1c docs: enhance Go divergence analysis with code examples + hypotheses 2026-04-30 07:57:37 -07:00
Rodin ca07514d9c docs: Go patterns vs official guidelines divergence analysis 2026-04-30 07:50:32 -07:00