This gist collects publications by GeePaw Hill around the topic of Incrementalism in Software Development - the advice to "take many more, much smaller steps." (MMMSS)
The good entry point into the discussion is a pair of 2020 muses: The RAT: Rework Avoidance Theory and Understanding Incremental Switchover
Later muses are also published as podcast episodes.
- Making Complex Changes
- “Avoid Changing Code” Should Be Avoided
- Endpointing vs. Next-Stepping
- Decomposition Rage Tweet Explained
- Iterative Change - What and Why
- Steps, Value, and Change-Harvesting
- More on Small Steps
- The Right Step
- The RAT: Rework Avoidance Theory
- Understanding Incremental Switchover
- Embrace Change - Modern Geekery Pratices
- Pathing: A Style of Laying Out Work
- Iterative User Value
- Iterative User Value in Flows
- Change Harvesting vs Rework Avoidance
- CHT-Style Implementation
- CHT Means Diffferent Design Imperatives
- The Cost of Rework Avoidance Theory
- Change Harvesters Iterate Change
- Why Have a Change Straegy
- Rice & Garlic & More Smaller Steps
- Big Batch Releases
- Path-Focused Design