Personal Dev Writing¶
10 cards — 🟢 3 easy | 🟡 4 medium | 🔴 3 hard
🟢 Easy (3)¶
1. Why does active voice produce clearer writing than passive voice in most technical contexts?
Show answer
Active voice names the actor and the action directly: "The deploy script restarts the service" vs. "The service is restarted by the deploy script." Active voice is shorter, assigns responsibility clearly, and is easier to parse. Passive voice hides the actor, which obscures who did what -- dangerous in runbooks, postmortems, and incident reports where accountability matters. Use passive only when the actor is genuinely unknown or irrelevant.2. What is the difference between concrete and abstract language, and when should you prefer each?
Show answer
Concrete language names specific, observable things: "p99 latency increased from 200ms to 800ms after the 14:00 deploy." Abstract language names categories and concepts: "performance degraded after the change." Prefer concrete when communicating facts, incidents, or instructions. Use abstract when framing strategy or principles. Most unclear writing is abstract where it should be concrete -- the cure is to name the specific thing.3. What is the inverted pyramid structure and why is it effective for technical communication?
Show answer
The inverted pyramid puts the most important information first (conclusion or key finding), followed by supporting details, then background. Readers can stop at any point and still have the essential message. It is effective for incident reports, status updates, and documentation because busy readers may not finish -- put the answer in the first paragraph, not the last.🟡 Medium (4)¶
1. What are editing passes and why is separating writing from editing more effective than doing both at once?
Show answer
Editing passes means reviewing your draft multiple times, each time focusing on one dimension: structure (is the argument clear?), clarity (can each sentence be simpler?), accuracy (are facts correct?), and concision (what can be cut?). Separating writing from editing works because drafting requires generative, uncritical thinking while editing requires analytical, critical thinking. Doing both simultaneously produces slow, self-censored drafts that are neither creative nor polished.2. What is audience calibration and what is the "curse of knowledge" that undermines it?
Show answer
Audience calibration means adjusting vocabulary, detail level, and assumed context to match your reader. The curse of knowledge is the cognitive bias where once you know something, you cannot imagine not knowing it -- so you skip explanations that seem obvious to you but are opaque to readers. Test: ask someone outside your team to read your draft. Where they get confused is where the curse of knowledge struck.3. What is the Hemingway principle ("write drunk, edit sober") and how does it apply to technical writing?
Show answer
The principle (attributed to Hemingway) means: draft freely without self-censoring, then edit ruthlessly afterward. In technical writing, the "drunk" phase means getting ideas on paper without worrying about perfect phrasing, structure, or completeness. The "sober" phase means restructuring, cutting filler, verifying accuracy, and polishing. The principle works because perfectionism during drafting causes blank-page paralysis.4. What is the "one paragraph, one job" rule and how do you cut filler from technical writing?
Show answer
Each paragraph should serve exactly one purpose: state one claim, explain one concept, or describe one step. If a paragraph does two jobs, split it. To cut filler: remove throat-clearing openers ("It is important to note that..."), eliminate hedge words that add no precision ("basically," "essentially," "in order to"), and delete sentences that repeat what the previous sentence already said. If deleting a sentence loses no meaning, delete it.🔴 Hard (3)¶
1. Why does structuring by logic rather than chronology produce clearer technical documents?
Show answer
Chronological structure ("First we tried X, then Y, then Z") tracks what happened but forces the reader to reconstruct the reasoning. Logical structure organizes by argument: state the conclusion, present the evidence, address counterarguments. Readers care about the answer and its justification, not the journey. Postmortems, ADRs, and proposals all benefit from logic-first structure. Use chronology only when the sequence itself is the point (timelines, procedures).2. What does "kill your darlings" mean in writing, and why is it especially important in technical docs?
Show answer
Kill your darlings means cutting passages you are proud of when they do not serve the reader. Clever analogies, impressive vocabulary, and elegant digressions often serve the writer's ego more than the reader's comprehension. In technical docs this is critical because every unnecessary section increases cognitive load, buries the actionable information, and makes documents longer than anyone will read. If a section is not helping the reader accomplish their goal, remove it.3. How do you diagnose and fix unclear writing when "it just feels off" but you cannot pinpoint why?