YENPO JOURNAL

From the symptom
back to the source.

Why did this value win? How did an old request overwrite a new one? Work through small examples, then run the tests to see what happens.

CHOOSE A READING PATH

What are you trying to find out?

Start with the question in front of you, or work through these four stages from understanding a project to checking its behavior.

  1. Where should I start in this project?

    Find an entry and sketch the files behind one behavior. Then follow a value, or use history to ask why a line exists.

  2. Which path does this input take?

    Trace calls and branches from the entry point to the result you can observe.

  3. Does the explanation fit the code?

    Compare the explanation with the branches and inputs in the code. For a patch, check which two versions you are comparing.

  4. Which behavior should I verify?

    Record current behavior, check affected callers, and inspect the assertions. Run the examples in your terminal.