Cormac Mccarthy's Tips on How to Write a Science Paper (2019) [pdf]
Key topics
A 2019 PDF document containing Cormac McCarthy's tips on writing a science paper is shared, sparking discussion on the applicability of his writing advice to scientific writing and the challenges of writing a good science paper.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
2h
Peak period
76
Day 1
Avg / period
38.5
Based on 77 loaded comments
Key moments
- 01Story posted
Sep 20, 2025 at 10:08 AM EDT
4 months ago
Step 01 - 02First comment
Sep 20, 2025 at 12:34 PM EDT
2h after posting
Step 02 - 03Peak activity
76 comments in Day 1
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 30, 2025 at 9:49 PM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
This echoes advice I first read in Strunk & White. It remains the most actionable tip for better writing I'm aware of, technical or otherwise.
Aside: I consider McCarthy's residency at SFI an ideal job
my writing advice:
never use the former and the latter
> Commas denote a pause in speaking.... Speak the sentence aloud to find pauses.
made its way into this article. Hard to imagine that this particular point, to which I might attribute many of the comma splices I see in scientific writing, actually came from a professional writer.
The work makes it worth it, makes it that much more rewarding to me personally. It's like choosing to play a difficult videogame, because you know once you overcome it, it'll be great.
However, I wouldn't take his advice on how to write for clarity. I too often found myself rereading paragraph, "wait is this description or dialogue", "who said that" - this is not what you want in scientific papers
I am reading NC4OM right now and this is not, technically, the case. He does use those “speech tags”.
Though I haven't read any scientific papers, so can't comment on those.
And I must agree. I often feel papers are written with an extra 20% over the page budget, then condensed in the last minute to fit the constraints, which hurts the exposition.
> A designer knows that he has achieved perfection not when there is nothing to add, but when there is nothing to take away.
https://english.stackexchange.com/questions/38837/where-does...
This is rich, coming from the guy that spends multiple paragraphs describing an empty ditch in the desert.
This is a testament to just how multifaceted he was.
- Antoine de St Exupery
And here’s a short article about his contribution to that article: https://andrewbatson.com/2016/12/13/cormac-mccarthys-contrib...
> Find a good editor you can trust and who will spend real time and thought on your work.
Haha, sure, I will send it to my LLM -- ... I mean "editor." :)
I do appreciate the arguments that footnotes can be distracting, or that one doesn't know whether to skip them, but at present I see them as the best option for keeping the main body streamlined/as short as possible without sacrificing points that I'd like to make that wouldn't make for or fit into an appendix.
I disagree. Readers have no way of knowing whether they can be safely skipped or not. Relevant information should go into the main text. If a paragraph starts out uninteresting enough, readers will skip it anyway.
As a non-academic that wrote a paper for the first time, I'll say that writing a good science paper takes an absurd amount of time, even on a topic you are very well versed in. It is also way different than other forms of writing, like blogs or technical documentation.
Frankly, I'm astounded I've even managed to get that result, working on it just one month from the submission deadline (a ridiculously massive time crunch) and only in my spare time, not having touched LaTeX in almost a decade. But if a proper heretic like me managed to get that far on their first try, then everyone who's considering writing a paper for the first time ought to have hope.
I might've somehow got an invitation to present a poster out of this, but that's a story for another day (still wrestling with Inkscape on that one).
So I've worked in my spare time for the past three years on an extremely esoteric and mind-bending reverse engineering technique I call delinking [1] and my tool for it [2] developed a small user-base. At some point I saw in a Discord server a call for papers for the SURE workshop, shitposted that it'd be funny to fry academic brains for a change, then got baited into writing it.
What started out as a long paper (12 pages) with quantitative case studies quickly got cut down to the bone and then some into a short paper (6 pages) that merely introduced my take on it and two qualitative case reports, because I realized it would take an amount of work on the scale of a master's thesis to do the long one. I barely managed to get that out of the door as my usual writing style is extremely unsuited for scientific papers (it took all the might of Gemini and Copilot to even wring out something that vaguely resembles academic vernacular from my first draft). I've submitted it, exhausted and deeply unsatisfied by the compromises I've had to do under that severe time crunch.
Then one month later, the reviews came in. The feedback was that the topic and my take on it were interesting; the criticisms can be summarized by saying that I've missed existing related work and it would've taken the long paper to address all the deficiencies in my paper. Fair I guess, but I definitely don't have that kind of spare time to spare on writing papers.
But alongside the notification decision, something unexpected was also sent: an invitation by the program committee to present a poster at the ACM CCS 2025 conference in Taiwan. This is the kind of world-class conference with a $1800 entry ticket, happening in a convention center whose area is measured in hectares, attended by professional members of an academic, industrial or state organization, all expenses paid in a five star hotel room with a king bed.
Somehow, a hobbyist who can charitably be described as a Doctor Frankenstein but with bits instead of gibs, who creates unholy chimeras of programs in his free time in spite of ABIs and common sense, received an invitation from the Hogwarts School of Witchcraft and Wizardry equivalent of the cyber-security academic world to present a poster. I can't even begin to express how utterly impossible this is.
So of course I said yes and now I'm in a mad dash to get everything ready in time for the conference, three weeks from now. Bonus point: it's on the other side of the planet and in my entire adult life I've basically never got farther away than the next county (and groaning while doing so). There's even more to that story, but I'll leave it for a blog post once it's done.
[1] Others call it unlinking, binary splitting or binary reassembly.
[2] https://github.com/boricj/ghidra-delinker-extension
If you want to take a peek at the case studies, I've blogged about my butchering of aln across C standard libraries and operating systems [1]; there is also widberg's outstanding write-up of their FUEL decompilation project [2], which uses ghidra-delinker-extension as part of the magic.
If you want to read a paper on the technique, there is the one for Ramblr [3] which I became aware of after the reviews came back.
[1] https://boricj.net/atari-jaguar-sdk/2023/11/27/introduction....
[2] https://github.com/widberg/fmtk/wiki/Decompilation
[3] https://www.ndss-symposium.org/wp-content/uploads/2017/09/nd...
You sound like exactly the sort of wizard they want to see!
> Keep sentences short, simply constructed and direct. Concise, clear sentences work well for scientific explanations. Minimize clauses, compound sentences and transition words — such as ‘however’ or ‘thus’ — so that the reader can focus on the main message.
Repetitive sentence structure is not engaging and lulls a reader to sleep, no matter the context. Clauses and transition words and nontrivial sentence structure allow for qualification and clarification, juxtaposition and contrast, and emphasis, often with many fewer words than if written as a series of single independent clauses. A short sentence following longer ones punctuates its point and can effectively lead into subsequent sentences that express more complex ideas/explanations.
In my own scientific writing I also frequently use compound sentences to indicate that the ideas are related (causally or otherwise). It's also unclear to me how one could more efficiently communicate logical or causal flow between ideas than with transition words like "thus" or "therefore."
> short, simply constructed and direct [sentences]
require an honed writing skill; a finely tuned feeling for language, reading flow and contiguous thought; and while time and effort can culminate in such abilities, they shouldn't be prioritized.
It's better to have adept editors who like fiddling--sorry, tinkering, with syntax and semantics.
> Avoid placing equations in the middle of sentences. Mathematics is not the same as English, and we shouldn’t pretend it is.
I don't know what to make of it. Equations are supposed to be part of sentences, and mathematical equations are compact expressions of relations. For example, the sentence,
can be compacted as This becomes more useful with more complex relations. Generally, hanging mathematical expressions (those independent of sentences) should be avoided to the utmost in any technical report.The authors are biologists, so I suspect they're not particularly versed in mathematical writing (and that McCarthy was not likely providing them much advice on it).
There's another piece of advice that is bad for formal mathematical writing:
> And don’t use the same word repeatedly — it’s boring.
If the word has a formal definition, this is bad advice. For example, in a game theory setting, we might say there are n agents. If we start calling the agents players, people, etc., it can get confusing, especially if there are other entities involved besides the agents (such as a mechanism designer or so on).
many early-career folks are afraid to make things too simple and easy to understand because they (subconsciously?) fear that it makes their work seem simplistic or trivial.
when you're an academic that has built a great deal of your self identity around being perceived as 'the smart one', it takes a fair amount self-confidence to start presenting yourself in a way that is easy to understand
[1] https://yelpingwithcormac.tumblr.com/post/11950502897/taco-b...
David Foster Wallace wrote a memorable review of it once in a piece for Salon, which read (in its entirety)
"Don't even ask."[1]
If you've read the book, you know.
[1] The article is "Five direly underappreciated U.S. novels > 1960." https://www.salon.com/1999/04/12/wallace/
So this is why the LLMs do it
7 more comments available on Hacker News