---
id: "action-shift-altitude"
type: "action-item"
source_timestamps: ["00:07:49", "00:09:30"]
tags: ["workflow", "debugging"]
related: ["concept-strategic-deep-diving", "concept-vibe-coding", "concept-archaeological-programming"]
speakers: ["Nate B. Jones"]
action: "Deliberately shift between high-level architectural prompting and low-level line-by-line debugging when AI agents fail."
outcome: "Builds system-level leverage while preventing 'archaeological programming' and experiential debt."
sources: ["s25-builders-identity-shift"]
sourceVaultSlug: "s25-builders-identity-shift"
originDay: 25
---
# Practice Altitude Shifting

## Action
Deliberately shift between high-level architectural prompting and low-level line-by-line debugging when AI agents fail.

## Why
To avoid the dual pitfalls of:
- Pure micromanagement (no leverage)
- Pure [[concept-vibe-coding]] (accumulating [[concept-experiential-debt]] and [[concept-archaeological-programming]])

## Concrete Steps
1. **Default to cruising altitude.** Manage AI agents at a high, architectural level. Provide broad directives. Coordinate multiple agents.
2. **Detect turbulence.** Watch for: agents stuck in loops, persistent bugs, broken user-facing flows.
3. **Drop to lowest abstraction.** Open the specific files. Read the code. Understand the exact mechanical failure — line by line if needed.
4. **Identify root cause.** Don't just patch — understand *why* the agent produced this failure.
5. **Ladder back up.** Return to architectural altitude. Adjust the system prompt or agent instructions that led to the error in the first place.

## Connected Concepts
- Conceptual basis: [[concept-strategic-deep-diving]]
- Avoids failure modes: [[concept-vibe-coding]] (when used exclusively), [[concept-archaeological-programming]], [[concept-experiential-debt]]
- Required mindset: [[concept-engineering-manager-mindset]]

## Outcome
Builds system-level leverage while preventing archaeological programming and experiential debt.