Exercise 3: Why "Simply" Is a Warning Sign, Not Harmless Filler — Possible Solution ==================================================================== WHAT THIS CHAPTER SAYS ------------------------------ Per this chapter's warn-box, "if a step needs the word 'simply' to sound easy, that's often a sign it's actually doing multiple things at once, or quietly skipping a prerequisite the reader hasn't been told about yet." WHY "SIMPLY" TENDS TO APPEAR EXACTLY WHERE IT'S LEAST TRUE ------------------------------ The word is typically reached for by an author who already knows the system well enough that a step feels easy to them - but that ease often comes from context and prerequisite knowledge the author isn't consciously aware they're relying on. "Simply restart the service" can quietly assume the reader already knows which service, how to check whether it's even the right fix, and what a successful restart looks like - none of which is actually simple for someone without that background, per this chapter's own "assume the reader isn't you" principle. WHY IT'S A SYMPTOM RATHER THAN THE ACTUAL PROBLEM ------------------------------ The word itself doesn't cause any harm directly - it's a signal that something underneath the step may be underspecified: a missing prerequisite, an unstated assumption, or several actions being described as if they were one. Treating "simply" as a flag to go back and re-examine the step, rather than as neutral filler, is what actually catches the real problem before a reader encounters it live. WHY THIS CONNECTS DIRECTLY TO OTHER TECHNIQUES IN THIS CHAPTER ------------------------------ A step that needs "simply" to sound easy is frequently violating one of this chapter's own other rules at the same time - bundling multiple actions into one step, or assuming unstated context the reader doesn't have. The word functions as an early warning that one of those other, more concrete problems is likely present. WHY TREATING IT AS HARMLESS WOULD MISS REAL ISSUES ------------------------------ If "simply" and "obviously" are read past as ordinary transitional language, the underspecified step behind them survives into the final document unnoticed - exactly the kind of gap that reads fine to the calm author reviewing their own work, but fails the stressed reader this whole chapter is written around. WHY THIS WORKS AS AN ANSWER ------------------------------ It quotes the chapter's own reasoning, explains why the word tends to surface exactly where hidden assumptions live, and explains why treating it as a deliberate red flag - rather than harmless filler - is what actually catches the underlying problem before a reader depends on the step.