The Internet and audience

So about this whole Frienditto thing.  (Ed. Note 2022: Frienditto was a service that could create a public archive of any LiveJournal post a user could see, thus effectively making public material the original poster had intended to be friends-only.  There was consternation.)

While I agree with the sentiment that it’s a bad idea to assume that anything on the Internet is private, there’s a separate issue which the integrity of friends-locking touches on: it’s really hard to judge one’s audience reliably on the net.

I think a substantial portion of online flamewars start from the equivalent of making a snarky joke about someone at a party, only to discover that they’re standing right behind you. It’s not necessarily that you wouldn’t say it to their face, but you might say it differently if you realized they were there. On the net, everyone is there. That takes some getting used to.

People phrase things based on the audience they’re addressing; it’s nigh-impossible to write without assuming something about your readers — their interests, their positions, their hot buttons. It can be frustrating when your words drift beyond the audience you intended, because they stop communicating effectively. And frankly, it’s a pain in the ass to write for the whole world all the time.

That’s why I find the idea of Frienditto a little troubling. I don’t talk about anything I consider private behind a lock, but I do sometimes rely on the known audience of my friends list to let down my hair a bit in matters of diction. I also avoid sensitive matters in email, but I’d still be ill-pleased to see my emails published Paris Hilton-style.

Originally published on LiveJournal

Suggestions for the Beginning and Intermediate Freelancer

Last week at DunDraCon, I was on the “How to Survive in the Gaming Industry” panel. One of the topics we discussed was the vital necessity of knowing your limits and pacing yourself, lest you get yourself into serious trouble. However, we weren’t able to offer any real guidelines for how to figure out what your limits are, which strikes me as a problem; in my life, I can think of several occasions when I learned what my limits were only when I broke. Trial and error is one way to do things, but it’s less than optimal.  So I’ve been looking at my records, and thinking about my experiences, and I’ve developed a few rules of thumb.

My first suggestion is that you should keep a journal of your work progress with daily wordcounts. This becomes important later. You’ll have to figure out how to deal with the issue of how to count revisions. I count revised wordcount at a 5:1 ratio, but different people have different tastes.

Most advice on how to get started in the industry recommends starting by writing magazine articles. The stated rationale is usually building your chops and developing a portfolio to present to future employers. I think magazine articles are equally important for developing a work routine and getting a sense of what amount of work you can fit into your life in a non-deadline situation; your work journal is useful for this purpose.

Once you’ve gotten a few articles accepted and gotten your feet under you, you’ll be ready to start soliciting contracted work. My rule of thumb for choosing contract projects is “Don’t stretch yourself by more than a factor of two”. This breaks down in a couple of different ways.

#1: Avoid taking on a project more than twice as long as anything you’ve done before. Write some 10,000-word adventures before taking on a 20,000-word chapter; write some chapters before taking on a 35,000-word supplement; and so on.

#1a: Under no circumstances take on a project that will double your total professional wordcount. I’ve done this. It was a bad idea.

#2: Avoid taking on a project (or multiple projects at once) that will require you to more than double your baseline daily writing speed. (Here, again, that work journal is useful.) Most people work faster when under deadline. As a rule, however, working much faster than normal for long leads to burnout and a slump in quality.

Originally published on LiveJournal

Book Review: Metropolis: Values in Conflict

I’ve just finished a book I picked up at the Menlo Park library sale a few months ago (any venue that sells books by the grocery bag is lethal to me). Metropolis is an urban studies reader from 1964. The first lesson I have gleaned from this is that I really need to break the habit of buying generations-old textbooks for a quarter; they’re interesting, but it’s not really a time-efficient way to learn things.

The second thing I notice is that urban theorists, from the earliest days of technocratic America up to the modern day, seem to dwell in a curiously non-geographic world. (I’m not just drawing from Metropolis on this; it just crystallized something that has niggled at me about various contemporary pieces I’ve read about reimagining cities.) I’ve seen any number of discussions of how to lay out cities, optimizing density and accessibility while preserving an appropriate amount of open and agricultural space, which completely elide the question of what happens if there’s a mountain or a river in the way of, say, your concentric rings scheme.

