Fan Film Factor

SPOILERS ARE JUST AN UNAVOIDABLE FACT OF LIFE

Last week, I truly LOVED the second-to-last episode of STAR TREK: DISCOVERY‘s third season, “There Is a Tide.” With so much happening going into the final episode, my hopes were high. Tilly and the bridge crew, along with the DOT-bot “army” still had to retake the ship from Oysraa. Michael had just been captured by Zareh while Book was already a hostage on the bridge. Osyraa was cornered, outnumbered by Starfleet vessels that could blow Discovery out of the sky (well, space) but holding the most valuable bargaining chip: the spore drive. But she couldn’t jump away because Stamets (against his will) was ejected from the ship by Michael…setting up lord-knows-how-many future fireworks between the two! Meanwhile, Saru, Culber, and Adira were stuck on the dilithium planet with the Kelpien equivalent of Black Bolt, trying to save the galaxy before dying of radiation poisoning. The clock was ticking!!!

With a set-up like that, what could possibly go wrong with the finale?

It’s hard to know where to start…or stop…or start…or stop again. I say it that way because that’s kinda how I felt as I watched the full 60-minute episode (the longest of the season). Have you ever ridden with a teen just learning to drive a car and they speed up and slow down and speed up and slow down over and over so much that it’s all you can do to hold down your last meal? The finale was kinda like that.

There was ample action—AMPLE!!!—lots of running and shooting and explosions and fighting and kicking people out of elevators and crew members suffocating and people running out of time and gosh darn it…things just moved at maximum warp.

And then there was Su’Kal. Gotta keep that kid calm lest he scream and destroy the galaxy again! So everything in the holo-chamber on the dilithium planet was super serene and slow, with lots of empathy and understanding from Saru and the others. Nothing necessarily wrong with that.

NEW YEAR, NEW SPOILERS

I know that some of you out there read my editorial reviews either before or instead of watching STAR TREK: DISCOVERY. This time, please take my word for it: don’t. Watch the episode first. And if you don’t usually watch Discovery or gave up on it (and if you have access), just watch this one episode. You don’t need to have watched the rest of the series or even the third season. This episode provides enough exposition along the way that you won’t feel lost.

It’s just a damn fine, exciting, fast-paced, engaging, well-crafted, and most of all highly entertaining piece of television that is loaded with surprises and the unexpected. So just watch it…trust me.

In fact, “unexpected” serves a very appropriate way to begin this blog because, even though I usually try hard to go into each new episode of Discovery open to anything and with no preconceived expectations, this time I was sooooo sure I knew what was coming! This would be Discovery‘s version of the TNG episode “Starship Mine.” Tilly, reeling from her dismal failure during her first command, would need all the help and hugs her bridge crew friends could give her as she proved herself by leading a successful plan to retake the ship. I was even thinking of titling this blog “How Tilly Got Her Groove Back”—that is, until I actually saw the episode.

From the first moment, the episode had me hooked with things I didn’t see coming. Using Discovery as a Trojan Horse to get inside Starfleet’s defense shield by “coming in hot,” being fired on by Osyraa’s dreadnought, communications jammed…brilliantly simple and simply brilliant! But then, as Book and Michael crashed into the hangar bay in the nick of time, I thought: “Wait, what about Discovery‘s shields? They were being fired on, why wouldn’t the shields be up?” So then I thought I’d write another nitpicking blog…those are always popular on Facebook! (Actually, I’m being sarcastic. My Guardian of Forever “Time Error” blog was royally bashed on Facebook.)

But then we came back after the opening credits to see this little nugget…

Award a point to the writers for addressing my gripe so quickly!

Okay, with my nitpicking nullified, I decided to just sit back, enjoy the episode, and write the blog later—and so I did. This was the seventh episode of the series and third this season directed by JONATHAN FRAKES, and I must say, the man knows what he’s doing. The episode was written by co-executive producer KENNETH LIN. Interestingly, Lin wrote and Frakes directed the 8th episode of the season, “Sanctuary,” where the crew goes back to Book’s home planet. Most fans found that episode somewhat mediocre (including me), but this episode was much the opposite, demonstrating that you can’t just an episode simply by the writer and director. Sometimes magic just happens.

Let’s look at how…

LET’S END THE YEAR WITH…SPOILERS!

I’ve often (often!) wondered would STAR TREK: DISCOVERY would be like if it were more like the classic Star Trek I grew up with on TOS and even TNG. I’m not talking a total homage like The Orville (where the heck IS that show anyway???) but more simply carrying through on certain story elements, structure, character interplay and development, and just the overall “feel” like they used to have in the “good ol’ days.”

For what seemed like one of the only times in the three seasons of Discovery, this episode FELT like Star Trek to me. But what does that even mean “felt” like Star Trek? It seems like such a subjective and ambiguous thing, possibly different in the mind of each Trek fan watching.

So let me tell you why I personally thought that the 11th episode of season three, “Su’kal,” felt more like real Star Trek than Discovery usually does. And along the way, I’ll try to decide if this was a good or bad episode…or both! (Knowing me, it’ll probably have aspects of both—as I seem to have difficulty committing to either loving or hating the episodes this season.)

Okay, let’s do this thing…

MOVING TO MORE MODERATE AMOUNTS OF MICHAEL

Fans couldn’t help but notice that, for the past nearly-three seasons, Discovery has felt like “The Michael Burnham Show, starring Michael Burnham as Michael Burnham.” Michael seems to be in almost every scene, usually is the center of attention, and she saves the day regularly.

One of the reasons that Star Trek‘s previous iterations worked so well is because they had a variety different characters spotlighted in different episodes. Not every TOS story was about Kirk, not every TNG about Picard nor every DS9 about Sisko nor Voyager about Janeway. There were Spock and McCoy-focused episodes, Data and Worf and Crusher episodes, Kirk and Odo and Bashir episodes, Tuvok and Paris and B’Elanna episodes, T’Pol and Malcolm and Phlox episodes…you get the idea. And just because one character was featured prominently in a story didn’t mean we wouldn’t see the rest of the crew. A Riker episode would also show the rest of the crew. Mix and match! These shows had great casts, and the captain didn’t need to be in every scene.

This episode of Discovery was the first time in a while that Michael wasn’t dead center of the action almost all the time. Excitement was also happening on the ship, and because the landing party beams down and splits up, Michael is only part of the story on the planet. Michael definitely gets some major stuff to do, but so do Saru and Culber…giving each of their characters some breathing space. On the ship, we see some great moments for Stamets, Tilly, and Adira (and one single line from Reno…really?).