fork

dilemma.dev

A glossy coastal tutorial for the moment your code forks into two tempting choices.

if (path === "A" || path === "B") sketchTheTide();

The forked tide

Write both paths like tide marks. Keep the reasons visible, messy, and small enough to test.

  • What gets easier?
  • What becomes fragile?
  • Who feels the ripple?

pearl code tab

choose({
  now: "ship the tiny fix",
  later: "shape the better API",
  clue: "which regret is reversible?"
});
?

Compare the cost of being wrong, not just the thrill of being right.

test

Debugging with feelings

Run a tiny experiment that gives both choices a fair minute in the sun. Make it small, observable, and kind to future-you.

A

Prototype the happy path

Build the thinnest wave that reaches shore.

B

Spike the risky edge

Touch the sharpest coral before committing.

☽

ship

Commit with confidence

Pick the path with the cleanest lesson. Leave a breadcrumb for later, a rollback note for safety, and one glittering reason your future self can trust.

retrace the tide
decisionchosen with evidence
fallbackvisible before launch
feelingcalm enough to ship