Quiz — Chapter 28: Blog Posts, Articles, and Science Communication

Target: 70%+ before moving on.

Section 1 — Multiple Choice

1. The single feature of the general audience that drives every technique in this chapter is that the reader:

  • A) is less intelligent than a specialist reader.
  • B) is unobligated—they can leave at any second, at no cost, and owe you nothing.
  • C) prefers short paragraphs.
  • D) reads on a phone.
Answer**B.** Every other audience in the book has a reason to push through imperfect writing (a paycheck, a grade, a problem to solve); the general reader has none, so attention must be *earned* sentence by sentence. That single fact drives the hook, the jargon budget, and narrative structure. The general reader is less *specialized*, not less intelligent (A is the cardinal sin); the phone and paragraph length (C, D) are real but downstream. (§28.1.)

2. In an analogy, the "source" is:

  • A) the unfamiliar concept you're trying to explain.
  • B) the citation you got the analogy from.
  • C) the familiar thing already in the reader's head that you map the new concept onto.
  • D) the publication you're writing for.
Answer**C.** The **source** is the familiar thing (a gym, a book index, a locked box); the **target** is the unfamiliar concept being explained (A describes the target). The analogy maps the source's structure onto the target so the reader understands the new thing via something they already know. (§28.2.)

3. The most important skill in working with analogies, per the chapter, is:

  • A) finding the most vivid possible comparison.
  • B) using as many analogies as possible.
  • C) finding where the analogy breaks, deciding if the break matters for your point, and flagging it if it does.
  • D) avoiding analogies entirely in serious writing.
Answer**C.** Every analogy is wrong somewhere—that's the definition—and a reader trusts an analogy further than you intend, so the skill is locating the break, judging whether it sits on your point, and naming it before the reader trips over it. Vividness (A) without a known break is dangerous; more analogies (B) is not better; avoiding them (D) discards the most powerful tool you have. (§28.3, threshold concept.)

4. The "jargon budget" for an article aimed at a general audience is, as a working rule:

  • A) zero technical terms, ever.
  • B) two or three technical terms, maximum.
  • C) one term per paragraph.
  • D) as many as needed for precision.
Answer**B.** Two or three per article, because every unexplained term is an exit for an unobligated reader. Zero (A) is usually impossible and unnecessary—you can keep-and-define the essential ones; "as many as needed" (D) is the specialist's standard, not the public's. And it must be enforced *mechanically* (circle and count), because fluency makes your jargon invisible to you. (§28.3.)

5. A "curiosity gap" is:

  • A) the time between writing and publishing.
  • B) the difference in knowledge between you and your reader.
  • C) a gap between what the reader knows and what they sense they're about to find out, which a hook opens and the article closes.
  • D) a missing section in your outline.
Answer**C.** A hook opens a loop—a question the reader now needs answered, a fact that breaks their model—and the reader stays to see it closed. (B is the *knowledge* gap / curse of knowledge, a different idea.) The whole transaction of an opening is: open a loop in the first two sentences, close it across the piece. (§28.4.)

6. Which opening fails as a hook, and why?

  • A) "The most dangerous part of flying isn't turbulence. It's a clipboard."
  • B) "In this post, we will explore the topic of customer churn."
  • C) "Why do two people who eat the same meal get different blood-sugar spikes?"
  • D) "At 11:38 p.m., the engineer sent the memo he'd been dreading."
Answer**B.** It *closes* the gap instead of opening one: announcing the topic and the structure ("we will explore") tells the reader everything they need to decide whether to care and leaves nothing they need to keep reading for. A, C, and D each open a loop (a surprising fact, a question, a scene). A topic announcement supplies the prediction up front and kills the need to continue. (§28.4.)

7. Why is IMRaD (Introduction, Methods, Results, Discussion) a poor structure for a general-audience article?

  • A) It's too short.
  • B) It front-loads the apparatus (background, method) the unobligated reader has the least patience for and saves the "so what" for the end, where they'll never arrive.
  • C) It uses too many figures.
  • D) It's only for chemistry.
Answer**B.** IMRaD is excellent for the specialist who *must* finish and wants to verify before trusting—but the general reader must be *made* to finish, and leading with method gives them every reason to leave before the meaning. It's the same failure as Dana's method-first memo ([Chapter 27](../chapter-27-writing-about-data/index.md)), pushed to the extreme. The fix is narrative—hook → journey → payoff—which *narrates* the rigor rather than front-loading it. (§28.5.)

8. The "nut graf" is:

  • A) the opening hook itself.
  • B) the short passage just after the hook that orients the reader to what the piece is about and why it matters.
  • C) the conclusion.
  • D) the byline.
Answer**B.** The **lede** is the hook (the opening that sets the tension); the **nut graf** ("nutshell paragraph") is the bridge right after it that tells the reader why this story matters and what it's about, getting them from "huh, interesting" to "ah, I see why I'm reading." The lede grabs; the nut graf orients. (§28.5.)

