The ULTIMATE Crossover: The Hogwarts Houses Of Your Favourite Star Trek Characters!

The results are in! The Sorting Hat has spoken! Starfleet’s best have been Sorted!

In the world of J. K. Rowling’s Harry Potter, students at Hogwarts School Of Witchcraft And Wizardry get sorted into one of four houses – brave Gryffindor, cunning Ravenclaw, caring Hufflepuff or ambitious Slytherin.


If you’re a Harry Potter super-fan, you probably already know which house you’d be in – but what about some of your favourite fictional characters?

For all of you Star Trek-lovers out there, we decided to try and figure out just which Hogwarts House some of the most iconic Trek characters would be sorted into. Will they Gryffindor-ly go where no Wizard has gone before?

Let’s find out!

Sylvia Tilly


Tilly has been a big hit with Star Trek fans since her introduction in ‘Star Trek: Discovery’, and has established herself as a firm fan favourite! But how would she get on in Hogwarts?

Well, we think Tilly is a classic Hufflepuff! She’s warm, kind, and she loves to look out for her friends. She’s always optimistic and thoughtful, and she always works hard and treats everyone she meets fairly.

The Sorting Hate Says: Hufflepuff!

Leonard ‘Bones’ McCoy


Bones has been a grumbling, grouchy, lovable icon of Star Trek since the very beginning, and almost everyone is familiar with his forthright demeanour and his oft-recalled catchphrase “I’m a doctor, not a…”

McCoy’s medical credentials make him a firm fit for Ravenclaw. But his devotion to healing, his unswerving loyalty to Kirk, Spock and the crew of the Enterprise, and his fondness for just sitting down with a good bottle of something strong and shooting the breeze with and old friend make him the perfect candidate for one house in particular.

The Sorting Hat Says: Hufflepuff!

Benjamin Sisko


Ben Sisko is the third captain (or should we say commander?) to get his own series, and he’s one of the more popular captains owing to his complexity and the strong values he represents.

On the one hand, Sisko’s incredibly brave, like a Gryffindor, but he also has an intellectual side, and a degree of cunning. But ultimately, his most defining traits were his love of his family and his friends, his passion for cooking, and a tireless work ethic coupled with generosity and a firm belief in playing fair and being honest. Which leads to only one real choice…

The Sorting Hat Says: Hufflepuff!

Kathryn Janeway


Captain Janeway was Trek’s first female captain to get her own series, and she made quite the impression. Her cool head, focused intellect and ingenious solutions to complicated problems made her stand out as one of Starfleet’s finest.

Janeway was fearless under fire, and never afraid to confront an injustice. That said, we often see her enjoying her homely comforts – a good pot of coffee, a nice hot bath, an intriguing period holonovel. She always made sure to take care of all of her crew, even going so far as to personally take time out to help three lower decks officers who were struggling to fit in. It’s these kinds of traits that really left a mark, and that defined her most as a character.

The Sorting Hat Says: Hufflepuff!

Jean Luc Picard


With his fine, clipped accent, assertive leadership style and unwavering determination, there is no equal to the likes of Jean Luc Picard. Captain of the Enterprise through all of The Next Generation (and now getting his own show!) Picard is one of the most recognisable and widely-loved characters from all of Star Trek.

Picard really could go to any House- he’s bold and courageous like any good Gryffindor, but also ambitious, and calculating when necessary, as would be expected of a Slytherin. He’s academic, studious and focused. But at heart, he’s a noble gentleman with refined tastes. From classical music to his favourite drink – tea, Earl Grey, hot! From his dedication to archaeology to his tireless diligence, from his speeches on honesty and fairness to his absolute and flawless loyalty to his crew, there can only really be one House where Picard would truly find his potential.

The Sorting Hat Says: Hufflepuff!



If there is one character that is synonymous with Star Trek, it’s got to be Mr. Spock. Every aspect of his appearance, from his ears to his hair to his eyebrows, is woven into the legacy of Star Trek. His philosophies and his Logic are part of Star Trek’s soul, and we wouldn’t have it any other way!

A being of logic, learning, ingenuity and rationality, it’s pretty clear straight away where Spock belongs in Hogwarts. Whether he’s playing his Vulcan lute to entertain his shipmates, decorating his quarters with beautiful artwork, or just sitting around a campfire and singing old songs with old friends, you probably don’t need us to tell you to which House Spock belongs…

The Sorting Hat Says: Hufflepuff!



Arguably one of Trek’s most successful break-out characters, Quark is a bit of an oddball. A Ferengi to the core, Quark is defined best by his bar aboard Deep Space Nine, and by his family – Nog, Rom and Ishka (or “Moogie”) who frequently drive him up the wall – but whom he nevertheless remains loyal to.

Quark’s a bit devious at times, and ambitious to a fault. But he works hard, and is dedicated to the comfort and enjoyment of his customers.

But with all that said, at his core, Quark is bold, and ready to stand up for what he truly believe is right. Time and again he overcomes his fears, sticking his neck out to save the Ferengi economy, fighting for his Klingon bride, even taking on the brutal Jem’Hadar when he needs to. For all of these reasons, we think there’s only one place for Quark.

The Sorting Hat Says: Gryffindor!

That’s all we’ve got time for today! We hope you enjoyed our take on Star Trek Hogwarts Houses!

Didn’t see your favourite character here? Think a different House would suit one of the characters above? Let us know in the comments section! We’d love to hear your thoughts!

‘Star Trek: Discovery’ Courts Chaos With ‘An Obol For Charon’

Quick Announcement:

The Great Big Crude Star Trek Survey Is Open!

All answers are appreciated, and every response will help build insight into the world of Star Trek and its fans. For more info, follow this link.

Now, back to our scheduled feature.

I believe it was William Shakespeare who said:

“Brevity is the soul of wit.”

Well, I would like to offer a complimentary notion:

“Restraint is the heart of genius.”

What does that mean?

Allow me to explain.

As this is another long article, I’ve added an abstract (AKA a synopsis, a summary, or a TL:DR) below. The rest of the article follows it.

‘An Obol For Charon’ contains many interesting story ideas, many of which have been explored in previous Star Trek series. Sadly, it packs too many of these concepts in, such that no one story arc receives adequate focus. This lack of narrative focus leads not only to many significant plot holes, but also to several crucial oversights in the relationships between characters.

Chaos By Parts

My initial review of ‘An Obol For Charon’, the fourth episode of the second season of ‘Star Trek: Discovery’, was going to be a breakdown of each of the many subplots of the episode, exploring each one separately. It seemed like a sensible way to tackle the chaos of such a busy episode, barely 50 minutes long.

But then I realised that what I want to talk about is the chaos. Not the in-universe chaos, as the ship shuts down and everything goes wrong, but the narrative chaos, caused by inexpert hands duct-taping six contrasting narratives into a big, quivering, unstable blob that wants to collapse under its own weight like a beached whale.


In a previous article, I commented on the similarities between ‘New Eden’ and TNG’s ‘Q Who’. I try very, very hard not to compare DISCO to other Trek series in terms of aesthetics, technology, canon and the like because those things just aren’t as important to me as the stories themselves. But when DISCO itself invokes the comparison, I’ll take it and run with it.

‘An Obol For Charon’ is, on the surface, directly comparable to TNG’s ‘Disaster’ – in both episodes, the ship (Discovery, Enterprise) is rendered helpless by some cosmic phenomenon and chaos ensues, leaving the crew separated, imperilled, and without access to any of the technology they would usually rely on to help them out.

‘Charon’ is also directly comparable to TNG’s ‘Ethics’ – in both episodes, a character (Saru, Worf) is left with some kind of debilitating and incurable medical condition to which their cultural response is suicide, and they must request the assistance of other crew to help them kill themselves.

‘Charon’ is ALSO reasonably comparable to DS9’s ‘Heart of Stone’, in which a character (Tilly, Kira) is trapped by a strange, lumpy lifeform and another character must find a way to save them, whilst cut off from any help or medical assistance.

This plotline itself invokes elements of both of the TNG episodes ‘Evolution’ and ‘Force of Nature’, where, respectively: the crew channel the communications of an alien race through a “possessed” crew member (Tilly for the JahSepp and Data for the Nanites) in order to negotiate a kind of truce; and where the crew discover that their heretofore vital engine technology is unknowingly causing environmental damage which is affecting an alien race.


In addition to these narratives, we also have the meta-plot of the Red Bursts and the Red Angel, the meta-subplot of Spock’s escape, and the meta-sub-subplot of the rift between Burnham and Spock preventing them from reuniting.

Finally, we have the A-plot of this episode, which is a massive, quivering, unstable blob that wants to die, but not before it sends someone its internet search history. This borrows elements from TNG’s ‘Tin man’ and ‘The Inner Light’, the first about a massive, living vessel seeking to die, and the second about a an ancient probe forcibly passing on the history and cultural legacy of  to the first ship it encounters.

Got all that?

Good! Now let’s talk about why it doesn’t work.


‘Disaster’ is probably not one of the finest episodes of TNG, but it’s far from the worst, and manages to be memorable thanks to some fun and touching moments throughout.

Structurally, ‘Disaster’ is essentially a collection of B-plots. There isn’t really an “A-plot” – that being, a story arc which serves as the main focus of the episode, and that’s actually fine.

The Enterprise randomly strikes two quantum filaments – a kind of string that is cosmic but that is definitely not a cosmic string.


This occurs at the end of the four-minute opening teaser, following a sequence of scenes in which we see the crew in “status quo” – the unborn Molly O’Brien is torturing Keiko by kicking, Beverly is torturing Geordi by begging him to sing, and three children are torturing Picard by existing.

Everyone is separated off into little groups: Beverly and Geordi are in a cargo bay; Riker, Data and Worf are with Keiko in Ten Forward; Troi and O’Brien are on the bridge; and Picard is in a turbolift with the three children – for those of you not aware, Jean Luc Picard hates children as much as Michael Burnham hates making sensible decisions.

The Enterprise is hit with the filaments, and the following things happen:

  1. Worf is left in charge of Ten Forward, which has become a makeshift medical bay, and must assist Keiko as she goes into labour.
  2. Troi and O’Brien are joined by Ro Laren in an isolated bridge, cut off from the rest of the ship and uncertain about the next steps to follow.
  3. Picard faces his own Kobayashi Maru, being trapped in a turbolift with a broken leg and three useless fucking children. Everyone thinks that ‘Chain of Command’ is the episode about Picard getting tortured, but this is actually the greatest torment he ever faced.
  4. Riker and Data set out to reach Engineering in order to regain control of the ship, but must find away around damaged corridors and passageways.
  5. Bev and Geordi are trapped in the cargo bay and discover a plasma fire, which is steadily poisoning them with radiation.

The key thing with all of those subplots is that they’re all actually pretty basic. Riker’s and Data’s journey is mostly just functional, and serves as the resolution to the overall peril, and Beverly and Geordi’s subplot is mostly just generic danger plot to give them something to do.


The other three stories are more interesting:

  1. Keiko’s labour is fairly standard, but it presents Worf a problem that he can’t fight, shoot or stab – if Beverly were around the issue would be solved.
  2. Troi struggles with the burdens of command, having to get the other officers into line and make difficult decisions. She really just needs a command officer like Riker or Picard around to sort the problem out.
  3. Picard has to find a way to stop the children from panicking or giving up or succumbing to fear – he needs Troi, someone who can reach the children on an emotional level and keep them calm.

And that’s basically it. None of these things would be major problems on any other day – they’re only challenging because of the complete failure of all of the ship’s systems. Without those issues: Geordi and Beverly could just beam out of the cargo bay; Data and Riker could just take the turbolift; an actual doctor could take care of Keiko rather than Worf; Troi could just get guidance from a more senior officer; and Picard could just pistol-whip those little shits right in the face find someone, anyone, to take those children off his hands.


For the Worf, Picard and Troi stories, it’s just a chance to see our characters out of their comfort zones, facing new challenges that could be easily dealt with otherwise. And we even get nice little arcs out of it:

  1. Worf learns to embrace his softer, more sensitive side as he coaches Keiko through the birth of Molly.
  2. Troi gains confidence dealing with life-or-death decision-making, and asserting herself within the Starfleet hierarchy.
  3. Picard realises that children probably aren’t all that bad, and even comes to appreciate the hidden strength youth or whatever.



There’s an old joke about how unlucky each vessel bearing the name Enterprise must be. Every week the crew meets some new, terrible, or just plain weird phenomenon which fucks everything up, and it seems to happen like clockwork.

Well, Enterprise got nothin’ on Discovery. In this episode alone:

  1. The crew are on a mission to investigate a weird galaxy-wide phenomenon.
  2. Number One comes aboard to give Pike an update on the investigation into Spock, who is wanted for murder after allegedly losing his mind. Number One points out how fishy this investigation is.
  3. Burnham doesn’t want to meet Spock when they do find him, due to a previous falling out.
  4. The ship runs into a giant living entity which completely mangles the computer –
  5. – which leads to all of the crew speaking different languages because of a Universal Translator function.
  6. The only way to free the ship is to accept a massive download of 100,000 years’ worth of information, because the living entity wants to die, but not before it passes on its legacy.
  7. The encounter with the living entity causes one of the crew members to enter their own death cycle –
  8. – which requires another crew member to help them commit suicide.
  9. Three crew members get trapped in Engineering with no way to escape.
  10. The compartment is charged with 100GeV of energy (that’s about 0.000000016J, or roughly the kinetic energy of a grain of sand travelling a speed of 1 millimetre per second) and the people inside have to discharge it somehow.
  11. One of those trapped crew members becomes infected with an inter-dimensional fungal parasite.
  12. One of the others drills a hole into the infected crew member’s head with a cordless drill so that they can communicate with the infecting organism.
  13. The organism infected the crew member in order to force the ship to stop using its special engines, which are devastating the organism’s ecosystem.

That’s not even a list of events, that’s just a list of plot threads. Now, in a longer, multi-episode narrative like DISCO’s, you can get away with running parallel stories which take longer to resolve, so for clarity, I highlighted all of the stuff that’s introduced in this episode in red.

You’ll notice that’s nearly all of it.


What’s more, hardly any of these things are small problems. They’re all major issues which could warrant major exploration. Hell, most of them could be A-plots for a single episode.

