Banner: Shi - Available @ DriveThruComics.com

Monday, May 31, 2010

On Reviews

If you've ever read one of my comic book reviews, you probably quit reading it halfway through; I freely admit, I write long, in-depth, sometimes sprawling reviews. It's a learning process, and I get a little better with each one, but every review is different, so I haven't created a template for them, nor any standard procedure, etc. Still, if you have never read one of my comic book reviews entirely, then you aren't getting the most out of what I write, because comic books are what I do.

I have some experience in everything I critique, but I literally know comic books. Strangely, even though I played music semi-professionally
until just about five years ago (meaning I made several demos/worked with others on their demos, and played many live shows, but I never made enough to join any unions or professional groups, etc.), I would say I know more about comics than I do music. For whatever reason, I just have a... connection to comic books and sequential art that is stronger than the connection I have to other media and mediums (music, TV, movies, et.al.). Like I say, I don't know if it's a "calling", but I think there's something to that - it may well be - and I definitely feel that pull.

So, by reading my comic book reviews, you truly get a better handle on whom I am - the way I perceive things (above and beyond comic books, though they are the focus), my acumen, my other pursuits, and so on. But, again, I know they're long, tedious, and - unless you're truly an uber-geek like me - probably kinda boring.

So I'm starting to do some Rundown-style reviews: Concise and to-the-point, with no real direction for the creators. These reviews have only the reader in mind, and are written from that POV: Will the average reader like this? Will the not-so-average reader like this more and why? Would I suggest subscribing or is this the only issue I'll read? And so on.

Also, if you're wondering why I do a lot of these "agenda" posts - why I spend time telling you what I plan on doing, instead of just doing it - it's because I rarely ever get to these things when I say I will, but usually spend a whole lot of time working on them (which you can't see). I go back and forth in the same direction: I want things to be as close to perfect as possible, but when it takes too long, I settle for posting what I have and promising myself I'll fix it later. Either way, I'm never satisfied.

It just takes a lot longer than it would appear to take, for all sorts of reasons, and I'd rather you had an idea of what I am working on/toward than think I abandoned the project or whatever. It's just to keep in-touch, basically. Because knowing is half the battle.

© C Harris Lynn, 2010

No comments: