tax-app is a demo app I built for an upcoming YC channel video,
not an "import-dominated history" as the previous commit claimed.
Excluded because it's not production shipping work, not because
of an import commit.
Updated rationale in scripts/garry-output-comparison.ts's
EXCLUDED_REPOS constant, in docs/ON_THE_LOC_CONTROVERSY.md's
method section + conclusion, and in the README hero wording
("one demo repo" vs the earlier "repos dominated by imported code").
Numbers unchanged — the exclusion itself is the same, just the
reason.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
tax-app's history is one commit of 104K logical lines — an initial
import of a codebase, not authored work. Removing it to keep the
comparison honest.
Changes:
- scripts/garry-output-comparison.ts: added EXCLUDED_REPOS constant
with tax-app + a one-line rationale. The script now skips excluded
repos with a stderr note and deletes any stale output JSON so
aggregation loops don't pick up pre-exclusion numbers.
- README hero: updated to 810× run rate + 240× YTD (were 880×/260×).
Wording updated to "40 public + private repos ... after excluding
repos dominated by imported code."
- docs/ON_THE_LOC_CONTROVERSY.md: updated all numbers, added an
"Exclusions" paragraph explaining tax-app, removed tax-app from
the "shipped not WIP" example list.
New numbers (2026 through day 108, without tax-app):
- To-date: 240× logical SLOC (1,233,062 vs 5,143)
- Run rate: 810× per-day pace (11,417 vs 14 logical/day)
- Annualized: ~4.2M logical lines projected
Future re-runs automatically skip tax-app. Add more exclusions to
EXCLUDED_REPOS at the top of the script with a one-line rationale.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Enhanced scripts/garry-output-comparison.ts so both calculations come
out of a single run instead of being reassembled ad-hoc in bash:
PerYearResult now includes:
- days_elapsed — 365 for past years, day-of-year for current
- is_partial — flags the current (in-progress) year
- per_day_rate — logical/raw/commits normalized by calendar day
- annualized_projection — per_day_rate × 365
Output JSON's `multiples` now has two sibling blocks:
- multiples.to_date — raw volume ratios (2026-YTD / 2013-full-year)
- multiples.run_rate — per-day pace ratios (apples-to-apples)
Back-compat: multiples.logical_lines_added still aliases to_date for
older consumers reading the JSON.
Updated README hero to cite both (picking up brain/* repo that was
missed in the earlier aggregation pass):
2026 run rate: ~880× my 2013 pace (12,382 vs 14 logical lines/day)
2026 YTD: 260× the entire 2013 year
Stderr summary now prints both multiples at the end of each run.
Full analysis at ~/throughput-analysis-2026-04-18.md (local-only).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Three new scripts:
- scripts/garry-output-comparison.ts — enumerates Garry-authored commits
in 2013 + 2026 on public repos, extracts ADDED lines from git diff,
classifies as logical SLOC via scc --stdin (regex fallback if scc
missing). Writes docs/throughput-2013-vs-2026.json with per-language
breakdown + explicit caveats (public repos only, commit-style drift,
private-work exclusion).
- scripts/update-readme-throughput.ts — reads the JSON if present,
replaces the README's <!-- GSTACK-THROUGHPUT-PLACEHOLDER --> anchor
with the computed multiple (preserving the anchor for future runs).
If JSON missing, writes GSTACK-THROUGHPUT-PENDING marker that CI
rejects — forcing the build to run before commit.
- scripts/setup-scc.sh — standalone OS-detecting installer for scc.
Not a package.json dependency (95% of users never run throughput).
Brew on macOS, apt on Linux, GitHub releases link on Windows.
Two-string anchor pattern (PLACEHOLDER vs PENDING) prevents the
pipeline from destroying its own update path.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>