Read Next

I Bought an RV!

A short while I ago, as an aside, I mentioned that I might be buying an RV to live in. It seemed like a good idea, so every day I checked ebay to see what sorts of deals were to be had. I wasn't ready to buy, but I figured it would be good to know what's available for when the condo sold.

I sat in my living room chatting with some friends on AIM when one of them brought up the RV idea. While I explained it to them I opened up ebay. By default it shows the most recently listed RVs on top. The very top one was an R-Vision Trail Lite, one of the few models I'd really liked. I glanced over at the price and it was $14,000, less than half of what they usually go for. There must be something wrong with it.

I opened the listing and read through the description. The front "shotgun" seat was missing. No big deal. They'd backed into something and the fiberglass around the tail light was cracked. No big deal. The couch wasn't the one specifically made for the RV. No big deal.

Lessons Learned from the Firestorm of Controversy


Two days ago I wrote the Genius and Tragedy post. It was extremely controversial - very popular on one hand, but got some very strong visceral negative reactions. I'd like to share with you what I've learned about writing, so I can step my game up and improve. Also, I got some downright hateful comments made about me, some really bad and terrible stuff. If this has never happened to you, maybe you don't know what it feels like, and I've got some advice on how to deal with it. I also did some detailed reading and analysis of the kinds of comments I got, and there was some fascinating results that I'll share.

So, first and foremost, I made a mistake - If you're writing to help someone, it can be pretty presumptuous to do it without touching base and clearing it with them first. I made that error for a few reasons - first, two of my best posts have come from the same format, and both achieved their desired objective. ("How do I write so much, you ask?" and "I think greatness is something you do, not something you are" both publicly called people I like out - and both times it worked) - so that's the first thing, I'd had a good track record with this, however those were people I'd been touching base with already.

Second, as a general principal I believe in working really quickly. I analogize it to "fighting out of formation" - quick, lightly edited writing is always worse than well-edited best practices. But, the more you do of it, the better you get at it. And by producing anything really quickly, you get better faster. If someone produces 10 times as much content, how long until their lightly edited work is superior to the other person's highly polished work? This isn't a rhetorical question - check out "Quantity Always Trumps Quality" on codinghorror.com sometime. If you produce quickly and of lower quality at first, you can iterate and improve, and eventually your quick production work is better than the obsessively refined person's work who isn't getting as much done (and thus not learning the lessons). Pablo Picasso talked about this quite a bit, if you're particularly interested on the topic.

The downside, of course, is that you make mistakes. And I did - I should've touched base before writing that post, or had it vetted, or at least, spent more time editing it to be clear, concise, and unambiguous, and even more polite. Mea culpa - my mistake! It's okay for me to work quickly and bring errors upon myself because of it, but I need to be more careful when involving others.

Then, why is that post still up? This is what I wrote as the episode was winding down, it was well-received by the community -

Rendering New Theme...