Commodore Wesley confuses me

Discussion in 'Star Trek - The Original & Animated Series' started by Sadara, Mar 18, 2013.

  1. HarryM

    HarryM Fleet Captain Fleet Captain

    Jul 20, 2007
    Old Earth
    For what it's worth I really never thought much about Wesley anyways (besides an underlying annoyance with him), the episode overall is solid. And Wesley does redeem himself in the end by guessing that Enterprise is disabled and it's not a trap.
  2. Timo

    Timo Admiral Admiral

    Aug 26, 2003
    I'm game. And yes, I'll be in the "plausible character development, logical choices, good leadership" camp. :devil:

    Timo Saloniemi
  3. CrazyMatt

    CrazyMatt Captain Captain

    Feb 21, 2013
    Trying to focus....
    I don't know why people are ragging on this episode... it's easily the best from the 2nd half of the second season. Whether he's the Lexington's actual captain or not, Wesley comes off as a very good starship (fleet?) commander, and while he's a bit anal at times (the "Captain Dunsel" comment comes to mind), at least he's not gone crazy like Matt Decker or Ron Tracey.
  4. Marsden

    Marsden Commodore Commodore

    Feb 23, 2013
    Will be Celebrating Spocktoberfest this year!
    I think it's a solid episode and posts that accuse it of "bad writing" are painful to see.
  5. Maurice

    Maurice Vice Admiral Admiral

    Oct 17, 2005
    Walking distance from Starfleet HQ
    It's bad writing because it's not thought out logically. I give D.C. the benefit of the doubt because of the speed at which teleplays are produced, but that doesn't mean the flaws aren't there.
  6. Duncan MacLeod

    Duncan MacLeod Fleet Captain Fleet Captain

    Feb 24, 2002
    New England
    Well John Masefield's Sea-Fever is a magnificent poem. I'm glad that Star Trek quoted it, otherwise I might never have learned it. And that would be a sad state of affairs indeed.

    For anyone interested in reading the whole work:

  7. Jerikka Dawn

    Jerikka Dawn Commander Red Shirt

    Jul 1, 2004
    I thought this episode was great especially now that I've viewed it after seeing TNG and DS9. I got a real kick out of seeing the crew behave, in light of what we see on TNG, as complete neophytes when it comes to new technology. The funniest part was seeing Scotty lose his shit over the M5 shutting off lights in unoccupied parts of the ship to save power. Who doesn't think that every starship, at least in the 24th century, doesn't have this feature in their computer system?

    We can almost be certain the E-D's navigation system and mission operations computers do this. There are probably entire subroutines for different away team/mission scenarios that present mission commanders with recommendations upon approach to the planet and inform department heads of important updates.

    This is exactly how every TNG era ship works. The CON officer is babysitting cruise control and GPS.

    It also made me realize just how far behind TOS tech is from TNG tech and the fact that most of the crew on the TOS Enterprise was needed just to keep the thing moving, while on the TNG Enterprise, while they had a huger crew, it was more about mission specialization with regard to exploration, and probably only a handful of those 1014 people were required to actually run the ship.

    It is good that by TNGs time, however, manual overrides were improved (somewhat) and they kept a human crew to actually make the decisions while keeping all of the good advances. I guess it would have been kinda cool in "Booby Trap" to have Picard scoff at the idea of turning the ship over to the computer and maybe reference the M5 incident.