The first NASA document I ever read all the way through was not about rockets. It was about writing.
Every flight has a set of rules agreed long before anyone straps in: what counts as a problem, who is allowed to call a stop, what happens in the minutes after something goes wrong. They are written in advance precisely because nobody trusts themselves to think clearly in the moment. The whole point is to make decisions while you are calm, and then hold yourself to them when you are not.
I keep coming back to that idea, because it is the opposite of how most people write. Most writing happens in the moment. You feel something, you get it down, you hope the feeling survives the trip to the page. That works for songs. It is a terrible way to run a spacecraft, and it turns out to be a fairly bad way to report a story too.
Writing things down is a way of arguing with yourself later
What I like about the flight-rule approach is that it treats writing as a form of engineering rather than a form of expression. A sentence in that kind of document is not there to sound good. It is there so that a person under enormous pressure, reading fast, cannot possibly misunderstand it. Ambiguity is not a stylistic weakness. It is a failure mode.
That is a high bar, and it is not the bar for everything. But it is a useful one to keep in the corner of your eye. When I write a paragraph now I ask a question I picked up from those documents: if someone read this quickly, in a hurry, wanting it to say something else, could they? If yes, it is not finished.
Clear writing is not a polish you apply at the end. It is the evidence that you understood the thing.
Why I want to write about this for a living
There is a version of space journalism that is entirely launches and countdown clocks, and it is genuinely thrilling, and it is about four per cent of the story. The rest is procurement, testing, budgets, the slow accumulation of decisions that mean a thing either flies or does not. That part is written down too. Almost all of it is public. Very little of it gets read.
That gap is the job I want. Not to be at the launch — though I would like to be at the launch — but to be the person who reads the appendix and can explain, in plain language, what changed and who decided it.
It is not a glamorous ambition. It is mostly reading. But the documents are right there, and somebody should.
This is a sample post, written to show how an article looks in this theme. Delete it, or rewrite it as your own — the layout stays the same either way.