code-simplificationlisted

# Code Simplification Simpler code isn't fewer lines. It's code that's easier to read, understand, and change. ## Progress Checklist - [ ] Understand why the code exists (Chesterton's Fence) - [ ] Define scope of simplification - [ ] Make one change at a time - [ ] Verify after each change - [ ] Ensure project conventions are followed ## Step 0: Chesterton's Fence Before removing or rewriting anything, understand why it exists. ```bash # Who wrote this and when? git blame path/to/file # What was the commit about? git log --oneline -5 -- path/to/file # Was there a PR? What was the context? git log --format="%H %s" -5 -- path/to/file ``` Look for: - Linked work items or issue numbers in commit messages - PR descriptions explaining the reasoning - Comments explaining workarounds (browser quirks, API limitations, business rules) - Tests that depend on this specific behavior **If you don't understand why something is there, don't remove it.** Ask first. ## Step 1: Define Scope Only simplify what was requested or what you're currently working on. Don't: - Simplify unrelated code you noticed while passing through - Combine simplification with feature work in the same change - "Improve" code style to your personal preference over project conventions ## Step 2: One Change at a Time Each simplification should be a single, reviewable change: 1. Make the change 2. Run tests: `npm test`, `go test ./...`, `dotnet test`, etc. 3. Check types: `tsc --noEmit`, `go vet`, etc. 4.