For yet another explanation of why this might matter, here’s Deborah Copaken Kogan talking about her experiences as a female writer. And for those confused about why talking about what a woman does is more important than what she looks, here’s this.
I’ve blogged elsewhere about the Night Shade Books convulsions. I wait to see what happens, as do a number of people with a lot more at stake.
Want access to a lively community of writers and readers, free writing classes, co-working sessions, special speakers, weekly writing games, random pictures and MORE for as little as $2? Check out Cat’s Patreon campaign.
"(On the writing F&SF workshop) Wanted to crow and say thanks: the first story I wrote after taking your class was my very first sale. Coincidence? nah….thanks so much."
So for Patreon, another Serendib story, and a return to The Dark and Tericatus. Here’s some from yesterday:
After she’d hopped the wall, it had been easy enough to defeat the bloodsucking ivy and the centipede hounds contained in the first set of walls. After that, it got more interesting.
The Dark rarely stooped to thievery nowadays but, the truth be told, it was how she had started her professional life, long ago in a city whose name she had deliberately forgotten. She had been a child born to both privilege and indifference. At fifteen, she had left the school where her parents had stored her in order to make a living from burglarizing the friends of those parents, at least those whose estates and townhouses she’d had occasion to reconnoiter in her adolescent years.
She had done quite well by this, well enough that she spread the largesse to those less comfortable, and in doing so, became known as “The Dark Angel.” When, sixteen months later, the unnamed order of assassins that had noted her exploits came to recruit her, they demanded she remained herself, which she did by truncating the former name to the form she had gone by several decades now.
She had kept that knowledge to herself as, over the course of those decades, she’d met any number of unusual characters, including her spouse for two of those decades, Tericatus the alchemist-mage, Chig the Rat God, and quite a few fellow assassins who failed to live up to the high standards she held when it came to both of her professions.
She had retired from assassinations ““ aside from the occasional hobbyist or wager-related killing ““ some time ago, but now to thievery not so much for entertainment but also because she was impelled by the yearly conundrum of a suitable anniversary present for a man who could, literally, conjure almost anything his heart could imagine.
The next wall was made of fricklebrick, which sounds amusing but involves a number of razor-sharp edges shifting frequently and somewhat randomly in their orientation.
As she paused, letting the gloves covering her hands sense the vibrations of the bricks and adjust themselves to countershift accordingly in a gentle grinding born of magic and machinery, she thought about his imagination and ““ not the for the first time ““ contemalted her luck in a mate who had long ago grown blasé with such things and preferred inner qualities of fierceness and determined loyalty.
She wriggled upwards, her features smeared with coalblack to match the midnight shadows around her. This year, she planned to snare something lovely that could not be bought ““ her philosophy of presents was that such things were better assembled by than by coin.This garden, located on one of the great terraces built along the mountain slope bordering the city to the north, belonged to a recent arrival to the city, a merchant/scientist whose name the Dark kept having tremendous difficulty remembering. This spoke of certain magics laid upon the name to avoid notice, and that was intriguing, and more intriguing yet were the rumors of the contents of the innermost garden, center of three sets of walls, which held a worthy gift.
This weekend I’m teaching Creating An Online Presence for Writers and the Flash Fiction Workshop – there’s still a few slots open if you’re interested!
#sfwapro
Enjoy this sample of Cat’s writing and want more of it on a weekly basis, along with insights into process, recipes, photos of Taco Cat, chances to ask Cat (or Taco) questions, discounts on and news of new classes, and more? Support her on Patreon..
...
One of the sad truths of the mud world is that there are never enough coders. Builders aplenty, brimming with fresh idealism and plans for entire zones, appear (and sometimes disappear) at the drop of a hat. But coders are the unicorns of the mudding world, seldom glimpsed and ardently pursued. We are lucky enough to have three dedicated coders on Armageddon MUD: Morgenes, Tenebrius and Tiernan, as well as a few other staff members willing and able to wade through the bugs file and tinker with things upon occasion. How, then, does an administrator keep these rare beasts happy? The following four steps may help.
1) Communicate: When asking for new code, try to let the coders know exactly what is desired. For example, instead of ‘Let’s make archery more complicated,” a staff member might propose “Let’s put a range on archery, so the farther away the target is, the harder it is to shoot it.” A full description of the the idea, perhaps including examples, such as fake logs showing what the idea will look like when being used, helps make sure the originator of the idea and the coder are on the same track as far as things like syntax and usage are concerned.The same holds true for bugs. Describing how it’s supposed to work as well to how it’s working right now helps clarify ideas. Coders want to know if the bug is REALLY a bug, or something being reported because it doesn’t work as the reporter feels it should.
With bugs, give the coders as much information as possible, including how to reproduce the bug. Examples by way of logs are great, and if they include some form of error message (or message that they’re getting that shows it’s an error), it often allows the coder to track down what section of the code needs to be worked on.
Make sure people aren’t bumping into each other. On Armageddon, we’ve got a coder’s board, where people post changes as they make them. This alerts fellow team members to what they’re doing and is also helpful if unexpected bugs crop up, enabling people to track exactly what got changed and when. Two people should not be working on the same idea at once unless they know it, and can divvy up the work accordingly.
2) Have a purpose: Will it get used? Is it something players are asking for? This one is a matter of ego, but we’re all human and we all do have egos. Seeing their work getting used, regularly and as envisioned, is a reward beyond any thanks or congratulations other staff members can give a coder. Track player requests, through entries in the bugs/ideas/typos files as well as emails to the account and posts on the general discussion board in order to convince a coder that the players want, and will use, something.
Generally, with new ideas figure out how they are moving towards some goal. A piece of code like a new skill is going to sound more interesting if it fits into some overall purpose, such as a master plan of non-combat related skills for the economy than it would if it is just a random idea. You are also going to end up getting more out of the idea if it is part of a greater whole.
Make it innovative. Some coders like to be trail breakers, to feel that they’re not just playing catch-up with another mud, but are creating ideas and concepts new to the mud community. Some ideas get requested to ‘balance’ things out between groups: guilds, or races, or mount speed. When a coder starts to feel like the code they’re doing that day only works to nullify a change made last week, then they’re going to start wondering what they will be asked to implement tomorrow.
3) Share the work: Do as much of the grunt work as you can for the coders, including helping thoroughly test, providing help files and documentation, and fleshing things out. In testing, give coders information about what is not working and how to recreate the result. Be precise about what needs to be changed: not ‘the plague of locusts spell needs to do more damage’, but ‘it needs to do about twice the damage it is now.’ When something requires a new help file or modification of an existing help file, do not expect the coder to do it, but supply it yourself. If it is something that requires building, provide the items. Teamwork of this kind, when it is working well, is terrific, and will often produce amazingly cool results.
4) Appreciate: Good coders can never be praised sufficiently. We try to make sure that players know who is responsible for new and interesting changes, by posting information about them in the news as well as in our weekly update, which is a mailing our players can subscribe to, which provides information about changes, staff and world news, upcoming recommended playing times, etc. When players write in with compliments or feedback on a code change, make sure that the note gets passed along to the person , as well as that the coder knows how cool or slick you think the ideas they have implemented are as well.
There is a tendency sometimes to regard coders as resources that spit out code at request. But the fact of the matter is that treating coders in that way will frustrate both sides, leading coders to become discouraged and unmotivated to implement new ideas and builders to feel that their coding needs are not being met. These four points may help avoid such frustration.
This article originally appeared in the April 2001 issue of Imaginary Realities.
© 2002 Cat Rambo. All rights reserved.
...
