reducing-entropy

1# Reducing Entropy
2 
3More code begets more code. Entropy accumulates. This skill biases toward the smallest possible codebase.
4 
5**Core question:** "What does the codebase look like *after*?"
6 
7## Before You Begin
8 
9**Load at least one mindset from `references/`**
10 
111. List the files in the reference directory
122. Read frontmatter descriptions to pick which applies
133. Load at least one
144. State which you loaded and its core principle
15 
16**Do not proceed until you've done this.**
17 
18## The Goal
19 
20The goal is **less total code in the final codebase** - not less code to write right now.
21 
22- Writing 50 lines that delete 200 lines = net win
23- Keeping 14 functions to avoid writing 2 = net loss
24- "No churn" is not a goal. Less code is the goal.
25 
26**Measure the end state, not the effort.**
27 
28## Three Questions
29 
30### 1. What's the smallest codebase that solves this?
31 
32Not "what's the smallest change" - what's the smallest *result*.
33 
34- Could this be 2 functions instead of 14?
35- Could this be 0 functions (delete the feature)?
36- What would we delete if we did this?
37 
38### 2. Does the proposed change result in less total code?
39 
40Count lines before and after. If after > before, reject it.
41 
42- "Better organized" but more code = more entropy
43- "More flexible" but more code = more entropy
44- "Cleaner separation" but more code = more entropy
45 
46### 3. What can we delete?
47 
48Every change is an opportunity to delete. Ask:
49 
50- What does this make obsolete?
51- What was only needed because of what we're replacing?
52…