One of my daily reads is Sarah Hoyt’s blog and recently I’ve been going through some of her older entries (I’m looking for a post where she was talking about the review submission process…don’t ask) and I stumbled over several mentions of how getting us writer-ly types to organize and do anything in a uniform fashion is kind of like herding cats. Especially those of us of what she calls the Odd bent (and what I call the “awesomesauce” bent because, yay, more fellow NTs!) I’ve noticed this myself — especially back when I was submitting to agents and traditional publishers before I realized that was a chump’s game and decided to go indie. Each agent or agent house and each publisher has their own guidelines for receiving query letters and manuscripts and none of them are the same.
Considering the uniformity of the end product (mass-market paperbacks have very specific cover and print-set specifications) and the general consistency of editing software and screen-readers, you’d think that there would be some consistency. But you’d be wrong.
The only other area where I’ve encountered such a dizzying array of sheer anarchy is…the tech world. I still keep a foot in that realm (because it’s fun) and anyone who’s actually delved into code very far knows what I mean when I say that reading someone’s code can tell you everything you need to know about them. If it’s not human-readable, you know that they’re using a graphical interface to drag’n’drop elements into place and that they don’t actually know what they’re doing. They might have a cursory understanding but they don’t grasp the fundamentals and the principles. Or, they’re not a coder (and they’re not pretending to be — I had this happen a lot in my professional life) and you get the fun job of digging through a single-line (that is actually several thousand lines) of nested HTML menu items to find the one that isn’t closed properly so you can make the document strict XML compliant.
If the code has function names that are the same as variables, you know you’re deal with someone who has some experience but is still new to the game. Their comments and documentation will tend to be hit-or-miss but at least it will exist. If the code has function names that are purposeful and unique, you know that the commentary and documentation will be fairly good (or they will have outsourced it to someone who will be better at it, you hope) or it will be non-existent. If the function names are vindictive and the documentation has you going in circles, you know that you’re probably better off removing everything and rebuilding from scratch because someone high up pissed this person off and you’re dealing with a BOFH type who has decided to extract a pound (or ton) of flesh. In this case, there’s only one thing to do:
The issue is, some techies are going to be die-hard Perl scripters and everything is going to be in that. Others will prefer Python. Some never moved past C++. You’ve got your K-shell users, C-shell users, Z-shell folks, and then a quick shout-out to my peeps out there in Bourne-Again land (BASH FOREVAH!). There’s the Xwindows folks who are all about some KDE while others are hung up with their Gnomes and the rest of us are wondering why in Torvalds’ name you’re running Xwindows on a server — it’s not secure. People will cling to their text-editors and bitter fights will break out over vi versus emacs versus pico versus nano at which point G.K. boots to Windows (hey, if you’re going to run a desktop, run a freaking desktop) and opens up Scrivener. PHP devs will say you can do everything with PHP and seasoned HTML coders will snort and think about all the times they had to implement HTML/CSS/JS fixes to deal with a PHPlib error. SQL DBAs will laugh at all of them while they work on their next round of fiendishly difficult certifications.
As you can see, though…techies and writers — none of us can agree on how things should be. Oh, we all have our opinions on how they should be. Techies will even form consortiums, conventions, conglomerations, conferences, and write out long RFCs about How Things Should Be. Enough others will agree and we’ll wind up with this situation:
Which, come to think of it, is probably what happened in the publishing world.
Now, do I think that writers are going to eventually get together and decide on a uniform submission process? Hell no! Do I think publishers will eventually decide on one? Nope. What will probably keep happening is what’s been happening. It’s just interesting to see that two groups of people the average Joe Public considers diametric opposites (writers and techies) are actually very much alike.
And it’s cool to be both of them at once, yo.
— G.K.