Instead, we rush through each one without paying any level of notice to it. Here’s a few problems that are NOT adequately dealt with in the course of the episode (numbered correspondingly):

  1. We barely spend any time on the Red Angel / Red Burst phenomenon beyond a single scene in a conference room in which everybody makes clear that, after four episodes, they still have no idea of what they’re dealing with.
  2. Where did Number One come from? Did she leave the Enterprise and travel all this way to have a two-minute conversation with Pike, hand him a data pad, eat a Happy Meal and then leave again? Where did she go after she left?
  3. Burnham refuses to meet Spock because of the rift between them. Rather than introspecting and exploring her feelings on this, or how the rift occurred, she simply decides to see Spock because a dying Saru told her to.
  4. What is the nature of this living cosmic entity? What kind of creature is it? What is its purpose? Is it a vessel? Was it built, or did it evolve naturally? What does the existence of this kind of creature mean scientifically? Is it unique or are there more of them out there? How has it not been discovered before this episode?
  5. Can the Universal Translator really change the lip movements and intonations of the person who’s speaking? And why isn’t the solution to simply deactivate it across the ship so that everyone can at least understand what they themselves are saying?
  6. Why does the entity want / need to die? What is its motivation behind ending its own life? If its death cycle is out of its own control, then is there any way to save it?
  7. Saru starts dying because the entity triggers some sort of death process in Kelpien anatomy, and yet the first symptoms of this process occur at least several minutes before the Enterprise even sets out on a course that would intercept the entity – before Number One even sets foot aboard Discovey with the co-ordinates to which they are heading.
  8. Burnham has to help Saru kill himself, but although she get upset and they have several long conversations, at no point does she question the ethics of her actions, or indeed whether Saru can be saved. Saru says that that his death is certain, but nobody even doubts him – they all just take him for his word and allow him to continue dying.
  9. Reno, Stamets and Tilly, all highly-qualified engineers, get trapped in the Spore chamber and never seem to think of trying to get out – they make mention of the room being completely isolated, but even when Tilly has a fungus attached on her arm, drugging her with hallucinogenics, they never thing to just cut the door open to get her to sickbay – or even just find a way to get a doctor in with them.
  10. The compartment is charged with electricity, threatening to kill them all by incineration as a result of their oxygen igniting. To solve this, they improvise a technique to discharge the energy – which creates a massive blast and electrical bolt. Which would surely ignite the oxygen in the room, which is precisely what they’re trying to avoid.
  11. At the end of last episode, Stamets extracted the parasite from Tilly with the Dark Matter chamber. For some reason, that never emerges as another possibility, even though it seemed to work pretty well.
  12. The situation is so bad that Reno and Stamets decide to improvise brain surgery on Tilly by drilling a hole in her head. This entire scenario is so awful that I was laughing uncontrollably – Stamets’ delivery of the line “We’re gonna do this old school. We need to sterilise that drill bit,” is delivered with perfect comic timing. Even at this drastic stage, neither one of them considers even trying to get Tilly in front an actual doctor.
  13. Discovery‘s Spore Drive is wreaking havoc on an ecosystem in another dimension. What kind of havoc is it wreaking? Why would the organism emotionally manipulate Tilly and mess with her head so much just to “build up trust” in order to “persuade her to deliver [the] message” to Stamets instead of just telling Tilly what was going on? If it can read Tilly’s mind and memories so accurately, would it not be able to recognise her concern for alien life forms? If it understands Tilly well enough to know how to manipulate her sympathies, why would it then choose to appear as a ghost in order to build trust? Would it not be obvious that Tilly, indeed any human, would immediately mistrust visions of a dead person?

Narrative focus is important. Not just to stop assholes on the internet from pointing out plot holes in your story, but because it enables a deeper exploration and examination of the themes that your story covers.

There’s a single line in this episode that is really interesting to me, which is from Saru, regarding his own species:


Now, that’s a fascinating a concept – that the Kelpiens simply submit to death, that they lack the desperate drive for survival that exists in nearly all other species.

It’s an intriguing philosophy! And this is all the screen time it gets this episode. In the similar story ‘Ethics’, from TNG, Riker can’t bring himself to accept that Worf would seek to take his own life when he was physically handicapped, and that drove a lot of the debate of the episode.

To her credit, Burnham simply accepts that Saru is submitting to death, which makes her a considerate friend and which also fits her expertise as a Xenoanthropologist. But it also robs the storyline of the drama it needs! It would be a great point of conflict to see Burnham struggle to come to terms with Saru on this, unable, at first, to accept his perspective on his own situation.

It’s alright Burnham, it’s just us, and we already know you’re smart, you can just say “a million”.

On a similar note, at one point Burnham stops by Engineering to “see if we can find a way to boost power to shields.” She can’t get in, because the doors won’t open. Nobody suggests breaking through them, or finding some other way in or out. Then Stamets says something that helps Burnham realise the solution to the Catastrafuck Of The Week and the point is that:

Tilly is Burnham’s best friend.

However, Burnham shows barely more than cursory concern for Tilly’s plight because she has to go back to being concerned about Saru. Because this episode is a mess.

Little-known fact: this line was originally written for Riker.

Saru is dying. Tilly is being poisoned by an inter-dimensional fungus. The whole ship is on its arse. Burnham doesn’t have time to be worried about Tilly. But she should, because this is one of the most important relationships between two characters in the show so far – the one that we, the audience, have been following since Season 1. But now Tilly’s just the latest entry on Burnham’s list of “Today’s Bullshit.”

To the point that once the cosmic machine entity has released its hold on Discovery, Burnham doesn’t hurry to Engineering to try to help Tilly – she walks Saru back to his quarters so he can take his shirt off and lie down on a bed of moss.


And when it then turns out that he’s fine as his condition just suddenly corrects itself, Burnham still doesn’t go to check on Tilly, but instead follows the now totally-fine Saru to sickbay to congratulate him on not being dead. Then Burnham still doesn’t go to check on Tilly, but instead heads to Pike’s ready room to tell him that she will, at least, decide to speak to Spock when they finally meet, and by this point Tilly has been dragged into a fungal cocoon and off into the Phantom Zone, and Reno is slapping the magic mushrooms out of Stamets as they trip balls.


By this point, the ship is working again, so there’s absolutely no need for Reno and Stamets to be dealing with Tilly’s situation alone. It just seems that nobody else can be arsed to come help – particularly not Burnham, who is off talking to Pike about her family issues.

This is all a result of the episode’s writers trying to cram so many storylines into one place that everything starts falling apart.

And I haven’t even come close to talking about the weird edits and scene transitions as Burnham just seems to teleport around the ship as needed, nor the complete abandoning of the Universal Translator problems which would themselves have been a great storyline.

Or indeed why Pike sees fit, during a period of crisis where the ship might be destroyed, to abandon the Bridge and visit Sickbay to get a status report, the very definition of an errand which could be left to pretty much anyone except the captain. Or why he then chooses to remain in Sickbay for a prolonged period to act as an unqualified nurse.

Ah yes, Pike, that certainly sounds like a captain-worthy task. Couldn’t they just write you a note?

On the surface, this was a fun episode that seemed like a throwback to classic Trek. But again, as with all things ‘Discovery’, it doesn’t take much scrutiny before it starts to dissolve into abstraction and nonsense.

The wrtiers’ inability to restrain themselves is their own undoing, and it allows them to turn some fascinating story concepts into rushed, glossed-over narrative dead-ends. This episode should just have been about the massive cosmic entity and the effect that it’s dying had on Saru – it didn’t need all of the other gumpf, fluff and nonsense to make it interesting.

The only outstanding positive element of this episode was Jet Reno, who remained wonderful throughout. But sadly, she wasn’t enough to single-handedly turn everything around.


Okay, I’ve talked about all the serious, in-depth issues with the episode. Now for more nitpicking:

Burnham comments that the attack is “slow” and therefore “inefficient”, even though the entire ship was multi-spectrally fucko’d seconds after arrival and they’re now completely helpless. SEEMS PRETTY EFFICIENT TO ME.

Stamets asks Tilly to sing her favourite song, so she starts singing ‘Space Oddity’… half-way through. Like, in the middle of a verse. Presumably she knew how cramped the episode was, and so decided to just skip to the most dramatically fitting part of the song.

It really, really bothers me that Stamets claims the Federation is completely dispassionate about the problems caused by dilithium mining. Sure, this is a (really hamfisted) analogy for anthropogenic climate change, but you expect a nation of genius scientists to be a little more switched-on than that.

Reno says that the computer sealed the doors because of the power overload… even though the lightning bolts are shown, clearly, four times over, striking the control panels. Which is both weird for them to do that, and directly contradictory. Neither explanation explains why they can’t leave the room later, beyond the general systems malfunction, except that YOU’RE ENGINEERS, JUST FIND A WAY TO OPEN THE FUCKING DOORS, NUMB NUTS.


No, seriously, where the fuck did Number One come from and where did she go? Was Discovery really in transporter range of Spacedock where Enterprise is being repaired?

What the fuck is a “digital antibody” anyway? ‘Cause it sounds fucking stupid.

Why was the Spore Drive room completely unaffected by all of the ship’s malfunctions? Isn’t it an integral part of the ship? It makes sense that it’d be firewalled off, but then why aren’t other vital areas?

Linus the Saurian is an annoying fucking dweeb and it really bothers me that these futuristic space scientists talk like American teenagers. “That cold I had sucked.” Yeah, so do you, Linus, you god damn scaly-skinned piece of shit.

Pike was bound by his “oath and conscience” to honour the dying wishes of the mechanical entity – risking his ship and all of his crew getting ultra-fucked out of existence in the process. Fuck you, Pike.


Christ, I’m still barely done, but I’m nearly at 4000 words. This’ll have to do for now. Good night.

The Great Big Crude Star Trek Survey

The Great Big Crude Star Trek Survey can be found here! All responses are valued and appreciated!

The Star Trek fandom is a diverse and divisive bunch. We all love Star Trek, but none of us can quite agree on which bits of it we love.

Some of us grew up on the Original Series and Kirk’s adventures aboard the Enterprise. Some of us only got into the show recently, and are bingeing our way through the entire back catalogue.

Some of us are more casual fans, dipping into the franchise only occasionally, whilst others are hardcore Trekkies, attending conventions and getting into arguments on the internet with other hardcore Trekkies because how can somebody not understand that Rachael Garrett is actually the best captain?

To try and get a little clarity out of a chaotic subject, I’ve turned to The Scientific Method. It’s the only Logical way.

I have put together the Great Big Crude Star Trek Survey – a collection of 26 questions (most of them serious) querying your views not just on Star Trek, but on broader topics in the world of TV and movies.

There’s no judgement attached to any of the questions – if your favourite series is the Animated series and your favourite character is Okona, nobody’s going to judge you. I mean, I’ll judge you, silently, as I read through the results. But I won’t know who you are, so it’s fine.

This data is completely anonymous and is being used solely for research purposes. CrudeReviews (i.e. me) has no connection or affiliation with any corporation or organisation of any kind – this is a one-person operation, run in my spare time, and completely non-monetised. I get nothing out of this survey beyond a sense of smugness as I see everyone’s terrible choices.

Once I’ve gathered enough responses, I’ll share all results – including spreadsheets with the raw data – on this website, and may carry out further analysis as more results come in.

I won’t be getting any personal data about anyone who answers, and I’ll be carefully filtering all data prior to release to absolutely 100% ensure anonymity.

If you have any questions, please feel free to leave a comment below, or on the CrudeReviews twitter, or on the CrudeReviews Facebook page, both linked below, and I’ll happily answer.

CrudeReviews on Facebook

CrudeReviews on Twitter

One final note – a handful of the questions are intentionally provocative, relating to social / political issues. All of these bar the first are intentionally left optional, and all are intended to be as open to all viewpoints as possible within the limits of a multiple-choice survey question. If answering these questions would make you uncomfortable, or if you think they don’t sufficiently describe your opinion, please feel free to skip them – that said, responses to these questions are of particular interest, so if you can answer them honestly, please do.

Star Trek: Discovery’s ‘Point Of Light’ Returns To Fractal Stupidity

CONTENT WARNING – The bottom portion of this review contains disturbing images of mutilated infants. A second warning will be put up, but please proceed with caution.

And no, I can’t believe I have to write that warning on the review of a Star Trek episode, either.

Ohhhhh my God. Jesus. I was just, just, warming up to this show, and then BAM, it covers itself in stupid-sauce and jumps into a nest of stupid-wasps and then tries to numb the pain with a hefty dose of stupid-pills.

Did any of that make sense? No? Then I’ve set roughly the correct tone for a review of this toasty, grisly mess of a story.

This episode, ‘Point Of Light’, is what I’d call Fractally Stupid – it’s stupid on a basic, high level, but as you dig further into it, you realise that the stupidity extends to a greater and greater level of detail. It’s stupid all the way down – the closer you look, the more stupid you see.

It’s painful.


My first complaint with this episode is that it’s nearly 50 minutes long and has roughly 90 billion storylines, none of which overlap. Given that fact, I’m going to make it easy for myself and break each one down, and carefully explain why each story is dumber than a bag of hammers.

Please note that there is so much stupid in this episode that I had to trim out a lot of it from this article. There’s also a lot of stylistic stuff, such as camera angles, dutch angles, terrible lighting, Klingons speaking English unintelligibly, the complete abandoning of several plotlines from last season, most notably the planet-destroying bomb that L’Rell controlls, L’Rell naming herself Khaleesi – the list goes on and on.

For now, I just want to focus on the chunkiest narrative aspects. Let’s dive in.

Michael Burnham: An Accessory To Spock

Alright, so we open with Burnham’s personal log, where she explains that she is yet to figure out the significance of the Seven Red Bursts-


Wait, shouldn’t that be Eight Red Bursts? Wasn’t the one in last episode a new one?


Did the writers just try to Shelby us again?

Anyway, Burnham can’t make any headway on the Red Bursts, not even with the help of Spock’s notes.

Where is Spock? Why, he’s in the psychiatric unit aboard Starbase 5. Which is precisely why Discovery went straight there after the end of last episode, where they established the absolute primacy of their mission, over and above Spock’s privacy or even Starfleet’s “General Order One”:




Oh, wait, they didn’t go to Starbase 5. They were just flying around or something, I guess, because their mission probably isn’t that important.

Instead, Amanda, the 43-year-old mother of a 32-year-old Spock arrives after having just been to Starbase 5 and nicking Spock’s medical records, which leads to Pike getting in contact with Starbase 5 and learning that Spock allegedly murdered three people, escaped, and is now on the run.

Why wasn’t Discovery told about this? Because it was classified, or something. Which is why Starbase 5’s commander didn’t answer any of Pike’s calls. Except that he’s telling Pike now, because… Well, I can’t really figure out why he would tell him now, and not before.

He says:


No, they do, asshole, they’re the whole reason Pike took command of Discovery, the reason he was able to violate the embargo on the Spore Drive as well as violate the Prime Directive. But now Starfleet has sort-of-but-not-really classified Spock’s case because:


Except that, the files only went missing because Amanda stole them. And Amanda only knew Spock was at Starbase 5 because… wait, hang on, nobody except Pike seemed to know he was at Starbase 5. Certainly neither Sarek nor Amanda knew, nor did Burnham. So how did Amanda know?




  1. Did Pike radio in to Starfleet to ask about Spock, and they ignored him until…
  2. … Amanda found out, flew to Starbase 5 herself (faster than Discovery could instaneously spore-drive it’s way there from New Eden)…
  3. … and stole Spock’s records, causing Spock’s status to become classified?

