Category: journal

And for your reading pleasure…

- 0 comments

If you want something that looks like a book, Angry Robot has a sample of Servant of the Underworld to download, which contains the first chapter. Available in Mobipocket, EPUB or PDF.

Or you can also read the first three chapters online at My Favourite Books (they were cut into five parts to make them more manageable, hence the number of links).

In the silence of the shrine, I bowed to the corpse on the altar: a minor member of the Imperial Family, who had died in a boating accident on Lake Texcoco. My priests had bandaged the gaping wound on his forehead and smoothed the wrinkled skin as best as they could; they had dressed him with scraps of many-coloured cotton and threaded a jade bead through his lips – preparing him for the long journey ahead. As High Priest for the Dead, it was now my responsibility to ease his passage into Mictlan, the underworld.

I slashed my earlobes and drew thorns through the wounds, collecting the dripping blood in a bowl, and started a litany for the Dead.

Books read

- 0 comments

  • The Night Watch, by Sergei Lukyanenko: part of the book swag my sister gave me for my birthday (belatedly, since she isn’t in Paris currently. Russia is underpinned by another world, that of the Twilight, and its children, the Others. Wizards, sorceresses, vampires and were-tigers stalk the streets of Moscow, divided into two sides, the Dark and the Light. Those sides once fought each other, but have now signed a truce in the interest of survival. The truce preserves neutrality: every act of magic by an agent of the Dark gives an agent of the Light the right to perfom an act of similar intensity. The Night Watch is the Light entity which watches over the Dark to make sure that it doesn’t break the rules, and the Day Watch, made up of Dark field agents, does the reverse.
    Anton is an agent of the Night Watch, a minor magician recently assigned to field work in order to catch rogue vampires. But when he meets Egor, a young, unaligned Other on the verge of change, and Sveltana, a young woman under a powerful curse, he has no idea his life is about to change…
    The Night Watch is made up of three semi-independent stories, each focusing on Anton, his relationship with his powerful boss, Boris Ignatievich, and his growing awareness of how both sides manipulate their own pawns for their gain. It’s urban fantasy, Russian-style, but very refreshing both in its setting and in its attitude: Anton isn’t a kickass hero (and, indeed, his kindness and human judgments end up much more useful than his magical abilities), just a man trying to make sense of what is around him and gradually coming to question his role in the organisation. Though there are clear sides, you can’t really say that one is better than the other, since they both have a tendency for ruthlessness. Both sides will cooperate to chase rogues, which makes for interesting scenes when they’re all bickering together. The characters are great, each pretty well-drawn, from Anton to were-tigress Tiger Cub, to young mage Yulia. Pretty strongly recommended. I’m definitely going to check out the other books in the series.
  • All the Windwracked Stars by Elizabeth Bear. Thousands of years ago, Ragnarok occurred, leaving only three survivors: Muire, the last of the waelcyrge (Valkyries), the war-steed Kasimir, reborn into a thing of metal and hydraulics, and the Grey Wolf, the betrayer, the one who swallowed the sun. Now the city of Eiledon is all that is left of the human world, dying more slowly than the rest of the poisoned land. But the Grey Wolf has come hunting again, to bring about the second end of the world…
    An awesome mix of postapocalyptic SF, Norse myths and steampunk. I love Bear’s writing style, and this book did not disappoint. It also had a very cool plot and a cast of interesting, flawed characters I rooted for easily (the Grey Wolf is made of awesome, but Bear has always been good at doing mysterious and dangerous, like Whiskey in Blood and Iron). Again, I’m looking forward to picking up the sequels.

What Stargate isn’t telling you about science…

- 0 comments

aka Common Myths about Science That Bug The Hell Out Of Me:

A scientist develops a great new invention in his lab on his own.
It used to be possible, but the days of great geniuses and polymaths like Newton and Descartes are past. Nowadays, it needs a team to develop anything. Most scientists work in teams, and so do most engineers. Someone might still have this amazing idea and make a breakthrough, but a complete prototype on his own? Not possible, as this involves several different areas of competence (see the point just below, too). Also, having people with similar competences to check what you do is usually a Good Idea, if only to make sure you’re not making any mistakes.
Just for the record, a simple prototype for a demonstration, built from scratch, should require at least a dozen people to handle the various aspects of the job. And that’s a bare minimum–like your student association building a robot for a competition. A company would have far, far more people designing the thing.

On a related subject: the scientist who knows everything about every field. He/she was trained in aeronautics, but is also a dab hand at biology, and chemistry too, when needed (I’m looking at you, Sam Carter).
Again, the days of polymaths is past. It’s possible to have vague knowledge of a lot of subjects, but to be able to make deep and sophisticated calculations in various divergent fields… You can’t be proficient in more than 2-3 connected areas (the BF had a wider education than most, and is still only proficient in physics and somewhat knowledgeable in computer science. He sucks in biology or mechanics. I’m good at computer science, reasonable in applied maths electronics, and suck at everything else).

The scientist(s) who has this great and amazing idea, and builds a prototype in a few days or a few weeks. Frequent bonus: the prototype survives field use and turns out to be perfectly operational.
Here’s the deal: developing anything is a long and drawn-out process, and field conditions are not a joke (sand that gets everywhere, weird temperatures… Your average materials are often going to take it badly). Building a prototype, even as part of a team, is more likely to need a year than a few weeks. And I’ll eat my hat if that hastily-conceived prototype is actually up to field conditions unless God takes a personal hand in the matter…

The aforementioned prototype is taken for an experiment, and no one keeps any backup anywhere. When it’s destroyed, people complain that they won’t be able to rebuild it.
Er, yes, OK. Sometimes it has happened. But this is BAD planning. Most companies/army research centres have backups and document every step of the prototype production. Not being able to rebuild it at all smacks of incompetence.

The scientist is setting up an experiment in field conditions, make modifications to the setup, and takes ages to relaunch the experiment (this usually happens when the bad guys are firing on the scientist’s position)
If you have, say, an electrical circuit and you’ve just rewired it with a few components, you don’t actually need to spend ages typing on the computer to make it work. It should be the equivalent of flicking a switch, and if you need more than a few seconds, I’ll start wondering about your actual skillset…

On a related subject, the scientist sets up an experiment in field conditions, and appears to have no idea what they’re going to do when the experiment fails.
Experiments have a protocol. They are actually prepared. You just don’t show up with your new shiny equipment and start fiddling with it in the thick of the action. Otherwise, the likelihood is that it won’t work, or worse, that you’ll fry something. And if you’re a good scientist/engineer, you’ve considered the fact that it might not work and have thought of one if not several backup solutions. Fiddling is all well and good, but the sad fact is that it’s seldom effective.

The scientist solves what looks like an amazingly complicated problem to the profane, but is actually quite a basic problem.
This is obviously a case of writerly misdirection and/or lack of research, but it’s really annoying when you happen to know a little about the subject matter (and nothing kills my trust in an SF show faster than this). The most recent example of this was Sam Carter bragging about writing an algorithm that searched through a database for words composed of a particular set of 18 symbols. This is a trivial problem (all the more so if the database is sorted, which they’ll have done if they have any brains).
A bonus case of this is when people start misusing scientific concepts. If I hear “logarithmic decrease” again, I’ll scream (a logarithm is a function that actually increases, and it’s also the one that has the slowest possible growth, so I’m not quite sure what a logarithmic decrease is supposed to be except obfuscation).

See, this is why I can’t watch most shows that are all about the cool science. I need characters to distract me 🙂

What about you? Any common misconceptions that drive you up the wall when you watch movies/series?

Linkage, progress

- 0 comments

Silvia Moreno-Garcia interviews me at Innsmouth Free Press on Servant, writing in other cultures and my pet history peeves.

The Shine competition has gone live: basically, guess the next sentence AND guess the story. See if you can spot the collab I did with Gareth L. Powell 🙂

And chapter 2 of Servant of the Underworld is now live at My Favourite Books.

Misc. midweek update

- 0 comments

Harbinger has stalled, mainly because I wrote myself into a corner and now need to get out of it. The solution I had in mind turned out to involve something I expressely mentioned as impossible in Servant, so it’s back to the writing board…

I have found a new toy: a Starbucks thermos mug (brought back from Moscow by my father), which is suprisingly handy to have–you never know when someone is going to interrupt you, and the water at work is lukewarm at best. Having the mug helps to get extra minutes of hot tea, which is cool.

This will probably be the last post before the blog goes dark, as I’m going to Dublin to visit my sister. Internet access will be around, but it’s likely I won’t be using much of it.

Some linkage:
-Fellow SFnovelist Jackie Kessler continues to chronicle the Harlequin Horizons debacle. Very interesting posts.
-Article over at Nebula Awards website on “International SF” and Problems of Identity
-David Antony Durham compares covers, which I always find a terribly fascinating exercise.
-Strange Horizons has an article from Nicholas Seeley, in which various Apex World Book of SF contributors discuss SF and language.

Sale: “The Church of Accelerated Redemption” to Shine Anthology

- 0 comments

I’ve been sitting on this one for a loooong while, but I’ve finally been allowed to make it public: the collaboration I wrote with Gareth L. Powell, “The Church of Accelerated Redemption”, has sold to Jetse de Vries’ Shine Anthology, due out 2010 from Solaris.

This one was one heck of a hard one. Many many thanks to Marshall Payne and the BF for reading it at least two or three times, and to Jetse for having such awesome rewrite suggestions. And to Gareth for being such fun to work with.

No snippet, as Jetse has a competition planned. Watch the Shine anthology blog on Monday, 30th November for more details 🙂

Monday monday

- 0 comments

Erk. Tonight’s activity consisted of transcribing my handwritten notes on the proofs into a big email to AR towers. My fingers, they hurt…

Tonight’s secondary activity is trying to transfer a homemade video from a Mac to a PC, and getting a big headache (the video is a Quicktime movie file, and I want it to be readable in Windows Media Player). So far, not so good. Will poke around some more.

And, while I was out there researching my mythology, I found this awesome resource on the Aztecs. Theoretically, it’s educational activities for kids, but it’s amazingly (and obsessively) detailed. My new stop for nifty details.

Lessons learnt today…

- 0 comments

…about the writing of sequels.

When naming a minor character in a book, don’t give him a long and complicated name on the assumption we’ll never see him again anyway.

Because, you know, he might turn out to be a major player in the sequel and thefore need his name mentioned on a regular basis…

From now on, the only people getting long and complicated names are those earmarked for death.

(yes, I know. It’s occurred to me the dead can come back unexpectedly, but we’ll cross that bridge when it presents itself)