Add the small-team case to A New Direction - #4
Merged
Conversation
The reconciliation passage explains why large institutions cannot leave the factory model. This adds the mirror image: small teams cannot enter it, because an assembly line needs enough people to staff every station and a reconciliation function needs enough people to check the station before it. Most teams do not have those people. The point is that a small team is forced by its size into the structure the document advocates, rather than having to be persuaded into it, and that this also supports the claim in Build or Buy that the approach scales down. The third paragraph keeps the passage honest. Without it the argument flatters small teams and sits badly against Reinventing the Wheel, where a generalist with modest engineering skill is exactly the researcher whose ambition is bounded by what they can personally code. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This pull request updates the A New Direction subsection in vision.tex to add the “small-team case” as a mirror argument to the existing “large institutions can’t leave the factory model” passage, positioned between the Toyota/scrapyard paragraph and the professional-kitchen analogy.
Changes:
- Adds a new three-paragraph passage explaining why small teams cannot adopt an assembly-line/reconciliation-heavy operating model due to insufficient headcount.
- Connects the small-team reality to the document’s advocated “checkerboard” structure (shared ownership, no handovers, quality at every stage).
- Adds an explicit caveat that generalism only compounds with shared tools/minimal platform foundations, tying back to earlier sections.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Adds three paragraphs to A New Direction, immediately after the Toyota/scrapyard paragraph and before "A more useful image is the professional kitchen."
The argument
The reconciliation passage explains why large institutions cannot leave the factory model — the reconciliation functions are load-bearing for careers, controls and reporting lines. This adds the mirror image: small teams cannot enter it. An assembly line needs enough people to staff every station, and a reconciliation function needs enough people to check the station before it. Most teams do not have those people and never will.
Stated together, the two halves make the factory critique sharper than either alone: the model is unleavable by the large and unavailable to the small.
It also does work the document needed elsewhere. Build or Buy claims the approach "scales down: a small team priced out of an enterprise platform can still build this way" without supporting it. This is that support, and an argument is better there than a headcount figure would be.
Why the third paragraph matters
Without the caveat the passage reads as flattery of small teams, and it sits badly against Reinventing the Wheel — a forced generalist with modest engineering skill is precisely the researcher whose ambition is bounded by what they can personally code. With it, the passage becomes an argument for why the foundation comes first, which is what Building the Kitchen already says. It also keeps clear of the edge where this would start to undercut Build or Buy: the passage points at the foundation, not at building the oven.
Placement
After Toyota and before the kitchen, the section now runs: large institutions cannot leave → here is a better factory for them → small teams cannot enter at all → the kitchen. The brigade analogy lands harder directly after a paragraph about small teams where everyone covers everything.
Note on the base branch
This targets
fix-vision-review(#3), notmain. The insertion point is adjacent to a\color{red}closing brace that #3 removes, so two independent branches would likely conflict there. Merge #3 first and GitHub will retarget this tomainautomatically. #3 remains a pure no-prose-changes PR.Verification
Built with CI's command and flags (
xelatex -halt-on-error -interaction=nonstopmode, twice): compiles clean, 15 pages, up from 14. Checked the rendered page to confirm the paragraphs sit where intended and read correctly against the surrounding text.🤖 Generated with Claude Code