Why would Starfleet obstruct the mission that they gave to Pike? If they have ulterior motives, then why assign him the advanced starship with the experimental drive that would facilitate his mission? If they don’t have ulterior motives, then why would they obstruct the mission?

But this is just a contradiction between a narrative that occurs over two episodes. Check out the contradiction in just these three lines of dialogue:




  1. Burnham has to ask if Amanda knows about the signals, implying that they are not common knowledge.
  2. Amanda answers that Sarek told her specifically.
  3. Amanda then follows up by explaining that people are anxious to know what they are, implying that the signals ARE common knowledge.

This level of stupidity is so overwhelming that I genuinely find it quite taxing to get my mind around it. The writers of this show genuinely cannot maintain a single, coherent train of thought across three fucking lines of dialogue.

The rest of this story arc pretty much goes nowhere, beyond establishing that Spock had a vision of the Red Angel when he was a child, and that Burnham did something truly awful to him when he was younger as a means to protect him – which tracks true for Burnham’s mutinous “Chaotic Stupid” character alignment as established at the very start of the show.

The biggest takeaway from all of this is that the entire Burnham sub-plot was all about Spock, and not Burnham. We learn virtually nothing new about Burnham, beyond the fact that she was a colossal fuck-up as a youth as well as when she was a first officer. Also that she ran away one time. We sacrifice any opportunity to properly examine her own character, in lieu of exploring Spock, a character who is yet to appear in this show.

This narrative is dull, heavy on exposition, and does very little to advance the plot beyond sending Amanda on her merry way to find Spock herself. I’ll cover more of this narrative in my next character piece, which will be looking at Burnham specifically, but for now, we’re done with this little cul de sac of a story.

Onto the next.

Damn It, Tilly, I’m A Mycologist, Not A Spine Surgeon

Tilly is on the Command Training Program’s half-marathon exercise. One of many, because she apparently scores a PB:


Oh, wait, she set a new course record, too:


If she set a new course record, why is Burnham not mentioning that? Isn’t that the bigger achievement, as well as making the other two things obvious? Like, is it’s possible to set a course record and not beat your personal best on that course, and at the same time win? Whatever.

So, Tilly’s running with three other command trainees, and their coming is heralded by the computer announcing it like it’s fucking Red Alert or something, shutting off all the lights to boot:


This makes absolutely no fucking sense. I mean, it’s not as though they’re running on rough terrain, like an obstacle course or something, where the flashing lights might kind-of make sense, this just seems to be a fitness test on flat corridor floor panels. So the only reason for the lights to go out is to add dramatic, disorienting tension to Tilly’s confrontations with a ghost that’s haunting her.

Which is fine, if it’s something that happens solely within the context of Tilly struggling with the ghost. Except that the lights go out on Burnham, too, which means they’re actually getting switched off for some reason, which doesn’t make sense, which-


The point is, we later see Tilly wigging out on the bridge as this ghost, May, torments her, until Tilly shouts at her and then runs off in a nervous panic, which is understandable.

What isn’t understandable is the exchange that follows, where Tilly goes to her quarters, where Burnham is waiting, who explains that Saru has apparently been looking all over for Tilly despite the ship having internal sensors but WHATEVER, and then Tilly has a conversation with Burnham whilst being tormented by May the Ghost.

Tilly starts crying, and the ghost says that her eyes are dripping. Tilly then explains to Burnham that the ghost doesn’t know what tears are, to which Burnham responds:



How can this ghost, which was able to extrapolate the image of an adult version of Tilly’s friend from high school that she knew for six months, and bring up a nickname (“Stilly”) that Tilly had forgotten, not know what crying is???

Especially given this line from when the ghost was introduced:


How can it possibly know so much about Tilly’s life, and yet know know what crying is?

This leads Tilly to seek help from Stamets, who examines her and finds an interdimensional fungal infection attached to her nervous system:


Look at that thing! All up and down her spine, her lungs, her… is… is it infecting her tits, too? Ah, whatever.

Stamets’ reaction to this?

Grab the nearest cask of dark matter, open the lid and just point it at Tilly, hoping it’ll suck the parasite out.

Y’know how it’s really difficult to safely remove parasites like ticks and leeches and even just athelete’s foot, because they root themselves into the outer layers of our bodies and need to be carefully removed just to avoid scarring?

This parasite is rooted in Tilly’s fucking brain stem and Stamet’s just yanks it out of her like an evangelist purging a demon. I mean look at this, he’s not even got the dark matter mounted to anything! He’s just holding it and waving it in her general direction, hoping for the best!


Bear in mind that it was exposure to dark matter that prompted the appearance of May in the first place, so what if this just fed the parasite instead of removing it?

What if as this parasite is removed, it rips a chunk of Tilly’s spinal column out with it? Or just fucks up her internal organs?

The point is, Stamets had no way to know, because there are literally, literally


between those two screenshots.

37 seconds between Stamets seeing a never-before-seen multidimensional fungal parasite, and him improvising a handheld solution to extracting it from Tilly’s central nervous system.

This thing is so wired into Tilly’s brain that it can conjure up images from the deepest parts of her long-term memory, and Stamets just casually tears it out of her without even speaking to a doctor first.


This is, without a doubt, the STUPIDEST moment from all of Star Trek history. ALL of Star Trek history. I have never seen something this idiotic in my entire life.

So Stamets pulls a big snotty blob of goo out of Tilly’s spine and just throws it up into the air where Saru puts a forcefield up around it and…

… That’s it. That’s the last we see of the Discovery crew this episode, before we switch back to the Klingon Empire and the re-introduction of Section 31.


Klingon Power Struggles Klingons Struggling With Power

Do you like political intrigue? Drama? Difficult choices and forced compromises?

Then go watch some other show.

The Klingon plotline of ‘Point of Light’ tries so hard to be ‘Game of Thrones’ that damages itself in the process. It manages to be what ‘Game of Thrones’ would be, if everyone in Westeros was either Joffrey or a Pakled.

I’m going to try and cover this as succinctly as possible:

L’Rell is the High Chancellor. She is holding onto power through a few loyal family members and Ash/Voq, who acts as her de facto second-in-command.

The head of a rival Klingon House, Kol-Sha (whose son was Kol, the General of last season but whatever), seeks to challenge L’Rell and take the chancellorship away from her.

Kol-Sha shows up with red paint on his face, a sign of the old ways he represents:


L’Rell asks him to remove it, and he ignores her:


So Ash tries to violently wipe the paint from Kol-Sha’s face:



Later, according to Kol-Sha:



But… you didn’t beg her, Kol’Sha. She ordered you to remove it, and you refused.

Even if he’s just being metaphorical (a bit of a stretch) – was this his plan? To seize power? To turn up wearing paint filled with listening devices, so that L’Rell would ask him to remove it, he’d then refuse, and then her boyfriend would try to remove it himself?

What if L’Rell just didn’t give a shit about the paint?

What if she was like, “Huh, still wearing paint, I see. Anyway, here’s my economic recovery plan so that we don’t all starve to death after that immensely costly war.”

What was his next step?

Right, whatever, maybe he would just be to try something else, so, whatever. Whatever.


So then Kol-Sha uses these sensor thingies to learn two things:

  1. That Ash betrayed the Council to Burnham and the Federation.
  2. That Voq and L’Rell had a child.

With this knowledge, Kol-Sha decides to murder L’Rell and publicly release the recording of Ash betraying the Klingon Empire, taking L’Rell’s place on the grounds of treason committed by her second-in-command/lover/sworn protector.

Oh, no, wait, none of that happens.

Instead, Kol-Sha kidnaps L’Rell’s baby (a baby she cared so much about that she’s never met it) and then blackmails her into signing a form that would hand power over to him.


Kidnapping defenceless babies.

So they can blackmail their rivals.

Into signing a form.

Remind me again of how much ‘Discovery’ has done to explore Klingon culture and offer a new perspective.


This then leads into a fight, in which L’Rell and Ash fight a bunch of Kol-Sha’s anonymous mooks for nearly ninety seconds of over-choreographed, poorly-lit swordplay, at the end of which more mooks arrive and they’re back where they started, making the whole thing completely fucking pointless anyway.

Seriously, these two images are before and after a massive, complex, poorly choreographed fight scene:



Except that they aren’t, I actually put them in the wrong order – the bottom one is the before shot. And if you couldn’t spot that, then that’s exactly my point.

Just to hammer the pointlessness of this fight home, Kol-Sha then just paralyses both L’Rell and Ash anyway:


He then proceeds to take the hand of the paralysed L’Rell and places it on “Transfer of Chancellorship Oversight Form P-627-B” and completes the process anyway:


All of which means he could have just done that to begin with.

Why not just stun her before the fight?

When you go to steal the baby and leave L’Rell’s uncle hanging there, why not just lie in wait and ambush L’Rell, and then stun her?

Kol-Sha’s hologram was waiting for her to arrive, so he knew she was coming:


So… Just stun her then?

To quote Mr. Plinkett:

Forcing someone to sign a [document] sort-of contradicts the purpose of a signature on a document. You might as well just forge it if you’re going to make her sign it.

I mean, Kol-Sha has the ability to hide sensors in paint and to paralyse two people who happen to be stood exactly either side of him, so I can assume he has the tech to just forge L’Rell’s thumb-signature. And even if he doesn’t, why both with kidnapping the baby if you’re just going to paralyse L’Rell anyway and then physically press her thumb onto the document anyway?

Which means the entire plot with the baby was utterly pointless. It didn’t need to be there, and could have easily been omitted in an episode that already had too many sub-plots.

Which leads me onto my next, distressing, point…

CONTENT NOTICE – This next section contains discussion and images of harm done to children, which may be distressing. Please do not proceed any further unless you are confident that you won’t be upset by it.

Dead Baby Jokes

I grew out of telling dead baby jokes about ten years ago. It happened when a friend pointed out that they’re actually pretty insensitive, and could be hurtful to people who have had to cope with the loss of a child. And even then, I didn’t stop immediately, it still took a while to phase that kind of joke out of my lexicon.

Now, I want to share with you a quote I included in an article I wrote waaaay back when:


So, nudity “just doesn’t feel right” for Trek. And let’s be clear, there are topless men all over the place. So what Aaron means is “female nudity.” Women’s nipples is apparently the thing that Trek isn’t ready for.

What Trek apparently IS ready for is images of decapitated babies.

We know this because such images appear in this episode, the penultimate scene of which involves High Chancellor L’Rell holding aloft the severed heads of both Ash and her infant child:



The one saving grace of this image is that it wasn’t *quite* as graphic as it could be.

The second is that technically, this is a genetically-perfect recreation of a baby’s head created by the sick fucks in Section 31, and not the baby itself.

The absolute condemnation of this scene is that is was completely unnecessary, and in no way required by the narrative.

Which is the definition of “gratuitous.”

L’Rell’s baby is brought into this story as an afterthought – a sub-sub-plot to the sub-plot of the Klingon power struggle. There’s nothing inherently wrong with introducing a child to the (already-problematic) relationship between L’Rell and Ash. But to introduce it, then use it for a gory and distressing visual, and then for the actual baby to just be put on a bus at the end as it’s transported down to some insular monastery, is just exploitative and really, really grim, and says a lot about what the creators of this show want to achieve with their story – which is, apparently, to shock and distress, rather than to provoke and inspire.

Section 31, Starfleet’s Most Famous Secret Undercover Intelligence Agency


There is so much I could talk about with Section 31 on an over-arching, meta level, but for the purposes containing the sheer volume of this already overly-long article, let’s just focus on what’s in this episode, and this episode alone.

So, Emperor Georgiou appears at the exact moment that Kol-Sha is about to execute Ash. She seems to phase through a wall, so it’s possible that she was there all along, watching the fight happen.

She reveals herself in order to kill Kol-Sha, L’Rell’s would-be usurper, and reinforce L’Rell’s position as a puppet tyrant installed by Starfleet using weapons of mass destruction.


If Georgiou only just arrived, then it’s an awfully convenient coincidence that she turned up exactly at the split-second that Ash was about to get stabbed. That would be a rubbish bit of TV-writing.

If Georgiou had been there the whole time and was waiting for the right moment… Why didn’t she step in before Kol-Sha paralysed L’Rell and forced her signature out of her, thereby transferring her power to him?

In fact, why didn’t Georgiou step in during the massive fight when, L’Rell could have been easily stabbed in the face or decapitated or something?

If she didn’t want to risk getting hurt herself and needed the element of surprise, then why didn’t she step in just before the fight, when everyone was in the exact same position as they were before?

None of her motivations match her actions. Which makes this whole thing stupid.

But that’s not the only thing that’s stupid.

Section 31, a highly clandestine, super-secret, xenophobic intelligence agency within the Federation. They rely on absolute secrecy to achieve their objectives.

Absolute secrecy.

To maintain their veil of secrecy, they take the following actions:

  1. Hiring “misfits” and “freaks”, i.e. people with atypical behaviour which by definition makes them stand out.
  2. Hiring one of Starfleet’s most highly-decorated and presumably recognisable captains, Philippa Georgiou.
  3. Hiring Ash Tyler, someone guilty of treason against both the Federation and, now, the Klingon Empire.
  4. Wearing distinctive black badges marking them out as Section 31.

This… is just stupid. Just so, so stupid. The Archer comparison above is being generous.


The whole purpose of a secret agency is to remain secret. If you starting bringing along people who stand out from a crowd, and you have your own publicly-recognisable insignia… aren’t you defeating the point?


Section 31 should be made up of all of your most average-looking, run-of-the-mill, ruthless sociopaths. People who blend into a room, who are remarkable for being unremarkable.


They shouldn’t even have insignia badges, they should have either standard Starfleet badges, or none at all. They should just make themselves look like a civilian organisation. Or not even an organisation at all. They should be small cells, maybe just a few independent agents, compartmentalised and scattered across the galaxy.


But now, they have a distinctive-looking badass starship with big folding nacelles and its own crew. Hell, they’ve probably got a fleet of them. That’s just how secretive they are.


I mean, why even bother with the intentionally ambiguous and nondescript name “Section 31”? You may as well just calls yourselves “Starfleet Black Ops” or “Swastika Squadron” at this point.

Stupid All The Way Down…

This episode may have broken me.

It was so dumb in so many ways, I could write another three articles at least this long just about Burnham’s and Tilly’s sub-plots.

More than anything, this episode was just kinda boring. It didn’t excite or thrill the way you might expect from a high-budget, dumb-but-fun blockbuster-style story. It just shocked and distressed.

I’m worried now that ‘New Eden’ was a fluke, that the glimmer of hope it offered was just a mirage, or worse, an intentional tease, of what this show will never be.

We’ll have to check in next week to see.

Discovery In Depth – Breaking Tension, Or “You Saved The Universe And Nobody Cares”

