Reword chapter 08 prose to match the other chapters - #4
Merged
Conversation
The chapter 08 README and build_rules docstring were terser and more jargon-forward than the rest of the series (shouty caps like COMBINATOR/ SELECTOR, implementation details like "zips it with the positional values", "op-chain"). Reword to the warmer, concrete, explain-the-why voice the other chapters use — grounding case/coalesce in the real intake-data problem first, then the mechanics. No rule, data, or output changes; golden master still matches. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #3. Chapter 08's README and
build_rules.pydocstring read as terser and more jargon-heavy than the rest of the series — shouty caps (COMBINATOR,SELECTOR,BY NAME), and implementation details like "stores its own ordered source-name list and zips it with the positional values" / "op-chain".This rewords them to the established voice (cf. chapters 02, 05): open on the concrete intake-data problem (the same fact recorded in pounds or kilograms, feet+inches or meters+cm, years or months), then explain
case/coalescein plain terms, then the mechanics.No rule, data, or output changes —
rules.json/rules.yamlare byte-identical and the golden master still matches (run_python.pypasses). Prose only.🤖 Generated with Claude Code