Perhaps I’m simply oversensitized to the question from living in a part of the world deeply at the mercy of its geography when it comes to urban development. I suppose that would explain why a lot of urban visionaries are Dutch; the Netherlands are pretty much flat, and heavily modified by human intervention already.

Originally published on LiveJournal

Reflecting on a log

I’ve been tinkering around with my dormant web site lately, and in the process I’ve been running some analyses on my server logs. From this, I have learned a few things.

1) There will probably never come a day that the 5 Geek Social Fallacies are not the most requested page I have. Not only is it the most requested page, the next five most requested pages are those available when you jump up one level in the site hierarchy from 5GSF.

2) I should not process my server logs when I am feeling a little twitchy and low. Long threads of people having fun with the 5 Fallacies will bring me only a little joy, and the pompous asshole who speculates at length about my own social deficits will stay with me.

3) I never realized this fully until my work started finding larger audiences, but people really don’t read what you write. They read some sort of virtual text constructed from your title, a few fragments of your text, and whatever preconceptions may be stimulated by them. It’s sort of amazing watching people rant about your failure to consider things you explicitly addressed.

4) Dude, Mike Mearls is hating on the Collective. You don’t get to do that if you weren’t there. (He doesn’t even have his facts right.)

Originally published on LiveJournal

Food Review: Trader Vic’s Palo Alto

Last night, one of Jen’s volleyball folks had a birthday bash at Trader Vic’s, and we attended. Considering the culinary experience, I have to say that the decor was nice.

To begin with, if one is going to slap a 20% automatic gratuity on a party of 20, one ought to assign said party more staff than one waiter and a busboy. The service was extremely slow and moderately inept; I was unimpressed.

We began with drinks. Jen ordered a Mai Tai ($8.50), figuring Trader Vic’s would be the place for a good Mai Tai; while the glass was large, it was mostly filled with ice and an lime half. According to the waiter, it was made with “lemon juice, lime juice, Mai Tai mix, and rum”. Maybe it’s just me, but I am dubious of destination drinks made with mixes. I had a glass of Firestone Riesling ($6); that’ll teach me to buy wine from a tire company.

Both of us ordered salad: Jen took the house salad, while I opted for the caesar. I can’t evaluate the house salad, because it never came. At least they didn’t charge us for it. The caesar ($8) had three serious flaws. First, the croutons were bland and stale. Second, they went a little nuts with the lettuce; they used the outer leaves of Romaine and tried unsuccessfully to cut them into bite-sized pieces; as a result, most of the salad was a mess of limp, perforated leaves. Finally, the dressing was watery; I can only imagine they didn’t drain the lettuce before dressing.

For the main course, I had the grilled king salmon ($25); Jen had the seafood taro nest ($23). The salmon itself was fine, if unexciting. It came with dry, leathery fingerling potatoes, and some grilled zucchini and eggplant that I couldn’t bring myself to eat. The whole dish sat on a pool of what was probably beurre blanc, though at the time it struck me more like bechamel. So not disastrous, but I’ve had a lot better food for twenty-five bucks. Jen’s seafood taro nest was a stir fry of overcooked marine life and canned vegetables. It looked pretty dismal. She picked out the seafood and called it a night. The taro nest also came with a side of rice, which I asked if I could take a bit of, as I wanted a palate cleanser after my buttered salmon. It takes some talent to screw up rice, but they managed it. I’ve had better rice in cafeterias.

So, when all was said and done, with the food, drinks, and aforementioned automatic gratuity, the bill was $96 for an evening of insipid 50s-style Polynesian fusion cuisine for two.

I suspect I won’t be going back.

Originally published on LiveJournal

The Styles of Creative Professionals: Auteurs and Impresarios

As I reflect on the many creative professionals I have known, I notice a range of stances on a key issue: how to steer one’s creative ship relative to the audience.

One one end of the spectrum, you have a group I’ll call the auteurs. They take their cues from their own hearts — they produce what seems important to them, and hope there’s an audience for it. This is an attitude close to the old adage “Write what you know”; it views the creative process as essentially personal, not to be guided by outside considerations.

