KeshavSoft / definitions
Chapter 04 ยท A reading habit

Read from the outside in.

When a definition looks large, don't begin by chasing every value. First locate where you are.

Four small questions

  1. Which top-level key am I under? That is the control type.
  2. Which key is directly inside it? That is the variation.
  3. Can I see the three contract keys? Find baseFromSpec, instructions, and options.
  4. What does each value name? Read the starting spec, the instruction names, and the option names.

Don't confuse a name with the thing it names

A definition may contain a value such as tableBodyOnly or buildBody. Those are identifiers in the definition. They point toward concepts described elsewhere in the wider declarative set.

This repository's job is to make the relationship between a control variation and those named pieces understandable. It does not reproduce the full contents of every referenced spec or instruction.

A useful reading rule: Understand the definition's place first. Then follow its references only when you need to understand what those references contain.
โ† Previous: bodyOnlyNext: The library โ†’