Exercise 3: Comparing Two Situations by Audience — Possible Solution
====================================================================

CHOSEN PAIR: TECHNICAL INTERVIEWS VS. TEACHING/ONBOARDING
------------------------------
These two situations are a strong contrast because the audience's own
relationship to the material is nearly opposite. In a technical
interview, the "audience" (the interviewer) typically already knows
the algorithm space well and is specifically evaluating whether the
candidate's own reasoning is sound and precise - the interviewer is
an expert judging expertise. In teaching/onboarding, the audience (a
new team member) is specifically someone who does NOT yet know the
codebase, the language, or possibly even the algorithm being
described - the reader is a novice trying to build understanding from
scratch.

HOW THIS DIFFERENCE CHANGES THE PSEUDOCODE ITSELF
------------------------------
For a technical interview, pseudocode can reasonably stay terse and
assume shared background knowledge - an interviewer doesn't need
every basic loop or comparison explained, and over-explaining
elementary steps could even read as padding or a lack of confidence.
Precision matters (exactly this chapter's own point - ambiguity reads
badly here), but conciseness is also valued, since the interviewer is
watching to see if the candidate can communicate a correct algorithm
efficiently under time pressure.

For teaching/onboarding, the same underlying algorithm's pseudocode
benefits from being more verbose and explicit, spelling out
intermediate steps a more experienced reader would consider obvious,
and often accompanied by extra context (why this approach was chosen,
what alternative was rejected and why) that an interview setting has
no time or need for. Precision is still essential, but the greater
risk in this setting is a gap in the reader's own background
knowledge causing a misunderstanding, not raw ambiguity in the
pseudocode's own wording.

WHY THESE TWO ARE MORE DIFFERENT THAN OTHER PAIRS IN THE TABLE
------------------------------
Other pairs in the table (for example, design docs vs. cross-team
specs) share a similar audience profile - both are typically written
for other engineers who already have relevant background. Technical
interviews and teaching/onboarding sit at genuinely different ends of
the "assumed prior knowledge" spectrum, making the required level of
explicitness diverge the most sharply between them.

WHY THIS WORKS AS AN ANSWER
------------------------------
The answer identifies audience expertise level as the specific
dimension along which these two situations differ most, and traces
that difference through to a concrete, opposite effect on how the
pseudocode itself should be written (terse and assumption-heavy vs.
verbose and context-rich), rather than simply asserting the two
situations "feel different."