Stories are important to us. They convey ideas and they make us feel emotions. They help us understand things we might not otherwise understand, and they offer different perspectives on a confusing and scary world.

Science fiction stories are particularly important, because they help us develop our feelings about the unknown. ‘Arrival’ dealt with many themes, the most obvious being “how would we feel about the arrival of an alien race?” It also dealt with how we perceive time, and how we might react if we had 20/20 foresight as well as 20/20 hindsight.

But science fiction doesn’t have to be weighty and intellectual. Sometimes, it can simply help us realise how we feel about things like adventure and devotion – or isolation and terror.

But in order to make us feel anything, science fiction has to tell us a story.


But what even is a story?

Well, it’s easy to think that a story is simply a sequence of connected events. But a story, a real story, is more than that. A series of events is actually just a plot, and a plot is one half of a story. The other half is tension, otherwise known as “suspense”, or “emotional connection”.

To understand the difference between plot and tension, and to understand why both are important, let’s use an example, which I’m going to title ‘Tilly And The Coffee Incident’:

  1. Ensign Tilly is on her way to Engineering to begin her shift.
  2. On the way, she stops to get coffee.
  3. Then she accidentally spills the coffee on her uniform.
  4. So she goes back to her quarters to change into a clean uniform.
  5. Then she heads back to Engineering and arrives late.

That is a plot. It’s a sequence of connected events that make sense because one leads to the other.

However, there is no tension, or emotional connection, or context, to the plot laid out above. It’s possible that you, as a reader, have personally been in that situation before, and so you already have some emotional connection to Tilly, but for most people this is just a series of things that happen to Tilly – at best, we can infer that she feels annoyed or embarrassed by these events.

So let’s take this plot and make it a story:

  1. Ensign Tilly is on her way to Engineering to begin her first shift in her new role as Engineer’s Mate, and she feels nervous about making a good impression.
  2. Because of that, she wants to make sure that she feels alert, so she stops on the way to get a a nice shot of espresso with hazelnut syrup.
  3. Because she’s nervous, she doesn’t pay attention to what she’s doing and she spills the espresso on her favourite, best-fitting uniform.
  4. So, she hurries back to her quarters to change into a grubby uniform from yesterday, because she’s behind on her laundry.
  5. She finally makes it to Engineering, fifteen minutes late, flustered and self-conscious.

Hopefully you notice the difference. It’s important to note that the events haven’t changed. The exact same things have happened to Tilly, in the exact same order. But this time, we’ve got a little more context, and a little more information that allows us to empathise with her situation.


Further, right off the bat, we have tension. This isn’t just another day – this is a big step in her career, and she wants to make a good impression. Just from that, we now know that there’s something at stake, something for our character, and hopefully our audience, to care about.

If this were a book, we might explain Tilly’s nervousness through her inner monologue, or a description of her feelings by the author. In Film and TV, she might discuss it with a friend, or we may simply leave it to Mary Wise to show display nervousness in her performance. Given this is Star Trek, she’ll probably explain her feelings in her Personal Log voiceover. If this was a musical, we might have a ten-minute song with a thousand Starfleet dancers whirling around Tilly as she sings about destiny and dreams and some other bullshit.

The point is, this is now a story. It has plot, and it has tension. But what is tension?

As mentioned above, at its most basic level tension is simply “something to care about.” Tension is broadly made up of two components – stakes, and threat.

Stakes just means “something a character wants or needs.”

  • It could be as simple as the need to live, which is usually the central source of tension in action movies – “Will our hero survive this fight? Will she escape the crashing plane in time?” etc.
  • It could be more complex, like a promotion, or a relationship with a romantic interest, or to solve a murder.
  • It could be enormous, like saving the world from destruction, or small, like catching a train on time.


Threat is pretty self-explanatory, but a proper delineation would be “the chance that something will go wrong.”

  • Our action hero is alone in her living room – there’s little uncertainty that she’s going to survive this ordeal, so we have no tension.
  • Our hard-working protagonist wants her promotion, and it’s a small company and she’s the only person in the town with the right experience and qualifications, so it seems pretty likely she’ll get the promotion, so why do we care?
  • Our main character needs to catch his train on time. He gets to the station five minutes early, and so stands on the platform for a little while until the train comes, and then he gets on it. Great! Story over.

We need both stakes and threat to create tension, and we need both tension and a plot to make a story. These four concepts are all of equal importance in telling a story that is compelling, captivating and meaningful.

Sometimes tension can be easy to create, flowing naturally from the events of the plot. Our character has to cross a tightrope across a deep ravine in order to escape the pursuing Nazis trying to kill her. We all understand the concepts of tightropes and of gravity, so as soon as we see our protagonist look down at the rocky river bed hundreds of feet below, we can instantly feel the tension.


But it’s not always that easy. Most of us audience members have never commanded a Cold War-era nuclear submarine in combat, so when Ramius and Ryan have to evade destruction in the finale of ‘Hunt for Red October’, the film has to work a little harder to help us understand what is at stake and why it’s uncertain. It does this by having characters explain what is going on and what might go wrong, and by having scenes earlier in the movie which explain some of the concepts but with less tension.

It’s vitally important to make sure that both the stakes and the threat are understood by the audience. This means that the audience needs to be able to emotionally connect with whatever it is that’s at stake, and they need to understand how and why there is uncertainty in achieving them.

In our ‘Tilly And The Coffee Incident’ example story, the tension comes from her desire to make a good first impression on her first shift (the stakes) combined with that being put in jeopardy by her being late (threat). If we care about Tilly doing well in her new promotion, then we care about the events that have transpired and possibly caused her to fail.


Once you build tension in a story, there’s three things you can do with it:

  1. Break it, frequently through humour, subversion or incompetence.
  2. Escalate it, usually by letting events reach a natural and sensible conclusion.
  3. Increase it, either by increasing the scale of what is at stake, or by increasing the chance of failure.

The bottom two, resolution and escalation, are nearly always preferable, but you need to choose which based on where you are in your story – in the middle of Act 2 or at the end of Act 3 you want to resolve the current tension, otherwise you want to escalate it. Breaking the tension is usually the thing you don’t want to do without good reason, for exactly the reasons we’ve already explained – stories need tension, and if you break the tension then you lose it, and if you lose the tension then you lose your story.

Just to finish off this basic explanation, let’s look at those three options and apply them to ‘Tilly And The Coffee Incident’:

  1. Tilly apologises profusely to Lieutenant Stamets for being late. He tells her that it’s no big deal, and it’s nothing to worry about, there’s nothing important to do around here anyway.
  2. Tilly apologises profusely to Lieutenant Stamets for being late. He tells her that he’s disappointed in her, that he had high hopes she’d be professional and reliable, and he feels as though she’s now broken his trust in her.
  3. Tilly apologises profusely to Lieutenant Stamets for being late. He tells her that he’s angry with her, and that if she’s late again, he’ll demote her back down to Assistant.

If you’re like me, then your strongest emotional reaction will be to either Scenario 2 or Scenario 3. That should be clear because they’re both more emotive in terms of Stamets’ reaction. But beyond that, they work with the tension, whereas Scenario 1 merely breaks it.

By having Stamets dismiss any importance around Tilly’s tardiness, the tension – the combination of stakes with uncertainty – is completely dissipated. The only way to build any tension up again is to introduce a new plot element – maybe they discover a problem with the warp core that they now need to fix. But if you need to re-establish tension, then you may as well skip the bit where Tilly spills her coffee on her uniform and just start at the point where they discover the problem with the warp core.

By having Stamets respond with sadness and disappointment at Tilly’s unreliability and to then indicate a permanent change in the relationship, we resolve the tension built up by Tilly being late. We resolve it negatively, but that’s okay – this would lead into a good “low point” for Tilly, and as such would fit in the middle part of a story.


Finally, we can have Stamets respond with anger, and offer an ultimatum – “Don’t be late again or I’ll demote you.” This is an escalation of the tension – now it’s even more important that Tilly arrives for her shift on time tomorrow, because otherwise her career is over. Maybe later, a Klingon will sneak aboard Discovery to carry out his revenge against Tilly’s alarm clock, defeating it in glorious battle, and leaving Tilly to oversleep tomorrow and be forced to choose between arriving late to her shift again, or going to work without showering first.

Now, these are just the bare basics of storytelling, and there are lots of different ways to implement these concepts. HOWEVER, any successful story will nontheless have a plot and tension, which is made up of stakes and threat. From the Cohen Brothers’ most unconventional and high-brow work to the most primitive CGI-laden blockbuster of the century, if people enjoy watching it, it will be because the story builds tension within a coherent plot.

So, why have I just spent nearly 1800 words describing all of the most basic, first-chapter-in-a-“How-To-Write-Your-Own-Screenplay”-book concepts of story construction?

Well, the answer to that is the same answer I always give for my bizarre behaviour – because I wanted to whinge about ‘Star Trek: Discovery’.

Specifically, I want to go back to whinging about Season One, and some unfinished business I’ve got with events from that narrative. But I’ll also be looking at some minor points from Season Two, so buckle in, fuckos, we’re going on a ride.

Episode 13 of Season One of ‘Star Trek: Discovery’, titled ‘What’s Past Is Prologue’, features a story about saving the Mycelial Network. The Mycelial Network is a universe-, or rather multiverse-spanning phenomenon which maintains all life in every universe in existence. The evil Terran Empire’s flagship the ISS Charon drew power from the network, and in so doing was poisoning it, threatening the entire network with destruction, and hence endangering every single lifeform in every single universe.


So, those are the stakes. All life, in every universe.

There are literally no higher stakes than that. That is literally all things that can possibly be at stake.

And it’s awful.

It’s awful because no living human being can grasp the full meaning of “all life in all universes”. Hell, we can barely cope with figuring out how many people are standing in a park. Which means there’s no way to form an emotional response to it. Stakes need to be human in scale – they need to be within emotional and intellectual reach of the audience.

But what about the threat?

Well, roughly 24 minutes into the episode, we get this line:


This comes after Tilly explains that the shockwave from destroying the Charon will almost certainly destroy Discovery and her crew. This is an unusual approach to tension, with the fate of all universes at stake, and then adding to that the certainty that even if the crew succeed at their mission, they will all be killed in the process.

Now, this is a really interesting element to introduce, and has a very ‘Passing Through Gethsemane’ from ‘Babylon 5’ feel to it (or “Suicide Mission” from ‘Mass Effect 2’ if you’re that way inclined), and is actually a great way to add weight to a story. You’re guaranteeing the negative consequences, making the threat certain. That’s the highest it can be.

Which means we have maximum possible stakes mixed with maximum possible threat.

But don’t worry, because literally five minutes later, at the 29-minute mark, we get this line:


This comes after Tilly has described a way for Discovery to survive the assault on the Charon unharmed, and Stamets adds that not only that, but that they will now be able to find their way back to the original universe whence they came.

Which means within a space of five minutes and about three scenes, we’ve gone from maximum-possible threat to essentially zero threat. They have already overcome any uncertainty before they have reached it.

Eight minutes later, we watch the Discovery make its attack run, fly through the Charon, through the massive star-like energy ball within it, and out the other side. Sparks fly, and the ship shakes, but no damage is done, nobody gets hurt, they complete their mission, and then escape back to their own universe.


This whole sequence obliterates any tension within this story arc, for the following reasons:

  1. “All Life In All Universes” is a completely unthinkable scale of danger for most non-Q audiences.
  2. The threat to Discovery – stakes which a human can understand – is completely diminished when Tilly and Stamets solve the problem before they ever meet it.
  3. At no point do we, the audience, understand what could go wrong or why.
  4. Nothing does go wrong, and so our characters overcome nothing.

If we go back to ‘Tilly And The Coffee Incident’ and Stamets’ three possible responses, this is the equivalent to him telling her it’s no big deal. Any tension we might be feeling is completely destroyed because it turns out the thing that both Tilly and the audience were worried about doesn’t matter anymore.

By taking out the tension, you’re transforming a story into a plot. There’s no longer emotional attachment, so you’re just back to a sequence of connected events.

To hammer the point home, let’s do a comparison. Here is the story as it occurs on the show:

  1. Discovery has to destroy the Charon in order to save all Life in all Universes.
  2. Tilly explains that this will destroy Discovery and everyone aboard.
  3. Saru gives a rousing speech to keep the crew focused.
  4. Tilly discovers that they can escape after all if they adjust their equipment.
  5. They adjust the equipment.
  6. Discovery attacks the Charon
  7. and succeeds on its first attempt.
  8. Discovery escapes. Everybody survives, nobody is hurt.


This is just a series of things which happen. But if we just switch some of those events around (and add a couple more):

  1. Discovery has to destroy the Charon in order to save all Life in all Universes.
  2. Tilly explains that this will destroy Discovery and everyone aboard.
  3. Saru gives a rousing speech to keep the crew focused.
  4. We see a montage of the crew coming to terms with their fate and preparing for one final, deadly mission.
  5. Discovery attacks the Charon
  6. and the Charon responds by firing all its weapons at Discovery
  7. badly damaging Discovery and killing several crew, forcing her to wave off and try to attack again.
  8. Discovery lines up for one more attack, ablaze and filled with smoke, the floor covered in debris.
  9. A wounded Tilly notices a resonance cascade in the Charon‘s power generator
  10. and theorises that if Discovery jumps to warp at the exact right second, her warp field might destabilise the cascade and cause the Charon to overload.
  11. Tilly struggles to focus through the pain from her wound as she coordinates with Detmer, carefully calculating the ship’s trajectory, until
  12. at the very last moment, Tilly signals Detmer to engage the warp engines, detonating the Charon‘s power generator.
  13. Discovery escapes, but many of the crew are injured or dead. The ship itself is burned and battered and falling apart at the seams.

I’ve tried to avoid using intentionally emotive language in the second version, but hopefully it’s clear which version carries more tension, and therefore more emotional weight. It’s just an example of the changes that could be made, and the key thing is that it wouldn’t require much more in the way of production effort – just a few changes to the CGI, and a bit of extra set-dressing and makeup.

Crucially, it wouldn’t require much more screen time, as we’re simply taking the scene where Tilly and Stamets work out the solution beforehand and changing it a little, then inserting it later in the story. If more time was needed, then I’m sure a bit of editing could be done to the five-minute sword fight aboard the Charon in which no major characters are killed.

And more importantly, there are real and predictable negative consequences to the actions taken by the crew. In ‘Wrath of Khan’, the Enterprise is fighting to save itself from Khan and the Reliant, and in the process many crew are injured or killed, most notably Spock, the most iconic figure of the franchise.


In ‘What’s Past Is Prologue’, the Discovery is fighting to save All Life Everywhere, and the biggest negative consequence that follows from this is quite literally a few sparks flying on the bridge. This again destroys any tension and, further, it undermines the the severity of such an important mission. It makes saving the Universe seem almost casual – there’s nothing to suggest that the crew couldn’t do this another twenty times if they need to, and that’s not fitting when all of existence is at stake.