9. According to the chapter, the honest core of SEO is:

  • A) stuffing as many keywords as possible into the text.
  • B) writing so that a person searching for what you wrote about can find it—the same audience service the book teaches, extended to before the reader arrives.
  • C) tricking search engines into ranking you higher than you deserve.
  • D) irrelevant to good writers.
Answer**B.** Honest SEO and good writing are the *same* choices—a searchable-and-compelling title, a meta description, descriptive headers, an FAQ—made to connect a specific reader with the specific thing they need. Keyword-stuffing (A) and gaming rankings (C) are the dishonest version the book explicitly rejects with its "does this help the right reader, or trick the wrong one?" test. The book itself uses honest SEO, which is the proof. (§28.7.)

10. The single most important SEO element, which is also a hook, is:

  • A) the meta description.
  • B) the title.
  • C) the first image.
  • D) the URL slug.
Answer**B.** The title appears in search results and determines whether anyone clicks, so it must contain the words a reader searches *and* promise something compelling. A clever-but-unsearchable title gets zero readers; the move is to engineer one that's both findable and compelling (e.g., "Why New Customers Quit in the First Month — and What Fixes It"). The meta description (A) matters but is the *ad for the click*, secondary to the title. (§28.7.)

11. A good pitch email to a publication should open with:

  • A) "I'd like to pitch an article for your publication."
  • B) your credentials and an attached CV.
  • C) the hook itself—the most compelling thing about the piece, the same opening you'd use in the article.
  • D) a list of topics you could write about.
Answer**C.** Opening with the hook proves you can do the one thing the job requires, and it pulls the editor in exactly as it would a reader. "I'd like to pitch" (A) leads with the writer, not the idea; credentials and a CV (B) come *after* the idea, in one line; a topic list (D) shows no angle. The pitch is itself a tiny science-communication piece—hook, so-what, audience-fit. (§28.8.)

12. "Translate, don't dumb down" means:

  • A) use a translation tool to reach foreign-language readers.
  • B) keep the real idea intact and change only the vocabulary and frame to fit a non-specialist.
  • C) remove anything complicated.
  • D) write at a lower reading level by shortening every word.
Answer**B.** Dumbing down cuts the actual idea or condescends; translating preserves the idea (the interesting, true thing) and changes the vocabulary and order to fit the reader—the same distinction from Chapters 2 and 7. "Remove anything complicated" (C) is the dumbing-down trap restated. If your simplified version no longer contains the thing that was interesting or true, you gutted it. (§28.1, §28.9.)

Section 2 — True/False with Justification

State true or false and justify in one sentence.

T1. A general audience is less intelligent than a specialist audience.

Answer**False.** A general reader is less *specialized in your field*, not less intelligent—a cardiac surgeon is a general reader for a post on compiler design, and you'd spare her the jargon, not write down to her. Condescension is the cardinal sin of science communication, and readers detect it instantly.

T2. A perfect analogy—one with no break—is the goal.

