De-slop: remove every em-dash + banned words across all modules + capstone (#94)
Sync course wiki / sync-wiki (push) Successful in 4s

Co-authored-by: claude <claude@jpaul.io>
Co-committed-by: claude <claude@jpaul.io>
This commit was merged in pull request #94.
This commit is contained in:
2026-06-22 23:21:22 -04:00
committed by Claude (agent)
parent 513d7e7ac8
commit c098933f25
99 changed files with 1324 additions and 1315 deletions
+12 -3
View File
@@ -61,9 +61,18 @@ then use a calculator.
Direct, concrete, rigorous. Reframe ops instincts the reader already has toward AI-assisted work.
No motivational filler. When in doubt, show the command and what goes wrong without it.
**No slop.** Don't write like an AI. Avoid "prose" (say "writing", "words", or "docs"), "unlock",
"leverage" as filler, "delve", "dive in", "seamless", "in today's fast-paced", "it's worth noting".
Don't lean on em-dashes — at density they read as a machine tell; vary the punctuation.
**No slop (hard rules).** Don't write like an AI.
- **No em-dash character (`—`) anywhere.** Use a semicolon, a period, a comma, or restructure the
sentence. This is absolute; self-check every edit by searching for `—` and removing each one.
- **Banned words:** "prose" (say "writing"/"words"/"docs"), delve, leverage, utilize, foster,
bolster, underscore, unveil, streamline, robust, comprehensive, pivotal, seamless, significantly,
extremely, truly, unlock, "dive in".
- **Banned openers/transitions:** Furthermore, Moreover, That being said, In today's world,
It's worth noting, When it comes to.
- No hollow "this is important" statements, no intensifier standing in for a number, no weasel
hedges ("may potentially", "can help to"), no dramatic/teasing headings (a heading names its
content). End claims on a concrete, checkable fact.
## Conventions for labs