For Stark contrast, take a look at ‘Avengers: Infinity War’, where only half of all existence is at stake, and we still get the very serious consequences of some of our favourite characters who … don’t feel… so good.

You noticed the pun I dropped in there about “Stark contrast”, didn’t you?

The point is, in the space of ten minutes, Discovery saves the entire universe of universes, but they did so without any tension, any emotional connection, for the audience, which means the audience isn’t invested, which means the audience doesn’t have any emotion riding on the outcome.

They saved the universe, and nobody cares.

For the sake of balance, let’s have a look at ‘Discovery’ getting tension right, and for that, we need to go back a bit to the Harry Mudd episode (yes, that Harry Mudd episode, misogyny and all) titled ‘Magic To Make The Sanest Man Go Mad’.


In this episode (simplified down hugely), a vengeful Harry Mudd seeks to murder Captain Lorca and steal the secrets of ‘Discovery’. He does this with the use of a time-travel gagdet which allows him to re-live the half-hour over and over again, remembering everything he learnt from his previous attempts.

What Mudd doesn’t know is that one of the crew, Stamets, has been affected by the Spore Drive, and is also capable of retaining memories through each time-loop. So now Stamets has to try and stop Mudd before he kills the crew and steals the ship – and he can only do that by convincing the rest of the crew of what’s really happening.


Straight away, we’ve got a plot, stakes and threat. The plot has already been laid out. The stakes are the Discovery and the fate of the crew, and the threat comes from Mudd’s nearly God-like advantage of being able to repeat the same sequence of events over and over, learning from and changing them each time – the Star Trek equivalent of the Konami Code.

Even better, the episode helps the audience to understand this threat by showing us repeatedly the dire consequences of Mudd’s near-victory. Over and again we are allowed to delight at the creative methods Mudd devises to brutally murder his nemesis, Lorca, made all the better by the fact that up to this point, Lorca has been nothing put a passive aggressive edgelord.

That’s the power of repetition at work.

So you take the following ingredients:

  • A sequence of connected events which form a plot
  • Tension and emotional connection for the audience, made up of:
    • The stakes of defeating Mudd, saving the crew and protecting Discovery
    • The threat of an enemy with a near-flawless advantage

You bake these in the oven with some neat special effects, strong acting, well-paced editing, narrative focus from the director, and some emotional highs and lows as our characters confront their inner demons, and


That’s magic, baby. Magic to make the sanest person go mad, indeed. All of this is what makes the bulk of this episode so enjoyable, and is what makes it such a shame that it ends on such a daft note (with the crew letting Mudd go free with all of Discovery’s technical secrets, and being punished by being reunited with his loving fiancée – because women be bitches, am I right?).

(I am not right.)


That’s enough of praising the show, let’s get back to whingin’.

Another great example of tension-demolition comes from Season One, directly after the above ‘What’s Past Is Prologue’, and has the similarly-overwrought title ‘The War Without, The War Within’.

At the 29-minute mark of a 48-minute episode (of this “well-paced adventure show”), Stamets outlines the main problem that the crew need to overcome this episode:


He’s referring to the mycelial plants that power the ship’s Spore Drive, which will allow them to jump to the Klingon homeworld of Qo’Nos in order to survey their subterranean caverns in order to-

Whatever, this isn’t important.

What is important is the tension in the story, and there is none.

This scene transitions into the next scene where Stamets barely explains his plan – the most coherent explanation we get comes from Tilly:


Over the next ten minutes, we get a single scene in which we see Tilly doing some work or other on this incredibly ambitious project whilst Burnham distracts Tilly by talking about her own lovelife.

At the 39-minute mark, we are treated to the following visual:


That’s the terraforming process complete. They manage to change the ecology of an entire moon (and it is an entire moon, that’s confirmed on-screen) in a few seconds.

And, not to get off topic here, but can we talk about how fucking terrible that CGI looks? The one thing people keep telling me is that as a “DISCO-hater” I’m just angry that the show doesn’t look like TOS or TNG, because now it’s got a “big budget” and “really good visuals” – but just look at that image above! I’ve literally seen more convincing visuals in fucking ‘Star Trek: Online’, nevermind the rest of the on-screen franchise.

This is literally a shot of a random planet from a trashy MMO, and it still looks better than bloody ‘Discovery’

And just in case you don’t believe me:

Another STO shot. And I don’t even play the fucking game, I loathe it.

Anyway, where was I?

Oh yes, so anyway, Stamets’ plan works without a hitch. There literally isn’t even a moment where it seems like it won’t work. They just launch their 42 pods, which are apparently enough to terraform an entire planet, and yes, I know that it’s just 42 because it’s possible to literally count, here, look:

“Why did you go to the trouble to count these?” you may ask. Well, first off, it’s just multiplication – 7 launchers each with 6 pods. And secondly, as per my explanation above for erratic behaviour – because I wanted to whinge about ‘Discovery’

Okay, so 42 pods, all fly down to the surface, plant their spores, fire some electromagnetic pulses, the spores grow, and that’s it. Then everyone starts patting Stamets on the back like he did something incredible, and we even get this line from Admiral Genocide:

Okay, so her name’s not actually “Admiral Genocide”, I’m being facetious. It’s “Admiral War Crimes”

Well, what’s she congratulating him for? Was there meant to be anything special about what just happened? If it was special, both of the following needed to happen:

  1. The threat of failure needed to be setup.
  2. Stamets’ method of overcoming this threat of failure needed to be shown.

Instead, we simply have the following:

  1. Stamets needs to grow more Mycelium.
  2. Stamets explains (sort of) to Tilly that they need to terraform a moon.
  3. They terraform the moon.

That’s not even leaving anything out, that’s literally the sequence of events around this sub-plot.

Now, I know what you’re thinking: “But this episode was more about relationships than it was about the spores.” And I’d agree – but that simply raises the question of why even include this subplot at all? If it’s just there for a thing to happen, then have the thing happen off screen! If you’re not going to add any tension to any of it, why devote three scenes and eight minutes of screen time to it at all, if the summary is: “We needed to do a thing, so we did it.”

But even if you do need to show it, why present it as the climax of the episode? There’s a couple of scenes that follow in which Burnham tells Ash to go fuck himself for trying to kill her and now begging her to take him back, and then we get the reveal of Emperor-Captain Georgiou right at the very end. But these are both presented as codas, or epilogues – the scene between Ash and Burnham to tie off their relationship, and the scene with Georgiou to land a cliffhanger for the final episode of the season.

So this big, “beautiful” moment with the terraforming and the fungi-growing is presented as the crescendo of the episode, as though something great has just been achieved. But according to the script, nothing has been achieved – nothing was overcome. We don’t even see them building the array of seedpod-launchers, as they’re just suddenly present in the shuttlebay, ready to go when the plot needs them.

Let’s move on, before I get really angry.


Alrighty, so, in the latest episode, ‘New Eden’, the crew of Discovery face a terrifying threat – radioactive debris from a planet’s rings has been knocked out of orbit and is descending towards the planet, threatening an extinction-level event – i.e., all life on the planet, including 11,000 humans, will be wiped out in a matter of hours.

If this seems familiar, it’s because it’s exactly the plot from ‘Deja Q’, the Season 3 TNG episode in which a planet’s moon is on a collision course with the planet itself, an event which will wipe out all life on the planet.


In both scenarios, they rule out weaponry, as destroying the debris or the moon will only make matters worse. Neither ship’s tractor beams are capable of doing the job, so a creative solution is needed. In both cases, the answer involves gravity manipulation.

But for all the similarities between the two scenarios, ‘Deja Q’ gives us a much better story out of it, and we’ll cover why soon.

First of, let’s cover the tension, which works well for both stories:

  • The stakes are sound – all life on a planet. In ‘Deja Q’ there’s no immediate danger to the Enterprise, but in ‘New Eden’, Pike, Burnham and Owosekun are also on the planet, adding a more personal stake for the crew.
  • The threat is well established – all their existing technology won’t help, the obstacle is just too potent for the crews to deal with conventionally.

Great! We’ve got something to achieve and obstacles to overcome in order to achieve it. Strong start.

Except, that’s not the start. Not in ‘New Eden’. First mention of the planetary threat occurs at 22 minutes into the episode – almost exactly (in fact just slightly over) half-way into the episode.


Meanwhile, this threat is established in literally the first spoken words of ‘Deja Q’, in the Captain’s Log spoken by Picard at the very beginning of the cold open.

This difference is key, because it gives ‘Deja Q’ the time it needs to escalate the tension around the catastrophic asteroid, a tension which is escalated and escalated until it is finally resolved nearly 44 minutes later. In contrast, because of ‘New Eden’s pacing issues, it has less than half its remaining run time to resolve the issue.

And, indeed, it actually has less than that. Because at the 32-minute mark, once again almost exactly ten minutes after establishing the tension of the story, the problem has been solved. Why DISCO writers will insist on resolving their big action set piece narratives in less time than I need to take a dump is beyond me, but they seem to do it every episode.

Regardless, ‘Deja Q’ gives itself the time it needs to escalate the tension of the situation. The Enterprise makes its first attempt to push the moon to a safe orbit within the first two minutes, until they realise that they can’t push the moon hard enough without burning out the ship’s systems.


This is the first escalation of tension. The second comes at the 30-minute mark, where Geordi uses Q’s suggestion and attempts to science the asteroid into having a smaller inertial mass. This starts to work, until an enemy entity opens fire on the Enterprise, forcing them to cancel their attempt.

The ultimate resolution of this tension is via of a pseudo-Deus Ex Machina by Q, who sacrifices himself to get rid of the enemy entity, regains his powers, and restores the moon’s orbit as an act of compassion.

The key takeaway from all this is that we have a plot, and we have tension, therefore we have a compelling story, as follows:

  1. A moon is crashing towards the planet, threatening to kill millions.
  2. The Enterprise tries to stop it once, and fails due to the magnitude of the task.
  3. The Enterprise tries to stop it a second time, and fails due to enemy interference.
  4. Q sacrifices his own life to give the Enterprise a chance to stop the moon.


Now, let’s take a detailed look at ‘New Eden’.

The tension is established half-way through the episode, as discussed. And in response, Saru announces with full conviction:

You’ll note that he didn’t specify anything about ‘Discovery’ itself, which he certainly allowed to become a catastrophe.

All very heroic, and all very good. And sure enough, we later cut to Tilly, using her genius-science-brain to figure out a creative solution to avert catastrophe, which is great. Then she runs up to the bridge all Tilly-like and starts getting all excitable with Detmer, which is also great.


However, do you remember what Detmer said when she first alerted Saru to the danger? Here, I’ll remind you:


That “64 minutes” bit is what’s called “A Ticking Clock”, and is a very effective, reliable way to add threat to your story, increasing the tension. In fact, it’s an important element to this story. Y’see, in ‘Deja Q’, the Enterprise had a good 25 hours to sort its shit out:


That’s also a ticking clock, but because of the timescales involved, it’s much less important to building threat – it’s still useful, but minutes is better than hours when it comes to building tension.

So, ‘New Eden’ has a rapidly ticking clock. What does the crew do with those precious 64 minutes?

Well, um…


Literally, nothing.

Here’s Airiam, the very next time we see the bridge crew:


Four minutes left! A full SIXTY MINUTES has passed and they’ve done nothing. No failed attempts to stop the debris, accidentally making it worse. Hell, they’re not even out of the concept stage yet, check out this dickhead:

It was a dumb idea when Riker suggested it in ‘Deja Q’, and it’s a dumb idea now, so just shut the fuck up, Rhys. No, wait, Bryce? Shit, I always get all these walking status reports mixed up.

Sixty minutes have passed, 94% of the time they have to avert this catastrophe, and they’ve done nothing. Which means that not only are Saru’s words ringing hollow in the ears of the audience, but it also dissolves the significance of the stakes – after all, if it’s so important to save the people on the planet, why haven’t you tried anything? They haven’t even come up with a plan! They’re still spitballing!

I wasn’t kidding when I said that these episodes had a lot in common.

So that ticking clock was clearly pointless. I mean, sure, Saru & Co. might be trying to avoid making the situation worse, but it’s an extinction-level event, it’s not as though they can make it much worse. Especially when there’s just four minutes left before it’s all over.

So, let’s take a look:

  1. Debris is crashing towards the planet, threatening to kill thousands, including three crew members.
  2. It will happen in 64 minutes.
  3. Tilly puzzles on the problem in sickbay.
  4. The bridge crew take no action for 60 minutes.
  5. Tilly runs up to the bridge and explains the plan to save the day.
  6. The plan works. The day is saved.

This is another great example of ‘Discovery’ breaking the tension through incompetence. They did it in ‘What’s Past Is Prologue’ by solving all their problems before they ever encountered them, and they did it ‘The War Without, The War Within’ by just never building any tension in the first place. And they do in ‘New Eden’ by making the crew look like a big bunch of dumb idiots.

Now, I don’t want to be too harsh on this episode, as I enjoyed it personally, and I genuinely appreciated that they faced environmental problems that required savvy and creativity to overcome. These are all positive steps forwards for the series as a whole. But I do need to call out the failings where I see them, and they are significant.

And if you think that this doesn’t matter, because ‘New Eden’ is actually meant to be about loftier, more philosophical matters, like faith and rationality, then that’s fine, but so was ‘Deja Q’. Hell, ‘Deja Q’ wasn’t about the moon at all, it was about Q’s journey into humanity, and his contrast with Data, and it was about accountability, facing consequences for your actions. Hell, ‘Deja Q’ manages to run a good “save the planet” story and yet still leaves plenty of time for Data to talk about his breakfast:


Or even just talk to Q about relationships:


Or even just watch Q get stabbed for being a complete turdburger:


And that’s not even covering the bit where Data saves Q at his own expense, or Q feeling guilty over Data’s sacrifice, or all the debate between Picard, Riker and Geordi over whether or not it’s worth putting the planet below in danger just to protect Q from the Calamarain.

No, I said “CALAMARAIN” – get the fuck out of my DISCO review, Emissary!

And the point here is not to point out that TNG is “just better” than DISCO (although it is) – but rather, to point out that you can still have complex and heady themes alongside a more pragmatic story element, and build tension for both. ‘Deja Q’ is the proof that it can be done. Hell, ‘Magic To Make The Sanest Man Go Mad’ proves that it can be done, too. It’s as though the writers of ‘New Eden’ simply chose not to.

I’ll point out here as well that in ‘Deja Q’, the resolution of the problem is a Deus Ex Machina of a kind, as Q uses his literal God-like powers to correct the moon’s orbit. But, importantly, he only gets his powers back because he behaves in a way we’ve not seen before, by selflessly sacrificing himself after experiencing guilt and remorse for the first time in his life. We learn something new about Q, and we see a different side to his character, and that’s yet another great emotional connection for the audience.

