don’t say you’re sorry
July 15, 2014 6 Comments
Gawker published a story over a year ago entitled “Michael Bay Is Sorry About Armageddon“. The story explains how Bay first apologized for the movie, and then later retracted said apology.
Both were weak moves. Here’s why.
I’m no fan of Armageddon. I think it’s one of the worst films I’ve paid good money to see. It was cliche, emotionally manipulative in all the wrong ways, and ultimately stupid in regard to both character development and story arc. That said, it was his. His work. His art.
(I’m tempted to say something about ‘art’ being used loosely, but just because I hated something with the fire of a thousand suns doesn’t mean everyone hates it. Some people liked Armageddon, and that’s just fine.)
He should have stood by it.
Having thrown his own baby under the bus, he should have left it there, not retracted the apology later in some half-ass attempt to save face. That move made him look even worse.
A couple of weeks ago, I posted one of the first serious fiction stories I wrote. It’s far from my best work, but I stand by it. You should stand by your work, too. Don’t ever apologize for it. If it’s not your best stuff, that’s fine. The process of writing includes highs and lows. You won’t always knock it out of the park. Don’t feel the need to be either apologetic or defensive of your lesser efforts. It’s all art, and it’s all yours.
Never, never, never say you’re sorry for what you wrote.
Say you’d do it differently now. Say you’d change some things. Say you’ve grown as a writer. Say you’ve penned better tales.
But don’t say you’re sorry. Ever.