home/ atoms/ iterative-refinement-live-coding-workflow

Dividing a shader build into named checkpoint stages lets you resume from a stable state and avoid rabbit holes

IQ structures the Happy Jumping live stream into 5 parts: basic raymarching, modeling, set/animation, lighting, optimization. Each part starts from a pre-saved checkpoint shader. This means deviations in part 2 can be abandoned and reset before part 3. The technique prevents cumulative bugs from compounding, provides recovery from live-coding dead ends, and lets him move to the ‘fun’ section (lighting) even if modeling was imperfect. The same principle applies to iterating on any complex procedural shader: identify the minimal stable state before adding the next layer.

Examples

In Shadertoy, save multiple shader versions (‘Happy Jumping Part 1’, ‘Part 2’, etc.) so you can open a stable baseline before extending.

Assessment

You are live coding a character shader and a bug corrupts the shadow system. Describe how checkpointed stages would help you recover and continue.

“safe point in the timeline that led me to the final piece. So here we go. switch here to, okay, these are the different actually steps that we are going to go through”
corpus · inigo-quilez-live-coding-happy-jumping-video · chunk 2