If you are writing about a new idea, mechanic, or technology, start with it. Talk about what it is before you start contrasting it with what it isn’t. Start by explaining the new thing and why the new thing is so good.
If the reason the new thing is good is because it’s different from an old bad thing, and you really, really wanna contrast and compare in order to make it super clear how much better the new thing is, I guess you can, but please move that to the end of your article.
It’s difficult to write positively, to write “new first”—we are so trained to tell stories chronologically—but we have the life-changing magic of editing. I need to edit my texts a ton, but that’s how I write: make a mess, then clean it up. This essay you’re reading right now started out just as backwards, just as “bad first”; my first draft of it started with a rant about how the typical Lobsters article is a rough read.
The article writer has invented some new technology, Bar, which is so much better than the old technology, Foo. You’ll never have to use Foo again.
But that’s not how the article starts. Instead, it spends ten pages carefully going over Foo in detail, explaining every nook and cranny, often with a disparaging tone. And then a brief blurb about Bar and why it’s better and use Bar from now on OK bye.
This is lede-buryingly backwards.
For people who do know Foo, we already know all that stuff so you’re wasting our time.
For those who don’t know Foo, well, the entire point of Bar is that you’ll never have to use Foo again so why do you first need to learn about Foo before we can get to Bar?
I feel the exact opposite when it comes to fiction and I am very spoiler averse. If I’m watching something for entertainment, I ideally don’t wanna know anything. I wanna just start the movie and find out as I go. Knowing that a band contributed music, an actor is featured, or what Rotten Tomatoes think of the work all take away delightful discoveries that I would wanna make on my own when seeing the movie or playing the game. Like, I remember seeing a Charlie Kaufman movie (not knowing it was a Kaufman movie) and seeing how it got gradually weirder (and better) and then seeing the director’s name at the end and going “Ah! Of course!” and enjoying it so much more than if someone had told it to me. Same goes with songs like “The Lion’s Roar” at the end of a TV episode can be such a mic drop moment if it’s unexpected.
It’s key to the sense of discovery and exploration that’s a huge part of the appeal to my engagement with art.
So that’s why it’s so important to distinguish essays, articles, academia, manuals, textbooks from fiction. I’ve written about this before, how it sucks that many RPG adventures are written as if they were stories, gradually revealing the mysteries to the GM. No! Bad book! As GMs, we need to know whodunnit right up front so we don’t mess up when running it.
It’s been a year and a half since I wrote this essay and…
A tech essay isn’t a mystery novel. Don’t bury the lede. Give good practice first, and then afterwards go into a “history” or “background” section where you explain what you were doing wrong before and how the new thing is better.