On the other, what I’ll call the impresarios: they study their audience, and develop projects based on what they think the audience will find useful (which isn’t always the same thing as what the audience wants). This is an attitude close to the saying “Only a fool ever wrote but for money”; success is measured by audience reception, and using a different yardstick is tantamount to intellectual masturbation.

The interesting thing is that people on either side of the midpoint tend to make concessions to the other side in their execution, if not in concept; impresarios take pride in putting their personal spin on whatever the market demands, and auteurs are often very concerned with how to position their work in the marketplace.

Me, I’m a mild auteur; I try to work on things that I think people will like, but I get no kick from contemplating the zeitgeist of consumer buying habits.

Originally published on LiveJournal

Book Review: Altered Carbon

Amazon’s been telling me I need to read this book by Richard Morgan since it came out, and a few weeks ago I managed to hack down the stack to it.

There are two things I think are structurally interesting about this book. First, it’s a wonderful example of setting economy. There’s a single central piece of technology around which the setting revolves — the capacity to upload and download consciousness in and out of different bodies — and most of the book’s world proceeds from the ramifications of that technology.

The other intriguing bit is that I think Altered Carbon is an excellent instance of the decline of prognosticatory science fiction. There was a time when most science fiction could at least be construed as an attempt to predict a possible future. More and more, however, science fiction is allegorical rather than realistic. Altered Carbon, despite being set centuries into the future, has the feel of a noir detective story plus the aforementioned braintaping tech and more sophisticated weaponry. It’s a great story, and a fascinating meditation on a whole slew of social and ethical issues, but it’s not a plausible vision of the future.

Originally published on LiveJournal

Lessons of 2004: The “Your Mom” Rule

Only your mom cares how hard you tried.

There’s this thing I do, and only lately have I realized how deeply boneheaded it is. What happens is that someone will offer me a task or project that I want to take on, or reveal a new complication to a task I have already undertaken, and I will suspect that the task as currently defined may be beyond my ability to complete competently. (Not is, mind you; just may be.)

My reflexive response tends to be to sigh heavily (or its online equivalent) and say, “Well, that’s going to be really rough, but if that’s what you need, I’ll take a crack at it.” There is a part of me that then thinks that if problems arise, or things don’t work out, well, I put my cards on the table, and they know the score. I have done this a lot over the years.

This is totally dim. The fact that I usually get away with it because I’m good at deathmarching makes it no less asinine. No one wants you to do your best, they want you to do the job. They don’t want you to tell them no, but they really don’t want you to say yes and then fail. And they don’t care that you tried really hard; at best, the fact that you tried really hard and still failed just makes it awkward to yell at you.

Part of this is that I tend to assume that someone wouldn’t ask something of me if it weren’t a reasonable request. Thus, when someone asks me to do something beyond my limits, the very act of asking tends to make me think, “Well, if they think I can handle it, maybe I can. They know the nature of the task better than I do.” Thus overlooking that it is not other people’s job to gauge my limits, and ignoring the fact that people often make (intentionally or not) unreasonable requests.

I suspect my stupid tactic is also half intended, subconsciously, as a bargaining ploy to get the person offering the task to offer me more congenial terms. It doesn’t work.

I need not to do that anymore. When someone offers me a job that I think I may not be able to handle, I need to make a counteroffer rather than accepting while trying to hedge. Even when the person making the offer says they’ll owe me one if I take it on.  (Editor’s note 2021: When that person is an employee, who then moves on before you have a chance to cash that chit in, it is vexing.)  Above and beyond only counts when you succeed.

Originally published on LiveJournal

Book Review: The Etched City

I’d been wanting to start doing some book reviews as I work my way through the massive backlog of bibliage that bows my shelves, but I realize, after a couple tries, that I don’t really enjoy that. I hate doing synopses, and a number of the books I’ve read lately feel a bit beyond the level that my critical skills can fully encompass.

So instead I’m going to try talking about individual concepts that interest me in or around the books I’m reading.

First up is K.J. Bishop’s The Etched City, and asymmetry.

I’ll start by saying that this book is really frickin’ good. Anyone who can pull together flavors of Marquez, Mieville, and Squaresoft into a single book and make it work is doing something right. There’s depth and juice in the worldbuilding, there’s interesting philosophical freight and multifurcate narrative, and there’s a dude who forges his dead wife into a battleaxe. What more could you want?

