clock menu more-arrow no yes mobile

Filed under:

FINAL: Diamondbacks 8, Rockies 7

In which our poor writer has a finished recap in the top of the 9th, only to see it go up in flames. But hey, Diamondback win!

Ron Chenoy-USA TODAY Sports

Anyone who has written a recap or a game report knows the drill. You watch the game, you take in impressions, you quickly start writing before the game ends because frankly you want to go home or go to bed or to get black out drunk.

Most of the time this works out just fine. You start writing in the 8th, or maybe a little earlier if it's a blowout, and finish up just as the game ends. You file it to your editor, or you post it online without any oversight, and everything is as it should.

Sometimes, though, you write up a recap, and then the score changes. And it's already been a long game because of a rain delay before first pitch, and then there was rain in the middle of the game. And you've already been up since 3am, and you have a real grown-up job you have to go to, and so you're writing this recap hoping that it goes quickly even if it means a Diamondbacks loss.

Sure, back in the 5th inning when the D-backs were up 5-3 you wanted a win, but now you just want the darkness to close around you and for it to end. Instead, the Rockies bullpen becomes the U2 of bullpens and manages to give up a run to cut the lead to 7-6, then walk in the tying run, then give up the go-ahead run to ultimate lose the game.

And you're happy the Diamondbacks, but also kind of not? Because now you have to start over again, and it's 10:30 and dammit, you just want some sleep. Instead you're retooling a recap that no one will read, and few will comment, because everyone always comments on the quick recap. And you know that's the way of things, but you can't help but feel a little blue because what's the point in writing 2 recaps anyways?

But you do it anyways, because it's a game in June and people need their Content.