Editor Log: February 2005

Poetry's a tough thing to do well, both here on Everything and in the real world. This has a lot to do with the fact that people like what they like and, for the most part, don't put much thought into why a poem strikes a particular chord. Words can float or sink depending on variables that are hard to quantify and the consensus seems to be that it works when it works and it sucks when it sucks and the line between the two is negligible.

We've got some awesome poets here on E2 and some not so awesome ones. Most strictly poetic works seem to float on the lower (though still positive) end of the reputation spectrum, the poetically 'good' ones coming in a little higher than the bad stuff.

What we need is a guideline - 'Don't Node Crap' doesn't help in this subjective of an environment and noders first dipping their feet into the murky waters surrounding poetry are likely to be discouraged from venturing any further. In an effort to prevent that, I give you the Top Five Six SEVEN Mistakes Made By Beginning Poets.

1. Plot. Have one.
   Know what you're trying to describe and include as much of it as you can. You're trying to evoke an image, here - make sure your audience has something to latch onto. This leads directly into:


2. Emotion ain't everything.
   There are only so many ways to say someone broke your heart. It's been done, and unless you've found a particularly new and vivid way of calling someone a homewrecker, don't.


3. Meter. Use it.
   ...or at least don't ignore it. Words need to flow from one into the other and there needs to be a swing to it - if you're throwing tons of hard syllables in there in oddly broken rhythms no one's going to bother. You don't want your readers straining - they should enjoy the process as much as the outcome and good metering is important to that. Oh, and also: if you're going to rhyme your lines, do it consistently - don't rhyme two lines and nothing else. And alliteration is a needle not a mallet - use it carefully. Strings of words beginning with B don't make poetry; it's just...cute.


4. Be concise.
   Don't say the same thing three ways, in a row, one to each line. Pick one. And while we're on the subject of format, keep your line widths nice and wide. Don't worry about the aesthetics of space until you're sure your words are bending the right way. If you think a poem flows better broken down into two to three word lines, try solidifying your meter - unless you know what you're doing such short lines come across as trite, abrupt and difficult to read.


5. EDIT.
   I can't emphasize this enough. Write, sleep on it and look again in the morning. Check yourself. Ask for opinions. Take the time to ensure your message is getting across without seeming like a blunt instrument - pick a theme and go with it and save your new ideas for a new poem. Stream of consciousness might be easier and seem more raw to you but it's blatantly obvious to the rest of us and we aren't quite so impressed. It's never (ok, rarely) that easy.


6. Ask for help.
   Everything is a community and we will do our best to help you with what you've got on paper if you ask - that's what your scratch pad is for. We also have a user group for all things poetic: see e2verse for shoulders perfect for leaning on and asking questions of.


7. And finally: Don't be that guy.
   Very few of us who write poetically do only that and that's mostly because a. we're talented, multifaceted individuals, b. our merit would suffer and c. we don't want to be that guy. Nobody likes that guy. You know, the guy who says 'if nobody gets my poetry it's far too sophisticated for them.' Guess what? If nobody gets your poetry you're doing something very wrong and need to change. Ask for advice from the poetic sorts here and listen to them. I guarantee they're only trying to make you a better writer and are NOT out to get you.

Keep in mind: rules are meant to be broken. Some of the best poetry here breaks most or all of these rules but you need to know what they are before you start toying with them and you need to break them for a reason.

Keep a cool head, and remember: some people just don't like poetry or don't feel it belongs here. Accept that (and the downvotes associated with that) and keep at it. You'll be fine. Don't forget to breathe.

Part of every noder’s calling here at E2, if they’re concerned about the quality of writeups on the site, is to be on the lookout for errors in writeups. Grammar and syntax errors, typos, content errors – we all make ‘em. For many people, myself included, it can be difficult to read a writeup that’s laced with such errors. They’re as jarring as a wrong note in a symphony, and can bring your train of thought to a sudden halt. Most of the time you skip over the error and read on, but wouldn’t it be nicer if the writeup were error-free?

Sometimes errors, especially common ones can elude an author, and it may require another pair of eyes to spot them. You, the helpful noder, benefit from this as well, because it never hurts to sharpen your proofreading skills.

For our part, we’ve been exhorted by The Powers That Be to gently point out these errors rather than just correct them on the fly – again, in the spirit of helping noders to perfect their writeups and turn the situation into a learning experience.

How You Can Help

Keep an eye out for potential errors in writeups. If you think you’ve found one, send a polite message to the author and suggest a correction.

Should you receive such a message, don’t get your knickers in a twist. Most likely the message was offered in the spirit of perfecting the database, and should be accepted as such.

Carry on, node well and often!

Let’s look at the record …

tweakin’ and tightenin’

• I, Robot – assisted noder with some typos and syntax.
• The rise and fall of Inger Lorre and the Nymphs – advised noder of some punctuation fixes.
• Lingustic and Cultural competence and Anita Roddick – assisted noder with some suggestions for tightening the syntax.
• Lyngby – assisted noder with typos and softlinks
• E2 HTML – advised noder that overuse of profanity detracted from the professionalism of the WU. Noder most cooperative, and was able to edit the piece to keep the flavour but not the language.
• Ender's Game – fixed some typos and grammar errors in the writeup (noder apparently fled).
• Jubileum Volume I – assisted noder with tightening up the language in the writeup.

prunin’

• ripping off porn sites – silliness superseded by later writeups.
• dcl – superseded by subsequent writeup.
• lifespan – superseded by subsequent writeup.
• alone – possible daylog material, but only with some formatting added.
• NCL – a one-liner with a typo and without punctuation. Noder advised to re-read the FAQ.
• manufacturing consent – at the noder’s request.
• nonce – one-liner, by fled noder, superseded by newer writeup.
• hot chocolate mix – superseded by newer writeup.
• April 27, 2004, IAWTP, tl;dr, leptokurtic, platykurtic – at the noder’s request.
• January 21, 2005 – at the noder’s request.

auditin’

• dgrnx

I also had a birthday this month. For the record, I’m 39. Again. That’s my story and I’m sticking to it.