When I took an initial stab at writing up a review, I had a paragraph about how I felt one of the book’s weaker points was its asymmetry. The book’s first fifty pages are set in a war-ravaged country (this bit read like a novelization of a console RPG in a very weird way), and then the protagonists go to the city of Ashamoil and pretty much stay there for the next three hundred-odd pages. The story is ostensibly a braided narrative about two estranged ex-revolutionaries and their tribulations in Ashamoil, but the vast majority of screen time goes to Gwynn, the brooding badass with the gun and the sword and the other gun.

The more I thought about it, though, the more I think that the asymmetry may be an effective narrative device. It’s unbalancing. You expect the narrative to shift from Gwynn back to Raule any minute now, or from Ashamoil back to the Copper Country or on to some other peregrination, and it consistently doesn’t. The net effect is that you lose your expectations, leaving everything possible. This may be essential to what Bishop is endeavoring.

The Etched City is basically magical realism set in a constructed world, which I’ve never seen before. Constructed-world fantasy tends to be naturalistic; the given circumstances may be different, but the world’s details proceed logically and predictably from those given circumstances. This is typically because it’s hard to make a story work when the audience lacks a touchstone to orient themselves by. In most magical realism, the familiarity of the real world is the axis mundi which makes the dream logic of the narrative comprehensible. Constructed-world magical realism lacks this anchor. I’m not sure how Bishop pulls it off, but my hypothesis is that she starts off with a fairly gritty, naturalistic base (the section in the Copper Country) and then uses distancing techniques like asymmetry to slowly ease the reader into the more dreamlike world of the later Ashamoil sections.

I have trouble describing this book in ways that don’t make it sound disastrous, but somehow it works. I recommend it highly.

Originally published on LiveJournal

Lessons of 2004: Delegation, and Bitches

I’ve been musing on the year that was — what I did, what I saw, what I heard about — and thinking about what is to be learned from the mighty shambles that was 2004. Today, I want to talk about what I learned about delegation, and about two-thirds of it boils down to this:

Nobody likes to delegate; everybody wants a bitch.

The difference, as I see it, is that delegation means assigning a task for which you are responsible to someone else whom you trust to get it right, while having a bitch means drafting someone to be an extra pair of hands for you because you can’t be everywhere at once. Almost inevitably, bitch work is of poor quality. There are a couple reasons for this.

First of all, nobody wants to be your bitch. If you have a bitch, either you’re paying them (whether in cash or less tangible forms of satisfaction) or they don’t realize they’re your bitch yet. It’s demeaning, and your bitch will resent you for it, and this will come through in their work.

Second, bitch work rarely shows initiative. This is because people tend to disrespect their bitches’ contributions, discarding (and occasionally excoriating) their labor if it’s not done exactly the way they would have done it. Over time, a bitch recognizes this pattern and sticks to doing exactly what they’re told, checking back for further instruction whenever there is ambiguity.

I cannot count the number of people I’ve seen bewailing the low morale, high turnover, and poor performance of their organizations, never realizing that their problems are a direct result of people waking up to the fact that they had been transformed from subordinates to bitches. And yet, people still want bitches.

Part of this is that you have to trust someone’s competence to successfully delegate to them, and competence is not falling off the trees in this world of ours. But the big sticking point, I think, is that at its heart, in order to really delegate, you have to be able to look at a project you’re responsible for, and say, “I think that’s the wrong decision. But it’s your decision to make.”

Delegation can’t just be “I trust you when I’m too busy to tell you what to do”. You have to trust your delegatee *all* the time, and you have to back their plays. Every time you override them — especially when you’re overriding something they’ve done in public — you’re saying, “Nice try, but we’ll do this my way, bitch.” And the bitch spiral takes another step.

Occasionally, that may be necessary, if something really huge is at stake. But I’ve seen far too many supervisors override their subordinates every time they disagreed, and every one of them had terrible morale and occasional revolts from the ranks. It’s not worth it to screw up your organization over minor points.

Originally published on LiveJournal