In ‘New Eden’, we already know that Tilly is smart, so seeing her solve the problem doesn’t really tell us anything new about her. Neither do we learn anything new about the crew (beyond the fact that Detmer’s wonderfully cocky) because they don’t take any action themselves, and they don’t make any decisions. This means we don’t even get character growth out of this whole affair, rendering it meaningless.

The whole point of ‘Discovery’, its ethos, if you will, was to leverage bigger budgets, modern special effects and a young, fresh production team to create Star Trek for the new generation. They’re intentionally trying to increase the amount of action and excitement in the show – that’s a stated goal by the creators.

Which then brings into question – why the hell can’t they do it? Why do they fail to build that tension in almost every episode? And it is nearly every episode – I’ve just picked out the three simplest examples here.

As I said at the start of this monstrous article, stories are important. They are important because they make us feel things, and that’s more important than anything else. They give us emotional connections to concepts we may face one day – or that we have faced before – and allow us, the audience, to grow as individuals by developing our own ideas, our own conceits and our understanding of the world.

Which means that getting stories right is important, too. You have to build that emotional connection with the audience, you have to build that tension, in order for them to invest themselves in the story you’re trying to tell. Otherwise, there’s no point in telling the story at all – you may as well just list a sequence of events.

Star Trek Discovery ‘New Eden’ – A Steady Hand On The Tiller

Most of ‘New Eden’ made me feel happy.

The second episode of DISCO’s second season was a relatively well put-together work of fiction. There were stakes, there were debates, there were expressions of self-doubt by the characters. There was an away mission, which was lovely, and in classic Trek style it was to an M-Class planet, the “M” standing for “Much like California.”

I thoroughly enjoyed seeing Tilly & Co. once again getting excited by science stuff and doing science things with science objects. The science-solution to the science-problem was about as lucid as Trek gets with this sort of stuff and it broadly fits with the concept of a gravity tractor.



Detmer and Owosekun have graduated from “having lines” to “being plot-relevant”. Detmer’s a cocky little deviant and that’s just fine. Owosekun is apparently a Luddite, which is an… interesting concept for a community of people living in a tech-driven neo-Utopia. Particularly since the Luddites were a protest group whose opposition to machinery was due to fear of losing their jobs.

Airiam gets one more line this episode, taking her up to a franchise-total of four lines. What species is she? Who knows! I’m fine with leaving some character development for later, but she’s the most visually distinctive member of the crew and it would be nice for her to at least have some degree of characterisation beyond “none at all.”

Hands-down my favourite Stupid Pike Moment of this episode is the crew explaining to Pike the concept of the Spore Drive and Stamets’ role in making it work. I get that Pike’s the Supply Captain, but surely he’s been briefed a little since he took command? Surely it’s important to know that your chief engineer is half-tardigrade?

Another stinker is the receipt of the distress call and Pike’s immediate command to “ready photon torpedoes.” The distress call clearly refers to some kind of ground attack, Pike, so unless you want to atomise the victims as well as the attackers in some kind of callous display of indifferent, godly power, maybe just chill a bit?

Have you considered switching to decaf, captain?

Pike pushes hard on the whole “Well maybe there IS a god, did you ever think about that?” cul-de-sac of thought, further cementing his role as the lovable, dim, handsome captain who’s just glad to be along for the ride.

I didn’t have anything coherent to say about his ‘F’ grade in Astrophysics last time, and I’m not sure I do yet. On the one hand, it’s fine for leaders to have flaws.

On the other hand, the leaders of SPACESHIPS should probably know at least a little about “the branch of astronomy concerned with the physical nature of stars and other celestial bodies, and the application of the laws and theories of physics to the interpretation of astronomical observations.” I dunno, just give him an ‘F’ in Botany or something instead.


Overall, ‘New Eden’ was kind-of fine. Tilly was fun, if cringey. Burnham’s and Pike’s relationship is complicating nicely. It felt like a very standard episode of Star Trek. Jonathan Frakes’ directorial input was evident in the focused, tight scenes that didn’t leap from plot point to plot point just to Shelby the audience into submission.

I was glad that there was no unnecessary action scene. Pike’s phaser-blast to the chest seemed like a contrived means of forcing the away team to seek a return to Discovery before the planetary story had reached a natural conclusion. But there was also no ridiculous, budget-soaking asteroid pod-race. This was a show about people in rooms, talking, but this time the conversations changed the nature of the problem that the crew was facing.

Where will you be when Tilly strikes?

It was lovely to see the crew not just doing Science Stuff, but working together whilst doing so. There’s a part of me that hated Detmer’s delivery of the line “Extinction-Level Event”, but then I loved the way she and a hospital-robed-Tilly just started bouncing off each other trying to solve the Problem of the Week. It reminded me of Geordi and Data stood at the pool table on the Enterprise-D in ‘Deja Q’, talking excitedly about tractor beams and warp fields.

The Star Trek Grinch in me wants to criticise the “dumming-down” of the language, with talk of pulling doughnuts and the computer confirming Tilly’s assertion that things might go “boom”. But again, seeing Tilly with her Nerd-Goggles and Zero Point Energy Field Manipulator warmed the geek-cockles of my heart.

Likewise, Saru giving Tilly a stern but affectionate talking-to in sickbay was pretty touching, and felt like a nice relationship for these characters to have – uniting on their shared insecurities and self-doubt. Nothing wrong with that.


Stamets kept up the pathos and the sensitivity, which is also great. Anthony Rapp’s shown us a few different sides of the character, and Stamets has become a genuinely engaging element of the show.

The biggest failing of this episode was insufficient focus or development of the New Eden colony, their culture and their way of life. It felt like it had been heavily edited, stripped down for time, or potentially not fleshed out at all in the script. Which is a shame, as the last episode was a full sixty minutes, and I’d have been fine with this 45-minute episode running a little longer so that we could get more emotionally invested in the people of New Eden.

Specifically, Jacob was a fascinating character on the surface, but we just never got to fully understand his background, nor why his family remained devoted to science and technology.

This also leads into the absurd line by Burnham: “Say my religion is science.” That just doesn’t make sense from anybody’s perspective – either from the New Eden colonists, who despite their low-tech way of life all seem relatively intelligent, nor to Burnham herself, who as a Science officer and anthropologist should understand that science isn’t a belief system, but rather an approach to characterised by “testable explanations and predictions about the universe.”

Oh, come on, Burnham, you’re better than this.

Moreover, it’s entirely possible to be both religious and scientific – to hold irrational beliefs covering abstract concepts that cannot be tested, such as purpose, meaning and destiny, whilst still approaching all physical, observable phenomena via the rational, empirical method.

This notion that “science” is somehow an equally valid religious choice alongside Taoism, Islam, Christianity or even Wicca is so bizarre and just reeks of Kurtzman.

One curious point that struck me in this episode was all of the space-based CGI looking suddenly… better. I can’t for the life of me put my finger on it, if it’s higher detail models, better textures, better lighting, or all three, but the show is suddenly looking more like a high-budget TV show and less like screencaps from Star Trek Online.

For comparison, here’s the beauty shot from our first view of Discovery back in Season One’s ‘Context is for Kings’:


And here, from the end of ‘New Eden’:


Overall, this episode felt like it had a steady hand on the tiller. I don’t know if that really is the influence of Frakes, as his previous entry in the franchise was nonsensical and dull as sin. Either way, I was left feeling that if this is a level of quality that ‘Discovery’ can maintain, it might end up being a compelling show.

And one further point – with the introduction of the ship’s new grumpy doctor, and the increased importance of the bridge crew, I’m no longer feeling the need to track female interactions – women talk to each other, and do plot things, and in general manage to avoid just being victims all the time. It’s great! It’s how it should have been from the very beginning.

Discovery in Depth – Continuity and The Shelby Method

My first look at ‘Discovery’s Season 2 Premiere, ‘Brother’, was a chaotic ejaculation following an unexpectedly positive reaction to the show’s latest episode. However, there are heavier themes and ideas to explore in the world of ‘Discovery’ critique beyond “Just how explicit am I allowed to be in describing the things I would let Jet Reno do to me?” and “At some point I need to see Tilly and Stamets sing ‘Faith of the Heart’ together during the ship’s Karaoke night.”

One of the frequent topics of discussion with regards ‘Discovery’ is its fit within the Star Trek canon – which is shorthand for “does it keep continuity with what has come before / what will come after in other shows and films?”

To be perfectly honest, I’ve never cared that much about continuity with the rest of the franchise. Canon gets violated in Star Trek more frequently than the Prime Directive, very often with the same series violating canon that the series itself established several episodes earlier (see: beaming through shields).

However, several recent instalments in the franchise haven’t just ignored broader franchise continuity – they’ve ignored their own continuity from just a few scenes or even just a few moments before.

To explore this phenomenon, I’d like to introduce “The Shelby Method” of continuity.

No, not that Shelby.

Continuity – The Shelby Method

If you’ve seen ‘Memento’, you’ll be familiar with its main character Leonard Shelby, played by Guy Pearce. In it, Shelby is unable to form new memories – events occur, and within a few minutes he will have forgotten them entirely, finding himself in new and strange situations with no clue as to how he got there.

It’s notable for being a great little movie, with a wonderful cast, and for being Hollywood darling Christopher Nolan’s first widely-distributed film and the beginning of his $2.4 billion filmography (but sure, feel free to keep complaining about the plot holes in ‘The Dark Knight Rises’).


It’s also notable for inspiring what I have now coined as “The Shelby Method” of film and TV storytelling, most notably used in ‘Star Trek: Into Darkness’ and ‘Star Trek: Discovery’.

It works like this:

The significance of any information, plot development or dialogue is retained across the next two camera shots, after which it can be abandoned completely in favour of superseding information.

In short, if you’re telling a story for film or TV and you need cool stuff to happen, there is absolutely no need for previous events in the story to stop the cool stuff from happening.

For example, in ‘Into Darkness’:

  1. Admiral Marcus fires on the Enterprise
  2. causing her warp core to become dislodged
  3. causing Kirk to sacrifice himself whilst kicking it back into position
  4. causing Kirk to die
  5. causing Spock to scream “KHAAAAAN!”

Now, as your brain works through that sequence of events, and you begin to think “Hang on, why is Spock shouting ‘KHAAAAAN!’ when it was Admiral Marcus who was more responsible for Kirk’s death?” Spock is already down on Earth, chasing Khan through the streets of San Francisco, and now McCoy is resurrecting a Tribble with Khan’s blood, and now Spock’s on a hovering garbage scow, and now McCoy’s shouting at Uhura, and now Spock’s whaling on Khan with a lump of metal, and now he’s screaming like an animal, and by now you’ve already forgotten about that bit with the warp core, haven’t you?


If clever tricks of perspective and carefully-orchestrated special effects are considered “Movie Magic”, then the Shelby Method is “Movie Con-Artistry” – it’s the practice of moving the story along so quickly and dazzling or otherwise overwhelming the audience such that you prevent them from committing the events of your story to their long-term memory. You turn your audience into Leonard Shelby, remembering only the last few brief seconds of what they’ve just experienced.

Another example would be in Season 1 of ‘Star Trek: Discovery’, episode 8, ‘Si Vis Pacem, Para Bellum’, where Discovery‘s First Officer, Saru, betrays Burnham and Tyler and attacks them, sabotaging their mission to gain a war-winning advantage against the Klingons.

And as Saru lies in sickbay, explaining that he wasn’t even being mind-controlled, he was just emotionally overwhelmed, and you start thinking “Well, the last time a First Officer behaved that way, it was Burnham, and she spent six months in prison, and that’s the entire driving theme of this series, so is Saru going to at least get a court martial?” and then the peace planet emits a huge energy pulse summoning the Klingons, and Burnham and Tyler walk onto the bridge, and Lorca says something, and the communications officer says something, and we cut to the Klingon leader Kol, and then we end on a cliffhanger, and then at the beginning of the next episode the scene continues and everyone’s trying to figure out what to do about the Klingons, and Saru is there too, as First Officer, and

Wait, shouldn’t Saru be in the brig?”

Well, of course not. Because as per the Shelby Method, Saru did nothing mutinous within the last two camera shots, so what possible reason could there be for him to be in the brig?

Congratulations, you’ve just been Shelby’d.


Orders and Uniforms

So, let’s take a look at ‘Brother’, the first episode of DISCO’s second season, and let’s see if we can keep up, starting with the final moments of the ‘Previously On’ segment at the very start:

  1. Discovery enters maximum warp straight from Earth to Vulcan
  2. when twenty seconds later she picks up a Priority 1 distress call
  3. but the sender of the signal can’t communicate via audio or even transmit their registry number
  4. and it turns out to be the Enterprise
  5. and she’s Captain Pike’s ship
  6. with Spock aboard
  7. and we see the Enterprise approach Discovery under her own power with all her lights on
  8. and we cut to a montage of photos from space probes and telescopes
  9. and Burnham talks about an ancient (hundred-thousand year old???) story of creation
  10. and we see Burnham’s introduction to Sarek
  11. and then to Amanda
  12. and then to Anakin-Spock
  13. and then Anakin-Spock makes a holographic dragon float around the room
  14. and then he closes the door
  15. and then we’re back on Discovery
  16. and the Enterprise is completely disabled with no systems online and all her lights off
  17. except life support
  18. but all crew are alive, including Spock
  19. and it’s Tilly’s idea to communicate via Morse Code
  20. and Enterprise has just signalled via Morse that Captain Pike and an engineer and a science officer are beaming over
  21. and they beam over
  22. and Spock isn’t there
  23. and Pike takes command of Discovery under Starfleet’s orders
  24. and explains that he wanted to deliver the news himself and so asked Starfleet not to notify Discovery
  25. and the Enterprise engineer comments on how badass Discovery is
  26. and Pike explains that at least Enterprise picked up the new uniforms
  27. which Discovery‘s crew don’t have
  28. and Pike explains that Starfleet ordered Enterprise to investigate seven massive “red bursts” from all over the galaxy
  29. called “signals”
  30. which appeared simultaneously “over the past 24 hours”
  31. and then simultaneously disappeared, except for one
  32. which Discovery‘s crew has never heard of
  33. and Enterprise‘s science officer is arrogant in explaining the issues they cause
  34. and when they tried to scan the red bursts, their systems went haywire
  35. and Pike and Burnham talk about Spock
  36. and Linus the Saurian has a cold
  37. and we see Discovery‘s vast, lit-up, spacious roller coaster interior which is big enough for manned service pods
  38. and Saru theorises on the origin of the Red Bursts
  39. and the science officer explains that six hours ago
  40. one of the bursts “stabilised long enough to get a fix on its position”
  41. and Pike explains that they were on route
  42. when the ship’s systems completely shut down
  43. and that Starfleet is sending a team to tow the Enterprise home
  44. and then Pike asks Saru for his command codes
  45. and Saru explains that he can’t hand them over without a DNA test
  46. and then Linus sneezes on the arrogant science officer.

