
**TL;DR** - Writing less code becoming deliberate engineering strategy; stacked PRs reduce review friction; economics of building for the Moon.
1. Challenge your team assumption that more code equals more value - refactor for deletability, not just functionality
2. Implement stacked PRs using tools like Graphite or linear.app if doing code review at scale
3. Study NASA software standards for space deployments - most rigorous reliability requirements in existence
**Example Prompt:**
Design a code review process using stacked PRs and AI pre-review to reduce reviewer cognitive load.
| Pros | Cons |
|---|---|
| Writing less code is a legitimate strategy | Maintenance burden does not disappear when you use AI |
| Stacked PRs genuinely improve review quality | Stacked PRs require tooling investment |
|---|---|
| Space software standards worth studying | Most teams do not have NASA reliability requirements |