This editorial contains spoilers for Source Code. Consider yourself warned, and consider yourself given another excuse to go see the movie. You’re waiting for a train, a train that will take you far away. You know where you hope this train will take you, but you don’t know for sure. But it doesn’t matter. How can it not matter to you where that train will take you? Because that train is going to explode, killing everyone on it. In fact, that train has already exploded, but you’re waiting to board it in a very peculiar way. You’re Colter Stevens from Source Code, and you have a ticket in your pocket because a man who was on the train earlier in the day (when it blew sky high) has a ticket in his pocket. Your mind is inside the short term memory of a dead man. Source Code plays around with identity philosophy in at least three key ways, and it seems directly influenced by the story of a man who loses his head in order to play hero. Hold on tight to your brain, and let’s try to find Colter.

Editor’s Note: This editorial contains spoilers for Source Code, so if you haven’t seen it 1) you should and 2) you probably won’t get the jokes either. It comes from guest writer James Kopecky who has thought far too much about what happened at the end of Duncan Jones’s latest. When I see a movie, I take it as a two-hour-long glimpse into a reality that has a rich history, as well as an ongoing, unwritten future. After the credits roll, I assume that the characters and the story keep moving, most likely in the direction they were headed when the picture ended. So when I saw Source Code, I thought about what happened to the characters after screen faded to black. This turned out to be problematic for me, because the ending of Source Code raised a slew of questions, some more perplexing than others.