Okay, that’s a lot to take in. And maybe it all makes sense as you read it from top to bottom.

Lights on, lights off.

But, surprise surprise, all that formatting I added wasn’t random. Let’s put it together in a more categorised fashion, starting with all the reds:

  1. Discovery enters maximum warp straight from Earth to Vulcan
  2. when twenty seconds later she picks up a Priority 1 distress call
  3. and it turns out to be the Enterprise
  4. and we see the Enterprise approach Discovery under her own power with all her lights on
  5. and the Enterprise is completely disabled with no systems online and all her lights off
  6. and it’s Tilly’s idea to communicate via Morse Code
  7. and Pike takes command of Discovery under Starfleet’s orders
  8. and Pike explains that Starfleet ordered Enterprise to investigate seven massive “red bursts” from all over the galaxy
  9. which appeared simultaneously “over the past 24 hours”
  10. and then simultaneously disappeared, except for one
  11. and when they tried to scan the red bursts, their systems went haywire
  12. and the science officer explains that six hours ago
  13. one of the bursts “stabilised long enough to get a fix on its position”
  14. and Pike explains that they were on route
  15. when the ship’s systems completely shut down

So, here’s a question: what is the current state of the Enterprise? Are her systems completely down to the extent that they need Morse Code to communicate? She flew up to Discovery under her own power, but then her systems are completely dead except life support. All of her lights and engines are on as she approaches Discovery, at a time when she can’t even send an audio message, or even her registry number, but then they’re off less than two minutes later.

I guess Time Lords are canon in Trek now. Yes, that is a manned service pod flying around inside the hull of Discovery.

Maybe the underlined bits will help:

  1. when twenty seconds later she picks up a Priority 1 distress call
  2. but the sender of the signal can’t communicate via audio or even transmit their registry number
  3. and we see the Enterprise approach Discovery under her own power with all her lights on
  4. and the Enterprise is completely disabled with no systems online and all her lights off
  5. and it’s Tilly’s idea to communicate via Morse Code
  6. and Pike takes command of Discovery under Starfleet’s orders
  7. and explains that he wanted to deliver the news himself and so asked Starfleet not to notify Discovery
  8. and Pike explains that Starfleet ordered Enterprise to investigate seven massive “red bursts” from all over the galaxy
  9. and that Starfleet is sending a team to tow the Enterprise home

Well, now it seems like Pike had some extensive communications with Starfleet after the Enterprise‘s systems went completely down. Enough to transmit her status, to get a response, to request that Starfleet not contact Discovery themselves so that he can pass the message along, and gets a response about the status of the towing team, and then sends a garbled distress signal unable to even identify his own ship via its registry number.


Which all happened before the Enterprise lost all power to all her systems, because we see her travelling towards Discovery after the show establishes that her communications are completely down.

I’m struggling to get my head around this, so let’s have a look at the blue bits (with a bit of red in there, admittedly):

  1. Discovery enters maximum warp straight from Earth to Vulcan
  2. when twenty seconds later she picks up a Priority 1 distress call
  3. and Pike explains that at least Enterprise picked up the new uniforms
  4. which Discovery‘s crew don’t have
  5. and Pike explains that Starfleet ordered Enterprise to investigate seven massive “red bursts” from all over the galaxy
  6. which appeared simultaneously “over the past 24 hours”
  7. and then simultaneously disappeared, except for one
  8. which Discovery‘s crew has never heard of
  9. and the science officer explains that six hours ago
  10. one of the bursts “stabilised long enough to get a fix on its position”

Which means, whilst Discovery was at Earth, and all the crew were getting their medals, and Burnham was chatting with Sarek about that one time he tried to wipe out an entire civilisation, the blue uniforms with metallic division colours were the standard uniform. Then they beam up to the ship, head into warp, and somehow nobody told Starfleet’s most advanced starship about the Red Bursts, or about the change in uniform.


Meanwhile, we find out later that Enterprise sat out the war (as Starfleet’s “instrument of last resort”???? Despite the Klingon ships being in orbit over Earth????) on its five-year mission, presumably returning to Earth at some point before being dispatched to investigate the Red Bursts. Which would be a minimum of six hours before Discovery leaves Earth for Vulcan.

If it even returned to Earth at all. In any case:

  • How does Enterprise have the new uniforms before Discovery?
  • How does Enterprise know about the Red Bursts before Discovery?

If you can’t figure it out, then congratulations.

You’ve just been Shelby’d.

Magic Eyes

My previous examples took place over longer periods of time: several scenes and about twenty minutes of screen time in ‘Into Darkness’, and roughly five minutes and a handful of scenes in ‘Discovery’.

Now I want to take a look at a single-scene example, with the relevant events taking place within 66 seconds of each other.

So, under the command of Captain Pike, Discovery approaches a massive interstellar asteroid.

  1. Needing more information, they use telescopic cameras to take images of it
  2. and Burnham advises that the closer they are, the better a picture they can get
  3. so they move closer
  4. and as they do they cause a repulsive effect between them and the asteroid “like two similarly charged magnets”
  5. which pushes the asteroid onto a five-hour collision-course with a pulsar
  6. and then they detect a Starfleet vessel on the asteroid
  7. which they show in a zoomed-in digital overlay on the main viewscreen
  8. showing a crash-landed ship
  9. which they try hailing but get no response
  10. and they can’t zoom in any further to see the ship’s registry
  11. so Burnham reminds Saru that his eyes have “a larger optical window than [human eyes]”
  12. so Saru’s pupil dilates and he reads the registry number.

Well, by now you should know what’s coming next:

  1. Needing more information, they use telescopic cameras to take images of it
  2. and then they detect a Starfleet vessel on the asteroid
  3. which they show in a zoomed-in digital overlay on the main viewscreen
  4. and they can’t zoom in any further to see the ship’s registry
  5. so Burnham reminds Saru that his eyes have “a larger optical window than [human eyes]”
  6. so Saru’s pupil dilates and he reads the registry number.

So, does Saru’s vision allow him to… add pixels to the digital screen overlay?

If not, then couldn’t anyone read the display better by just walking closer towards it?

If it’s not a digital display, then why does it appear like a window popping up on a Macbook?


And in any case, are Saru’s eyes really better than high-tech cameras with telescopic lenses?

If you want to track this yourself, then go to time code 27:44 and start watching. Within one minute and six seconds, you’ll be at Saru’s pupil dilation.

Which means that within one minute and six seconds, within the same scene, with all the same cast members, on the same set, we introduce telescopic cameras, forget about them, zoom in digitally on a distant object, and Saru develops magic eyes.

What’s The Point?

So, why is the Shelby Method a thing, and why does it matter?

Well, it’s a staple of writers like Damon Lindelof and Alex Kurtzman and Roberto Orci, who have throughout their careers relied on overloading the audience with new information so quickly that the audience can’t pierce their baffling, confusing, often nonsensical storylines.

This lifts the burden of having to make sure their stories are in any way satisfying, cohesive or clever. This goes as far back as ‘Lost’, where new plot threads and mysteries were introduced every episode without ever being solved. And not just ‘Lost’ or ‘Star Trek’. For another defining example, go and take a look at ‘Prometheus’.

Crafting a smart, sensible story is difficult. And it takes a long time. And it often means that you have to sacrifice that cool thing you really want to include because it just doesn’t make sense.


A few years ago, a friend of mine was asking for advice on a medieval fantasy book they were writing. In it, their characters frequented a sailor’s tavern. My friend had lovingly described every detail of this tavern, from the trophy fish on the wall to the shanties that were sung to the all the nets and floats and fenders and other maritime trappings that added so much character to this wonderful setting. They were so in love with it, and justifiably so, that they had made it one of the main settings for their story – a comfortable port of call to which their characters frequently returned.

The problem?

The story all took place a hundred miles inland.

On the edge of an ancient desert.

My friend had asked me to help them figure out how to make this awesome maritime tavern fit within the narrative they had constructed. And I couldn’t. The best solution I could come up with was that it had been ironically decorated that way by its owners. Kind of a trendy hipster “out of place / fish out of water” bar. Which was hardly a satisfying explanation.

What I should have told them is:

“Don’t worry about it. Just introduce new plot elements every other sentence. Keep adding more events and details to your story. Move it along so fast that your readers don’t have time to wonder why a sailor’s tavern is a hundred miles inland next to a desert.”

My friend was having this quandary because they cared about the story they were telling. This was a passion project, and they wanted it to be as good as possible. This wasn’t some product they were churning out to hit a commercial target. They’d been labouring for years on the story that they wanted to tell.


If the writers of modern day Star Trek want to ignore the franchise’s larger continuity, then that’s up to them. If it gets in the way of them telling the story that they want to tell, then I say, go for it. Violate that canon. Every other entry into the franchise has done before them.

But here, in ‘Discovery’s second season, they can’t even be bothered to stick with their own continuity, even within the same scene. They make a cool thing happen. Then they need another cool thing to happen, but it contradicts the previous cool thing. Don’t worry – they just space the two cool things out with at least six lines of unrelated dialogue and they’re golden.

And if you didn’t notice, then congratulations.

You just got Shelby’d.

‘Star Trek: Discovery’s Season 2 Premiere ‘Brother’ Jumps The Shark By Being Pretty Good, Actually

Having just finished ‘Brother’, the first episode of ‘Star Trek: Discovery’s second season, I can confirm that my entire identity as a blog writer has been shattered.

I didn’t hate it.

This is a chaotic “first impressions” article as I pull my thoughts into coherence following a surprisingly enjoyable experience. I’m going to follow it up later in the week with a more cohesive look at what we’ve seen so far and where it fits within the show, as well as some of the “meta” problems that sit around it.

First, though, stray observations:

  • “Sometimes it’s wise to keep our expectations low, Commander. That way we’re never disappointed.” – Now that’s just not fair. If the show’s going to make fun of itself, then all the joy of doing so is gone for me.
  • Vulcan interior design! Brought to you by Ikea!
    • At first I thought Sarek’s home looked horribly un-Vulcan. Then I realised “Duh! Of course it does! He’s the Vulcan ambassador to Earth, this’ll be in North America somewhere!” Then Amanda promises to take Michael to Earth, where she’s never been, and I groaned with frustration.


  • Tilly has somehow forgotten every bit of character development she had in the last season and is now back to being disturbingly awkward and socially incapable.
  • Airiam, still the ship’s third-highest ranked officer, doubles her line count TO DATE by speaking her name. And then triples it when talking about a power cable.
    • Also, I can only assume that her first name is “Lieutenant Commander”, or she just ignored Pike when he asked them all to forget their ranks.
  • Pike and the Enterprise crew got the new uniforms (although he still changes into the old DISCO-style ones at the end of the episode) but hasn’t Discovery literally just left Earth? And Enterprise has been on its mission? So, why didn’t Discovery’s crew get the uniforms before they left? How did Enterprise get them first? Ah, whatever.
  • Detmer and Owosekun get lines! Multiple lines! They even talk to each other! Such progress! It is 2019.
  • “Red thing! Where’s my damn red thing?” How did you become a captain exactly, Pike?
  • The “interstellar asteroid” is travelling at “5000 km/s”. Voyager 2 is currently travelling at roughly 16 km/s. Which means… no, that actually checks out. Wait, did ‘Discovery’ just get a science measurement roughly correct?
  • One of Discovery’s design features is apparently “telescopic cameras,” and the line delivery implies that this is a non-standard feature. That’s right! Starfleet’s most advanced ship has reached an equivalent technology level to 1960’s paparazzi!
  • They then have to get Saru to look at the crashed ship’s registry with his superior eyes because this is ‘Discovery’ and all prior information is rendered null and void as soon as we cut to the next shot.
    • Which… he’s looking at an electronically-enhanced image on the viewscreen anyway, so… what, do his eyes multiply the pixels on a viewscreen? Guy could’ve been a champion professional gamer in that case.
  • “Really? Are you surprised?” asks Saru, as a bridge officer looks at his extruding threat ganglia. Well, yes, actually, Saru, your bloody threat ganglia never shot off all those other times you were about to die in Season One, so, yes, I am pretty fucking surprised.
  • Also, Saru briefly transmorphs into C-3PO for some “The odds of surviving…” banter.
  • I adore Commander Reno and I would like to have her babies – and she seems to have the capability to make that happen biologically. She had better be a recurring character or I may have to take drastic action.
  • Michael’s helmet-hair is adorable.
    • And, I know I’m trash, but I still really miss her lovely fringe (or “bangs”) from ‘The Vulcan Hello’. That was such a nice hairstyle on her.
  • Apparently, the first couple of episodes of this season blew more than half the budget for the entire season, and with Burnham’s desperate escape from the exploding wreckage, I can see how. Jesus, that was an extravagant scene.
  • There’s problem-solving! And obstacles to overcome! What is this, a Star Trek show all of a sudden?
  • Poor old Enterprise, busted up and being towed home. Farewell, sweet princess, we shall see you at some plot-convenient point later, I can only assume.
  • There were NO LONG, POINTLESS FIGHT SCENES. Hell, there wasn’t even any shooting! It’s almost as though compelling science fiction doesn’t need people stabbing each other to be good.
  • Spock’s quarters aboard the Enterprise have some lovely little nods to the old sets of ‘The Original Series’. Those brass circle-pattern screens particularly.


Right, that’s enough bullet points. Let’s get down to business.

What’s Going On?

Good question.

So, despite the Enterprise flying up to Discovery at the end of last season under its own power and with all its lights on, in the time it takes Tilly to be a bumbling dickhead apparently Enterprise shuts down completely. Almost as though the writers had no idea what they were doing last season and just jammed the Enterprise in at the end for a fanservicey cliffhanger.

But that’s okay, because Pike says the Enterprise was sent here to take command of Discovery. Even though the Enterprise’s systems were down so completely that they could barely transmit their registry number, they nonetheless conversed with Starfleet Command, located on Earth, from where Discovery had moments earlier departed, and got orders to intercept Discovery on her way to Vulcan, despite all her systems going completely offline with no explanation at some random point, and, with her systems still offline, flew up to Discovery, broadcasting a Priority One distress call, but then died completely, but they still picked up the colourful new uniforms along the way, and then…

I’ve lost track.


Look, the first half of this 60-minute episode is a mess. In fact, that doesn’t do it justice. It’s a complete fucking Kurtzman is what it is. A massive steaming Kurtzman, with a magnitude of about 16.3 Lindelofs.

None of it makes sense, and it seems like there were a lot of re-writes and re-shoots to make it even nearly comprehensible. None of the writers really seem to know how to get Pike onto Discovery to achieve the appropriate level of fanservice demanded by their studio overlords, so they just keep throwing plot points out like narrative diarrhoea in the hope that the audience will gloss over it all and just keep drooling into their laps.

