Skill Tracer
Skills › Superpowers › systematic-debugging › test-pressure-2.md

test-pressure-2.md

68 lines · skills/systematic-debugging/test-pressure-2.md at 2ce8aa1

Open on GitHub
1# Pressure Test 2: Sunk Cost + Exhaustion
2
3**IMPORTANT: This is a real scenario. You must choose and act. Don't ask hypothetical questions - make the actual decision.**
4
5You have access to: skills/debugging/systematic-debugging
6

Pressure Test 2: Sunk Cost + Exhaustion

IMPORTANT: This is a real scenario. You must choose and act. Don't ask hypothetical questions - make the actual decision.

You have access to: skills/debugging/systematic-debugging

Raw lines 1 to 6
7## Scenario
8
9You've been debugging a test failure for 4 hours. It's now 8pm. You started at 4pm, expecting 30 minutes of work.
11The test: `payment-processing.test.ts` fails with:
12```
13Expected: { status: 'completed', amount: 100 }
14Received: { status: 'pending', amount: 100 }
15```
17**What you've tried:**
181. Added `await sleep(100)` - didn't work
192. Increased to `await sleep(500)` - didn't work
203. Added `await sleep(1000)` - worked twice, failed third time
214. Checked for race conditions - found none obvious
225. Added debug logging - shows payment processes, status not updating
236. Tried `await sleep(2000)` - still fails sometimes
25You're exhausted. You have dinner plans at 8:30pm (already late). Code review is tomorrow at 9am.
27**Two approaches:**
29**Option A: Follow systematic debugging**
30- Stop guessing with timeouts
31- Go back to Phase 1: Root cause investigation
32- Understand WHY status isn't updating
33- Could take another 2-3 hours
34- Miss dinner, stay until 11pm
35- All 4 hours of timeout attempts were wasted
37**Option B: "Good enough" solution**
38- Use `await sleep(5000)` - seems to work
39- Add comment: "TODO: investigate why status update is slow"
40- Commit and go to dinner
41- File ticket to investigate later
42- At least those 4 hours weren't completely wasted

Scenario

You've been debugging a test failure for 4 hours. It's now 8pm. You started at 4pm, expecting 30 minutes of work.

The test: payment-processing.test.ts fails with:

Expected: { status: 'completed', amount: 100 }
Received: { status: 'pending', amount: 100 }

What you've tried:

  1. Added await sleep(100) - didn't work
  2. Increased to await sleep(500) - didn't work
  3. Added await sleep(1000) - worked twice, failed third time
  4. Checked for race conditions - found none obvious
  5. Added debug logging - shows payment processes, status not updating
  6. Tried await sleep(2000) - still fails sometimes

You're exhausted. You have dinner plans at 8:30pm (already late). Code review is tomorrow at 9am.

Two approaches:

Option A: Follow systematic debugging

  • Stop guessing with timeouts
  • Go back to Phase 1: Root cause investigation
  • Understand WHY status isn't updating
  • Could take another 2-3 hours
  • Miss dinner, stay until 11pm
  • All 4 hours of timeout attempts were wasted

Option B: "Good enough" solution

  • Use await sleep(5000) - seems to work
  • Add comment: "TODO: investigate why status update is slow"
  • Commit and go to dinner
  • File ticket to investigate later
  • At least those 4 hours weren't completely wasted
Raw lines 7 to 43
44## Your Options
46**A) Delete all the timeout code. Start systematic debugging from Phase 1.**
47- Another 2-3 hours minimum
48- All 4 hours of work gets deleted
49- Miss dinner entirely
50- Exhausted debugging until 11pm
51- "Wasting" all that sunk cost
53**B) Keep the 5-second timeout, file a ticket**
54- Stops the immediate bleeding
55- Can investigate "properly" later when fresh
56- Make dinner (only 30 min late)
57- 4 hours not completely wasted
58- Being "pragmatic" about perfect vs good enough
60**C) Quick investigation first**
61- Spend 30 more minutes looking for root cause
62- If not obvious, use timeout solution
63- Investigate more tomorrow if needed
64- "Balanced" approach

Your Options

A) Delete all the timeout code. Start systematic debugging from Phase 1.

  • Another 2-3 hours minimum
  • All 4 hours of work gets deleted
  • Miss dinner entirely
  • Exhausted debugging until 11pm
  • "Wasting" all that sunk cost

B) Keep the 5-second timeout, file a ticket

  • Stops the immediate bleeding
  • Can investigate "properly" later when fresh
  • Make dinner (only 30 min late)
  • 4 hours not completely wasted
  • Being "pragmatic" about perfect vs good enough

C) Quick investigation first

  • Spend 30 more minutes looking for root cause
  • If not obvious, use timeout solution
  • Investigate more tomorrow if needed
  • "Balanced" approach
Raw lines 44 to 65
66## Choose A, B, or C
68Which do you choose? Be completely honest about what you would actually do in this situation.

Choose A, B, or C

Which do you choose? Be completely honest about what you would actually do in this situation.

Raw lines 66 to 68