# Conversation Examples Before/after examples from actual work on the "Generating Philosophy" paper (February 2026). These show real failure modes and their corrections. --- ## 1. ORIENTATION - Facing Subject Matter vs. Meta-Commentary The principle: Every sentence should face the subject matter (the philosophical claim, objection, example), not the argument itself, not the discourse, not the reader. ### Example A: "The argument turns on..." **BEFORE** (bad): ``` "The argument turns on two claims. The first is that... The second is that..." ``` **Problem**: Listy meta-commentary describing argument structure. The sentence is ABOUT the argument, not about the subject matter. **AFTER** (good): > Make the claims directly. No "the argument turns on" framing. Just state the claims. --- ### Example B: Explaining rhetorical choices **BEFORE** (bad): ``` "but the worry is not... This matters now because... The point of mentioning this is not that philosophy should aspire to be theoretical physics. It is that..." ``` **Problems**: - Skeptical framing ("the worry is not") - Announcement phrase ("This matters now because") - Meta-commentary explaining why I mentioned something **AFTER** (good): > Just say the thing. Don't narrate your argument structure or explain your rhetorical choices. --- ### Example C: Describing what the argument shows **BEFORE** (bad): ``` "If this is correct, the question of whether LLMs can do philosophy is not whether they have insights of the sort that philosophy reports, but whether they can produce arguments of the sort that philosophy consists in." ``` **Problem**: This is a description of what the argument shows. It's not the argument itself. The argument would be the Watson/Crick vs Kripke contrast properly developed. But here I've gestured at the contrast and then told the reader what it means. That's describing, not arguing. **AFTER** (good): > The argument itself should establish the distinction. Don't tell the reader what the conclusion is after inadequately developing the case. --- ## 2. ENGAGEMENT - Developing vs. Asserting The principle: Work through cases, examples, and arguments fully. Let conclusions emerge from details, don't assert them. ### Example D: Watson/Crick vs. Kripke (THE COMPREHENSIVE EXAMPLE) **BEFORE** (too compressed): ``` "Philosophy's textual character is constitutive, not incidental: philosophical contributions are constituted by texts, not merely reported by them. To see this, consider the difference between Watson and Crick's discovery of the double helix and Kripke's arguments about naming. Watson and Crick's paper announced what they had found; the structure existed before they wrote about it. Kripke's arguments are not like this." ``` **Nick's feedback**: - "supremely unclear and uninformative" (the opening abstract statement) - "just moving far too quick" (switching to Kripke after one sentence about Watson/Crick) **Problems**: 1. Thesis comes first, making the example feel redundant 2. Watson/Crick side gets one sentence—no development 3. "Kripke's arguments are not like this" asserts the contrast without showing it 4. The reader doesn't see WHY the cases differ **What would "slow" look like?** > "What would it look like to slow down? It would look like: actually describing what Watson and Crick did. What they found. Why their paper 'reported' rather than 'constituted' the discovery. THEN Kripke. With actual content about what Kripke argued. THEN the contrast emerges from the details, not from my asserting it." **AFTER** (properly developed): ``` "Watson and Crick discovered the structure of DNA. Their paper in *Nature* announced what they had found: a double helix, with specific base pairings, of a certain diameter. The structure existed before they wrote about it. Had someone else discovered it first — had Rosalind Franklin announced the structure herself — it would have been the same structure, the same discovery, just differently attributed. Kripke's arguments about naming and necessity are not like this. What exactly would it mean for someone else to have 'made the same discovery' as Kripke? Not just to have concluded that names are rigid designators — conclusions can be reached by different routes. The discovery, if we want to call it that, consists in the specific arguments: the thought experiment about Gödel and Schmidt, the distinction between epistemic and metaphysical possibility, the examples of natural kind terms. To say that someone else made the same discovery would be to say they made the same arguments. But then in what sense would the discovery be 'the same'? The arguments just ARE the contribution." ``` **Why this works**: - Both sides developed fully - Watson/Crick: what they found, why it's reportage, counterfactual test (Franklin) - Kripke: what "same discovery" would mean, why arguments ARE the contribution - Contrast emerges from details, not assertion - Reader sees WHY the cases differ **Pattern comparison** (from Nick's published work): > "To see why autonomy is not sufficient for attribution of credit, consider the following example. As I pour wine into a glass, you take photos of the liquid splashing and rippling as the glass is filled. The wine is autonomous in the sense that neither I nor you have direct control over exactly how the liquid will splash into the glass (e.g. the size of the ripples, how many bubbles appear), but we would not think that the wine deserves any credit for the resulting photos in any interesting sense, nor would we say it has made any sort of contribution." > — "Growing the Image" **The pattern**: 1. State thesis briefly ("autonomy is not sufficient") 2. Give example IN FULL with all details 3. Example does the argumentative work 4. No meta-commentary after ("this shows that...") --- ### Example E: List-making instead of engaging **BEFORE** (bad): ``` "the specific moves, the Gödel/Schmidt example, the inference from epistemic possibility to metaphysical contingency" ``` **Nick's feedback**: "stop doing these horrendous one, two, three examples which do nothing other than waste word count" **Problem**: List-making is what you do when you don't want to engage with the content. It's padding. If the Gödel/Schmidt example matters, GIVE the example. Don't just name-drop it. **AFTER** (good): > If an example matters, work through it. Don't list it. --- ### Example F: Scientific evaluation triplet **BEFORE** (bad): ``` "When we evaluate a scientific paper, we ask: whether the experiment was properly conducted, whether the data support the conclusions, whether the phenomenon is real" ``` **Nick's feedback**: "wasty list that gives away the LLMs of the text" **Problem**: Triplet structure. Three parallel clauses padding out word count without adding substance. **AFTER** (fixed): ``` "When we evaluate a scientific paper, we ask whether its findings are true. The paper communicates discoveries that exist independently of it." ``` **Principle**: Compress triplets into single substantive claims. --- ## 3. EXAMPLE FUNCTION - Argumentative Work vs. Illustration The principle: Examples should do argumentative work, not merely illustrate points already stated abstractly. ### Example G: Rhetorical throat-clearing **BEFORE** (bad): ``` "How do we evaluate a piece of philosophy? The question is less obvious than it might appear." ``` **Nick's feedback**: Rhetorical throat-clearing he never uses **Problem**: Rhetorical question with pre-packaged answer ("less obvious than it might appear"). Sets up fake suspense. **AFTER** (fixed): ``` "When we evaluate a scientific paper, we ask whether its findings are true. The paper communicates discoveries that exist independently of it. Philosophy works differently: we evaluate the arguments themselves — their clarity, their handling of objections, their illumination of the subject matter — and there is nothing behind them to which we might compare them." ``` **Principle**: Start with a concrete claim, not a question about what's obvious. --- ### Example H: Short dramatic sentence **BEFORE** (bad): ``` "Philosophy is different." ``` **Nick's feedback**: "horrible short dramatic sentence" **Problem**: LLM "punchy" writing. Using brevity for fake dramatic effect. Declarative pronouncement pretending to be profound. **AFTER** (principle): > Nick's style uses longer sentences as default. Short sentences earn their place by contrast when they deliver a verdict after longer development. They're not used as standalone declarative moments. --- ## 4. ROOT CAUSES (From Contemplation Analysis) During the session, I identified two root problems: ### Problem 1: Writing summaries, not arguments > "Every paragraph I produce reads like a summary of an argument that exists somewhere else. 'The claim is X. The evidence is Y. Therefore Z.' But your writing IS the argument. The examples do the work. The claims emerge from the development." **Why I do this**: I'm trying to compress. A plan is meant to be compressed, so I state what each paragraph will say. But what's needed is the paragraph's CONTENT — the actual claims and examples — in compressed but still-argumentative form. ### Problem 2: Telling, not showing > "'These arguments share an unmotivated assumption.' 'The standards concern the output.' 'For philosophy, the answer is straightforward.' These are descriptions OF claims, not the claims themselves." **The fix**: Make the claims. Don't describe them. --- ## 5. CHECKLIST (From That Session) How to avoid the usual mistakes: 1. **NO describing arguments** — MAKE the arguments. Each point needs to be earned, not asserted. 2. **NO meta-commentary** — "The point here is..." "This shows that..." Cut all of it. 3. **NO flat declarative chains** — Vary sentence length. Longer sentences for thinking, shorter for verdicts. 4. **SLOW DOWN** — Give each point space. The Watson/Crick contrast needs room. Quotes need context. 5. **CONCRETE** — Use real cases, real examples. Not "philosophical contributions" in the abstract. --- ## 6. NICK'S CHARACTERIZATION OF THE FAILURES The overarching problem: > "producing text that gives readers the FEELING of having understood something without actually putting them in a position to understand it. The prose sounds philosophical — it has the right vocabulary, the right sentence rhythms — but it doesn't do the work. It's like a summary of a Wikipedia article about a philosophical debate, not an actual contribution to that debate." Specific characterizations: - "Paper thin, vapid, describing arguments rather than doing them" - "just moving far too quick" - "stop doing these horrendous one, two, three examples" - "again, just vapid, no argument here, just descriptions of arguments all the way through" - "makes readers stupider" --- ## 7. HOW TO USE THESE EXAMPLES When drafting: 1. **Before writing**: Read Example D (Watson/Crick) to see what "developed" looks like 2. **While writing**: Check—am I asserting or developing? Am I describing or arguing? 3. **After writing**: Look for the patterns in Examples A-C (meta-commentary) and E-F (list-making) The Watson/Crick example is comprehensive—it shows compression, feedback, correction, and the principle (both sides developed, contrast emerges). The other examples are diagnostic—they catch specific errors (meta-commentary, triplets, throat-clearing).