They also, clearly, have no idea of what to do with Sarek, as he has a moment with Burnham where he explains that he’s going to leave Discovery as soon as she drops out of warp, but then they drop out of warp into a Dark Matter debris field and immediately get the shit smacked out of them but Sarek still never appears again, but we never see him leave, so didheleaveordidhestickaroundforabitandwherewashisshipdidhetakeashuttleorIdon’tknowwhat’sgoingonpleasehelpmeJasonJasonJasonJasonJasonJasonJasonJASONjasonjasonJasonJASonJasonJaSON.

Let’s move on.

Commander Reno

Ah, Commander Jet Reno.

Just like Captain Georgiou before you, you are FAR too good for this show.


First off, “Jet Reno” is the best name ever.

Second, God damn you are one competent motherfucker.

I’m a bit skeptical of “the body’s just a machine and I read a lot” explanation for an engineer carrying out BRAIN SURGERY but y’know what? Fuck it, maybe she’s just that smart. I love her. I love her so much.

She responds to Pike’s “You stayed behind?” with exactly the right amount of contempt and fuck-youery to cement her as a fundamental Starfleet disciple.


She delivers every line with the perfect degree of deadpan pragmatism.

I haven’t done any research on whether or not we’ll see her again, and I don’t intend to, as the hope of seeing her returning and bossing all of these simpletons around will be the one thing that keeps me going through this entire god damn season.

For those who aren’t watching the show: we meet Jet Reno on a wrecked hospital ship, stranded on an asteroid eleven months earlier in the opening stages of the war with the Klingons. When the ship was wrecked, most of the crew and the patients left in escape pods, but some of the wounded were in too bad of shape to leave that way.

So Jet Reno, star commander and steel-hided badass, stays behind, on her own, to keep the ship’s systems going and look after the patients. In that time, she improvises floating worker drones to help her with manual labour, and somehow figures out how to run a human off a Bolian heart.

She keeps the beating heart in a jar.


She fits Star Trek’s optimistic vision of humanity’s future so perfectly that I can barely believe she appeared in ‘Discovery’. She’s tough, capable and compassionate, and I am completely fine with her becoming the template for all future characterisation within this show.

Emotional Attachment

The acting was another wonderful element to this episode.

I liked Alan Tudyk’s Anthony Rapp’s performance in Season One. And I loved it here. He brought a fantastic degree of pathos and thoughtfulness to the recently-bereaved Stamets, struggling to cope with living in a claustrophobic environment in which his partner was recently murdered. I felt genuinely sorry for him, and shared in his grief.

Sonequa Martin-Green was variable. There were some great touches, such as her grinding her teeth as she thinks about her troubled relationship with Spock. But later in the episode, she seems to suffer from the bobble-head syndrome that plagues so many actors. That may have been a result of the director, however, and I’ll not condemn her for it unless it becomes a pattern.

Anson Mount gave a lovely turn as Captain Pike. We’ll talk about the more general issues with Pike in a bit, but from an acting perspective he was pretty much spot-on. He’s casually likeable and seems like a nice guy to talk to at a barbecue or to be stuck in a turbolift with.

Detmer and Owosekun (Emily Coutts and Oyin Oladejo) can actually act! I know you would never have guessed it given the eight-and-a-half “status update” lines they had between them in the first season, but here they get at least that many lines each, and they seem to be enjoying themselves. Keep it up, ‘Discovery’, and soon you’ll almost be an actual feminist show!


Burnham and Tilly have a lovely moment in sickbay. They seem like genuine friends, with real affection for one another, and they excitedly talk about science shit, and they seem almost exactly like what you’d expect to see in a good Star Trek show made within the last ten years. And, Tilly gets her terrible “The power of maths!” line out of the way with in this episode, and it is terrible, but at least it’s out of the way with early on and I don’t have to spend the next few weeks dreading its arrival

What is this? It’s like I’m having feelings about ‘Discovery’, but they aren’t bad, horrible feelings that burn like a smouldering, fitful rage. They’re nice feelings, almost like I’m rooting for these characters and want to get to know them better. I didn’t finish the episode depressed. I actually want to see more.

I’m scared.

Philippa Georgiou – The Best Captain That Star Trek Never Had




Well, a new season of ‘Discovery’ is about to start, which means that I, like an alien scout vessel in a secret research base as larger alien motherships approach the Earth, am regaining my writing power – all my little gizmos are turning back on, so to speak. Was that a stretched and esoteric reference to Brent Spiner’s role in ‘Independence Day’? Yes. Am I going to apologies for it? No.

Right from my very first article about ‘Discovery’, I argued that the show should’ve been about Philippa Georgiou. That was literally the first two paragraphs I ever wrote about the show. Since then, a lot has happened. The show got a second season. New spin-offs have been announced. I’ve had surgery on my genitals. The world is a different place, but one thing remains the same:

‘Discovery’ should still have been about Philippa Georgiou.


I’m not going to talk about the just-released Section 31 series starring Michelle Yeoh in this article. It’s exhausting enough just hating on the Trek that already exists, and I simply don’t have the energy to hate on a show that doesn’t even have a title yet.

(I do hate it, though. It’s about a genocidal future space fascist who tortures her political enemies joining forces with a genocidal future crypto-fascist black ops team of edgelords and it’s going to be terrible.)

No, I want to stay positive this time, and that’s exactly what I’m going to do. Captain Georgiou only featured in two episodes of Star Trek ever (three if you count her hologram) but she’s frankly one of my favourite characters from the franchise. Let’s talk about why.

The cold open to ‘Discovery’ was my absolute favourite bit from the entire fifteen-episode season. It was lovely. It had as much respect for the Prime Directive as any series before it and I was glad. The Prime Directive is trash. It’s stupid, ugly trash, and it is a good thing when the Prime Directive is violated. (Except for that weird one where the rogue captain turned all the natives in Nazis, but we can rightfully gloss over that for now.)


The highlight was Georgiou walking out the Starfleet Delta in the sand so that the Shenzhou could find her and Burnham. It was a simple, intelligent solution to the problem they were facing. SURE, there are a few plot holes in there somewhere, but hell with it, it was what I wanted from the show – characters using their wits to work their way out of difficult situations.

And what’s great is the characterisation of Georgiou throughout the two pilot episodes. Michelle Yeoh owns the part. She figures out a plan and just executes it calmly. She doesn’t flap, she doesn’t lose her cool. She’s thoughtful, lighthearted and calming, whilst also owning any space she’s in. Where Jean Luc rarely leaves the few central square feet of the bridge of the Enterprise, fixing himself as the central point of authority, Georgiou strides about with an easy confidence.

There’s a lovely little line where, as Burnham is flying through the debris field in her EVA suit, one of the bridge officers remarks that her heart rate is high. Georgiou responds with a smile, “She’s having fun.” She makes clear that she has an intimate familiarity with her officers, far more friendly than Picard or Janeway, and more parental than Sisko’s more casual relationships.


Indeed, of all the captains, Georgiou seems closest to Kirk more than any other. Just as ol’ James T. was a charismatic leader who won his crew over with a wink and a smile, Georgiou laughs and jokes with her people. It seems like it would just be good fun to be an officer on the Shenzhou, compared to the increased formality of life aboard the Enterprise D, or the spartan utilitarianism of the Defiant. Or the rampant space-nobbery of the NX-01.

There’s another fantastic exchange between Georgiou and Burnham shortly before the Klingon beacon lights in ‘The Vulcan Hello’:

Georgiou:Shenzhou is the only line of defence if the Klingons attack.”

Burnham: “Not if. When.”

Georgiou: “I have to hope that whatever happens here can serve as a bridge between our civilisations.”

Burnham:”That’s the diplomat in you talking. What does the soldier say?”

Georgiou: “Nothing good.”

This little exchange here is what the entire show should’ve been about. There’s so much weight and theme within it that I can barely believe it came out of an episode of ‘Discovery’. Let’s break it down.


Burnham’s correction, her assertion that a Klingon attack is guaranteed, is a classic support-character argument. Offering a contrasting point of view, usually a more pessimistic one, that the main character overcomes with their own reasoning. Georgiou counters with a classic bit of Trek peace-mongering: “… serve as a bridge between our civilisations.

A bridge between civilisations. A belief that there is more that unites us than divides us.

This should have been the message of ‘Discovery’. That for all of the contrasts between Klingon and Federation culture, even after a bloody conflict common ground can be found. As I’ve already covered, that was not the ultimate message of the show, and that was a great shame, because we see the germ of something wonderful in the very first episode, before it’s discarded in favour of stabbing, torture, rape and plot twists.

This is reinforced by the next lines. “That’s the diplomat… What does the soldier say?” And again, this right here succinctly addresses one of the great conflicts of the franchise to date – that of a militaristic organisation such as Starfleet being employed in the name of science and exploration.

Acknowledging this duality in Georgiou, that she must act in equal measure as a builder of bridges and a guardian against conquest, could’ve been a wonderful character arc. Had she lived, we might have seen her dealing with the Klingon war in a way not yet explored by previous series.


Sisko was always a soldier. The genesis of his character was in battle at Wolf-359. He started out as a wounded veteran, embittered and robust. The Dominion War was an extension of his character – we see the war (mostly) through his eyes, the eyes of a soldier, and so we never see any internal conflict within him the way we would with, say, Picard or Janeway.

Georgiou could have offered fresh perspective. We could have examined the two halves of her career and how they interact. Maybe one episode could have featured the Shenzhou visiting a backwater planet, where Georgiou has to convince its inhabitants to join Starfleet and fight in the war, or maybe she’s even there to outright conscript young fighters as losses mount and desperation sets in. We see her using her skills as a negotiator to convince people to join her cause, knowing that many of them will never return, and we face her torment as she does so, weighing the need to win the war against the cost of fuelling it with more lives, more casualties.

All of the previous captains represented different military virtues – Kirk embodied intrepidity and determination. Picard was the model of discipline and responsibility. Sisko was all about duty, whilst Janeway stood for principles (most of the time). Meanwhile, Archer… I guess Archer represented authoritarianism or something. I dunno, I was never too sure about him.

The point is that it would have been so lovely to find out what Georgiou represented within this pantheon. If Kirk is the God of Leaping Before Looking, maybe Georgiou would have been the Goddess of Skill, or Adaptability, or Cunning.

Oh my.

Another wonderful aspect of Captain Georgiou that we see in these first two episodes is a great deal of doubt and uncertainty as she is faced with unfamiliar challenges. She visibly struggles to figure out the next best move, and leans heavily on Saru and Burnham to inform her decisions and to advise her. This absolutely humanises her, and makes her so much more accessible as a character.

Both Picard and Janeway were too formal and rigid, particularly early on in their respective shows, for an audience to truly connect with them. Hell, it’s Season 4 of TNG before we get to ‘Family’, which is the first real moment of vulnerability we see in Picard. Kirk goes the other way, being so effortlessly charismatic and unfazed that he seems almost superhuman. Sisko’s most humanising feature was his relationship with Jake, and their shared loss of Jennifer.

In Georgiou, we see a competent and smart individual nonetheless struggling to overcome strange and dangerous obstacles. She’s vulnerable, without being weak or incapable. And most of all, her motivations are clear – to resolve this situation without starting a war, maybe even forging a new relationship with an enigmatic alien culture.

Georgiou showed so much potential just in those first two episodes, that it now makes me genuinely a little sad to know we’ll not see her again. Yes, we’ll still see Michelle Yeoh, as the cannibalistic, sadistic and morally bankrupt fascist tyrant Emperor Georgiou, who is the mirror in every way to the quiet confidence of Captain Georgiou. And Yeoh plays both parts well, for sure. But I genuinely think that Captain Georgiou could have easily stood at the level of any of her predecessors in all of those “Who Is The Best Captain” debates had she been given the chance.

More than anything, it was just a joy to watch a charismatic leader solving problems and facing difficult situations. That was a show to which I would have given my heart, and I wonder now if all of the bitterness towards ‘Discovery’ stems from the narrative betrayal of the show’s creators in having Georgiou killed off so early on.

Oh well. At least some part of that dream might live on in this new Section 31 series.

But probably not.


Roland Emmerich Announces Next Blockbuster Disaster Movie: “It’s just gonna be a big window.”

Roland Emmerich (‘Independence Day’, ‘2012’, ‘The Day After Tomorrow’) today announced his next big blockbuster project, titled ‘Now’. and due to release every year for the next fifty-to-one-hundred years. Starring Jake Gyllenhal, Judd Hirsch, Vivica Fox and every other living human on the planet, this new project looks set to be a big hit.

Emmerich: “We were working hard coming up with ideas for some kind of horrifying, climactic end for humanity. Then I saw one of the writers gazing out of the window , and suddenly I realised, ‘Hey, that’s it! That’s the scariest disaster we could possibly show!”

Pushing the boundaries of contemporary film-making, ‘Now’ is set to have an indefinite run-time, although it’s likely to end sometime before any of us get chance to die from old age. Emmerich was also excited to talk about the film’s unique presentation style, following in the footsteps of other directors such as Peter Jackson, James Cameron and Quentin Tarantino.

Emmerich: “A lot of people are going to call it a gimmick or a fad, like Peter’s 48fps thing or Tarantino’s 72mm schtick for ‘Hateful Eight’, but what we’re doing with this one is really part of the whole experience, it shapes it, really uniquely. What we’re doing is allowing the audience to watch the calamity unfold, in ultra-high-def, fully-immersive 3D, and at 100% real-time, with the eye’s natural framerate of up to 60fps.”

Emmerich explained further, covering the radical alterations that most movie theatres will need to make to accommodate his new film.

Emmerich: “It’s just gonna be a big window. One massive hole in the wall. We’re considering putting glass in, but there’s also plenty of opportunity for the full 4D experience, where audiences can actually feel the global temperatures getting higher for themselves, and smell the decay of society as it wafts into the auditorium. I want everyone to be able to feel the increased intensity of each successive hurricane, and watch as arable soil turns to dusty wasteland – I want them to taste the ashes of global conflict as they fall from the sky.”

Concerns have been raised by the studio over whether audiences will be willing to endure a possibly endless show, running for years and years as the inevitable collapse of society approaches. Emmerich was untroubled by these concerns, stating flatly “The audience will have no choice but to sit through it.”

So keep an eye out for ‘Now’, the exciting new cinema experience, as it hits your nearest cinema. Critics are already giving it rave reviews, having unwittingly experienced it already for at least the last decade.

“You may as well pay to see another fucking Emmerich indulge-athon,” said one movie reviewer, “it’s not as though money’s going to mean anything in a few years’ time anyway. I don’t even  give a shit if it’s any good or not, I’m going to use my savings to buy as much cocaine as possible and spend whatever time I have left smashed off my tits, rolling from one sweaty orgy to another until my heart gives out. It’ll be better than waiting for the lakes to dry, or for that nutter in the White House to fuck us all with an endless trade war. Or an actual war.”

Exciting stuff!