Answer**False.** There's no such thing: an analogy works *because* the source isn't the target, so every analogy diverges somewhere. The goal is an analogy whose break you *understand and disclose* (if it's load-bearing), not a nonexistent flawless one.

T3. Flagging where your analogy breaks undermines your credibility.

Answer**False.** It *builds* credibility—it signals you understand the target deeply enough to see past your own simplification (expertise) and it pre-empts the knowledgeable reader's objection before they raise it (honesty). An unflagged analogy a reader catches breaking looks like ignorance; a flagged one looks like mastery.

T4. Leading a popular article with your methodology makes it more trustworthy to a general reader.

Answer**False.** It front-loads the apparatus the general reader can't evaluate and has the least patience for, so they leave before the finding (the IMRaD failure). The fix is to *narrate* the rigor as part of the journey, not hide it—rigor delivered as a story is what keeps a non-specialist reading.

T5. You can reliably tell whether you're within your jargon budget just by re-reading your draft.

Answer**False.** The curse of knowledge makes your own field's vocabulary read as plain to you, so the terms that are walls to the reader are invisible to you—your "feel" is broken in exactly the direction that matters. You must enforce the budget mechanically: circle every term, count, and cut.

T6. A title that's clever and literary is always better than a plain, searchable one.

Answer**False.** A clever-but-unsearchable title ("The Silent Goodbye") gets found by no one, so it has zero readers; findable-but-plain beats clever-but-invisible. The best move is a title that's *both*—a searched phrase plus a hook—but when forced to choose, findability wins because an unfound piece doesn't exist.

Section 3 — Short Answer

S1. Name the three tests a good analogy must pass (§28.2), in one phrase each.

Model answer(1) The **source is genuinely familiar** to *this* reader (not a second piece of jargon); (2) the **mapping holds for the one relationship** your point depends on; (3) the reader can **reason *with* it**—extend it correctly on their own, not just nod at it. *Rubric: all three, roughly in these terms.*

S2. Explain the two-step procedure for handling an analogy's break (§28.3), and what you do in each of the two cases the second step produces.

Model answer**Step 1:** List where the source and target diverge (name a few ways the gym isn't a software company). **Step 2:** Ask whether any divergence sits *on your point*. If the break is off to the side (irrelevant to what you're explaining), the analogy is safe—use it, maybe with a light wave at the edge. If the break is *load-bearing*—it sits right on what you're explaining—either flag it explicitly or pick a different source whose break is elsewhere. *Rubric: list divergences, test against the point, both cases handled.*

S3. Why does "In this post, we will explore X" fail as an opening, and what should replace it? (§28.4)

Model answerIt *closes* the curiosity gap instead of opening one—by announcing the topic and the structure, it gives the reader everything they need to decide whether to care and nothing they need to keep reading *for*. Replace it with a hook that opens a gap: a surprising fact, a question, a scene, or the stakes—something the reader now *needs* the next sentences to resolve. *Rubric: names the closed-vs-open gap + a hook replacement.*

S4. Contrast IMRaD and narrative structure in terms of what each assumes about the reader (§28.5).

Model answerIMRaD assumes a reader who *must* finish—paid, graded, or professionally obligated—and who wants to verify the method before trusting the result, so it front-loads apparatus and saves the meaning for the end. Narrative assumes a reader who *can leave at any second and owes you nothing*, so it leads with tension (a hook), narrates the rigor as a journey, and lands the "so what" so the reader is rewarded for staying. The structures differ because the readers differ in whether finishing is obligatory. *Rubric: the must-finish vs. can-leave contrast drives the structural difference.*

S5. The book carries seo_description and seo_queries in every chapter's frontmatter and ends each chapter with an FAQ. What is it demonstrating, beyond "ranking on Google"? (§28.7)

Model answerThat honest SEO and good writing are the *same* choices—serving a specific reader by helping them find and navigate the exact content they need—so "optimization" done honestly is just audience service extended to the moment before the reader arrives. The book models its own advice rather than preaching findable, reader-serving writing while being an undiscoverable wall of generic headings. *Rubric: SEO = audience service / same choices + the book modeling its advice.*

Section 4 — Applied Scenario

Scenario. You're handed this draft opening of a company blog post, reported as "nobody finishes it." Fix it.

"## Understanding Our New Recommendation Engine. Our recommendation engine uses collaborative filtering combined with a content-based model to generate personalized suggestions. The collaborative-filtering component computes item-item similarity from the user-interaction matrix, while the content-based component uses TF-IDF vectors over item metadata. The two are combined via a weighted ensemble. In this post, we explain how it works."

Write (a) a short critique (4–6 sentences) naming what's broken, and (b) a rewrite of just the title, opening hook, nut graf, and the one core analogy (you don't have to write the whole post). Your critique should identify the hook failure, count the jargon-budget overrun, and name the structural problem. Your rewrite must open a curiosity gap, build one analogy from a source a general reader owns (for "how recommendations work"), keep the jargon within two or three terms, and give a searchable-compelling title.

Rubric **Critique (full marks):** identifies that there's *no hook*—it opens with the topic ("Understanding our…") and ends with "in this post we explain," closing the gap (§28.4); counts the jargon overrun (collaborative filtering, content-based model, item-item similarity, user-interaction matrix, TF-IDF vectors, weighted ensemble = ~6 walls, far over budget, §28.3); names the structural failure as method-first / IMRaD-style, front-loading the apparatus the reader can't evaluate (§28.5); notes the title is a topic label, not searchable or compelling (§28.7). **Rewrite (full marks):** - **Title:** searchable *and* compelling, e.g., "How Does Netflix Know What You'll Like? A Look Under the Hood of Recommendations" (contains the searched idea + a hook). - **Hook:** opens a curiosity gap, e.g., "Some days it feels like your apps know you better than your friends do. You watch one cooking video and suddenly your whole feed is risotto. How does it actually *do* that—and is it reading your mind, or something simpler?" - **Nut graf:** orients—e.g., "This is a look at how recommendation engines actually work, using nothing more complicated than the way you already get suggestions from people you trust." - **Analogy:** one source the reader owns, e.g., "A recommendation engine works like asking friends with similar taste what they loved (collaborative filtering, the *one* term kept) *and* noticing that you liked three spicy dishes so you'll probably like a fourth (content-based). It blends both."—jargon kept to ≤2 defined terms, the rest cut. - **Bonus:** flags the analogy's break if pushed ("unlike a friend, the engine has no idea *why* you liked something—it only sees the pattern"). No "in this post we will explore."

Scoring & Next Steps

Score What to do
< 50% Re-read §28.1 (the unobligated reader), §28.2–§28.3 (the analogy and its break—the heart of the chapter), and §28.4 (hooks). These three carry most of the skill.
50–70% Redo Part B (Revise This), especially B1 (the jargon-to-analogy rewrite) and B5 (method-first to narrative)—the skill lives in the revising, not the theory.
70–85% You've got it. Proceed to Chapter 29 (Writing with AI), and try writing your Portfolio Piece 7 (Part C5) if you haven't.
> 85% Try Part E: reverse-engineer a published article you admire (E1) or build an analogy bank for your field (E3)—what working science communicators actually do.

Back to: Chapter 28 · Exercises · Case Study · Key Takeaways