Count_Zero

I thought this radio play was fairly enjoyable, though having someone other as David Suchet playing Poirot caused a bit of cognitive dissonance for me. The narrative resolution wasn't as good as I'd like - thought that's perhaps a problem of the nature of radio plays as a medium - you have to tell everything, which means omissions are an even bigger problem then they'd be normally.

This book is so desperate to show you how 70s it is, that it can't stop ramming it down your throat. Between a bunch of poorly executed references to various 70s prog rock
bands, and shoehorned in drug use (of hallucinogens, naturally), the book loses any sense of being a 3rd Doctor story.

I definitely enjoyed the novelization of the film more than the film itself. I still consider McGann my favorite Doctor though, and I really hope that he shows up in a fashion other than stock footage for the 50th Anniversary.

Interesting developments in this installment.

It's kind of weird listening to this book as an audiobook. Going from the sort of “Literary agent” structure that the Lord of the Rings was born from (J.R.R. Tolkien translating a book that he found in some archive somewhere), the Silmarillion feels like it should be structured in the form of something like Beowulf or the Odyssey - a legend originally told orally, transcribed into a more written form. Thus, this should be something that would be perfect for an audiobook.

However, rather than using any of the meters or rhyming verses that those earlier works (which clearly inspired Tolkien) used, instead the book is structured in a form that's probably closer to the Bible, particularly the King James version, with a mix of events told in the abstract, combined with individual moments told with more specific details, in a very floral style.

Having the book read as an audiobook does make it less dry, and easier to get through. However, there are moments where, as a reader, I have to basically stop the book after the book summarizes a big moment (such as an epic battle between two armies), and picture that battle in my mind's eye, before continuing with the book, whereas in the more specific moments, the story in the narration plays out at about the same pace that it does in my imagination.

I am glad I've finally read the Silmarillion, but it's not something I'm going to re-read again for a while, and even then, I'll probably stick to specific passages.

A fun little stand alone Elric story. Some of the more fun stories with the character have been those that carry him to other worlds and other planes. A story that carries him into dreams is particularly interesting and inventive. This might be my favorite Elric story.

Virgin Books' Doctor Who: New Adventures series was, back in the day, meant to provide fans of Doctor Who the thing they wanted after the show was put on indefinite hiatus after the serial Survival. Time's Crucible is the 6th book in the series, part of a pair of thematically linked stories under the heading of “Cat's Cradle”.

The story involves the TARDIS basically having a temporal collision with an early prototype Time Ship from Gallifrey from just before the rise of Rassilon. This gets into material that doctors from Tom Baker on had explored directly, but which Sylvester McCoy's doctor had only explored obliquely – the history of the Time Lords.

Conceptually, telling the story as a novel lets you do some stuff that would be really hard to do in live-action television. The mixed up TARDIS interior is described with a weird surrealistic and claustrophobic interior that you could do with comics or animation (as was demonstrated by the anime Id:Invaded), but would be very difficult to do with a TV budget for the time (even modern Doctor Who might stumble a bit with that).

Additionally, the book puts Ace at the forefront in some interesting ways – she's always been an active character in Doctor Who stories, but here for 3/4th of the book she's the driving force of the resolution of the plot.

The book's not without some real problems though. The elements of the plot with time folding in on itself and alternative versions of characters from different places in their timelines running into each other works very awkwardly in prose. By the end of the book I've completely lost track of some of these characters timelines. This, on the other hand, is something that a visual presentation would work strongly with – through showing the same character in different physical states to indicate where they are in their life and their timeline (or timelines).

Additionally, the opening portions of this book are something of a slog – when the book gets going, it really gets going. It's just that it takes almost a quarter of the book to get there.

(This book review originally appeared on my blog)

Frankly, this is Tom Clancy's magnum opus. If you're going to read only one Clancy novel, read this one.

Very good discussion of the life of Vlad Tepes, Vampire myths, and the Dracula story.

Interesting book. The idea of having the detective be a sports agent was something I hadn't encountered before. However, the whole thing of Bolitar's gay ninja business partner seemed a bit silly. The ending was okay, and reminded me a little bit of the solution to “The Mysterious Affair at Styles” in both good and bad ways.

I've found the best Urban Fantasy novels are also great detective novels, except instead of ballistics, DNA testing, and the other tools of the science detectives trade that Sherlock Holmes & the like bust out, there's magic. The Peter Grant novels succeed at this fantastically. Aaronovitch creates excellent characters and riveting mysteries that really pull you in.

A fascinating book about the Mafia. Most books on organized crime either focus on the modern or semi-modern period, or on Prohibition and events related to that. This book is the first I've read that goes further back then that, all the way to the turn of the century. It's very well researched and well written, and does a good job of avoiding both mafia-worship and passionate hatred of the organization.

I enjoyed this volume well enough, though with the structure and events of the stories, I think I'll enjoy the anime more.

Another fun installment of the series. I do empathize with the main characters' response to going to the beach - I generally tend to do the same thing. Then again - I live in Oregon, so generally at the beach it's too cold to swim. Also, if there are sea lions in the water, there are also sharks.

Well, this was certainly enjoyable, but not without its faults. When your society is almost more sexist than Westeros, you've got some problems. As it is, I do like how some of the characters are written, particularly the Master Smith towards the end of the book (who acts exactly like an engineer).

I also have a bit of a gripe with how quickly the Dragon Riders manage to cope with four-dimensional thinking. It seems slightly absurd.

With 2010, Arthur C. Clarke's ability to write interesting, believable, and likable characters has improved dramatically, particularly compared to the cardboard cutouts from Rendezvous with Rama, and the similarly bland characters (with the exception of HAL) from 2001. The book also does a great job of answering the remaining questions from the novelization of 2001.

As far as the book to the movie goes, it's something of a 50/50 split. The book is better at providing the answers then the movie is, and there are some stupid decisions that the characters make in the film which aren't made in the book (like sending Max in a manned pod out to the Monolith, instead of using an unmanned pod operated by remote). Also, the book manages to be semi-prescient by having giving China a space program that would have been somewhat unimaginable when the first film came out. However, the movie manages to be more reasonable by increasing the danger to the Leonov when SpoilerJupiter becomes a star.

All in all, 2010 is one of my favorite Arthur C. Clarke novels, and is definitely a worthy companion to 2001.

The book definitely brings the series to a satisfying conclusion, but the denouement runs a little long (though, to be fair, getting the denouement the right length is something that lots of writers have problems with). Probably the bigger problem with the book's end is that, approaching the conclusion, it screams, “The writer got the publisher to agree to another trilogy, so he's going to lay some plot hooks for the next one!”

This is aggravated by the fact that I'm reading the book's first printing, and right after th end of the story we get this little bombshell.

Here ends The Sapphire Rose, thus concluding the tale of The Elenium – but not the adventures of Sparhawk and his companions. Watch for further danger and magic in The Tamuli, a new series from David Eddings, forthcoming from Del Rey Books.

The Marcus Didus Falco series really should be an HBO TV series. It's a highly engrossing mystery series, with incredibly interesting characters, and Lindsey Davis makes the Roman Empire really come alive. This book, the second in the series, is really no exception. Davis makes Pompeii and Herculanium (where the majority of the action takes place) feel like living, breathing cities.If I had one complaint about the book, it has to do with Spoilerthe discovery that Pertinax is still alive. There was no evidence in advance to show he was still alive before then. To be fair, it's a surprise to Falco as well, but it could have been handled a little better, I think.Falco, as a character, is probably one of the better realized examples of a detective who is too pig-headed for their own good. While some of the classic hard-boiled PIs of the 30s have this trait, we rarely see enough of their lives and friends outside of the job to see how this changes that side of things. Falco has family and friends with families, so we get a better look at how his stubbornness effects his life outside of the job.As a fan of historical mysteries (like the Cadfael novels by [a:Ellis Peters 4046 Ellis Peters http://d202m5krfqbpi5.cloudfront.net/authors/1242605103p2/4046.jpg], I really enjoyed this book, and I'm probably going to read the rest of the books in the series, at least until it gets bad.

I'd definitely say the second installment of the series is better than the first, and definitely does a better job of fleshing out the characters. However, I'd rather that establishing the characters of the leads be done in the first book, so they can undergo growth and development in later books - like this one.

Oh, and the little Carmilla sequence fit in nicely with October.

About 6 years ago, a sort of scandal rocked the gaming industry related to a blog post by a woman known as “EASpouse”. The blog post criticized EA's labor practices at the time, which required employees to work massive amounts of unpaid overtime, as they were salaried employees. By massive, I mean about 12-16 hour days, 6 days a week, regularly. This was a big deal among gamers, because very few of us had ever had the opportunity to peek behind the curtain like this. It was likely that most of us viewed game development with a variation of the way that Roald Dahl as a child imagined the inside of the Cadbury Chocolate Factory near the boarding school he attended (which later led to Charlie & the Chocolate Factory).

The Soul of a New Machine, by Tracy Kidder shows that such working conditions are nothing new. The book follows the development process of Data General's micro-computer (sort of like a rack mounted server, except it's the size of the whole unit, but essentially only being one of the server nodes), that would be a successor to their Eclipse line of microcomputers, code named the Eagle, and later released as the MV/8000. The book goes into both the personal and technical aspects of the development process, profiling the various men (and a few women) involved in the project, and giving a description of the technical aspects of the process for the layman.

While the technical bits (pardon the pun), are enjoyable, the book's strength, and where it spends most of its time, is in profiles of the people. The book paints a bleak picture of the inner workings of Data General. The working conditions at Data General, particularly on this project, are brutal. Much as with EA Spouse, employees are salaried, with no overtime pay, and work 12-16 hour days, 6 days a week. As the project goes on, project leads and younger employees are worn down. Often, employees at Data General observe that the company brings in a lot of new fresh recruits, and few stay at the company after they turn 30. Many of these new recruits drop out for various reasons, and often employees discuss the company's sweat-shop like working conditions. As the project moves into the heat of summer, the air conditioning breaks, turning their windowless basement office into a sweltering oven, which they can't even leave the door open for, for security reasons. Only after the employees strike do they fix the air conditioning.

By the end of the book, several of the project leads, themselves burned out, leave the company, and while some of the employees on the Eagle team stay on, many more have left.

Tracy Kidder got an impressive amount of access at Data General when he wrote this book, and while he's honest and truthful about what happened there, Data General, at least to my 21st century mind, comes out of this book smelling like shit. I base this solely on what Data General does, and I know this because Kidder doesn't whitewash - he thankfully calls it right down the middle.

While the book is never accusatory, it makes clear that Data General is a predatory employer. It preys on young, semi-idealistic college Engineering graduates, who don't have a lot of job experience and are looking more for interesting problems to solve, interesting work to do, than a big paycheck. They promise them interesting problems, and briefly, very briefly, warn them that there will be long hours and possibly a limited social life, that this job will become their life. To meet the deadlines required of them they will have to give up friends, family, and the outside world, living only the job, for months or years at a time. Plus, because they're salaried, despite all the hours they get that would be overtime, they're only making their standard pay grade.

It chews up 22-24 year old kids, and spits them out at 30, burnouts who had great potential, but were consumed by their jobs. They don't say if many of these former employees stay in the industry, and some certainly do - Ray Ozzie, creator of Lotus Notes and current Chief Software Architect at Microsoft is a Data General veteran. However, those who leave the industry with a sour taste in their mouth will probably leave worse off then they would be if they worked somewhere else. Had they been actually paid overtime, they could have possibly built a nest egg that could have allowed them to retire early, or to at least take their time looking for work elsewhere.

While some poor decisions related to processor architecture helped to kill Data General right before the dawn of the 21st century, it is my suspicion that the boom in Silicon Valley may have inspired a brain drain. Nicer weather, a less oppressive corporate culture. For people who wanted more money, there was the change to come in on the ground floor of companies which had the potential to be worth millions and get significant stock options. For those who preferred challenge, they could face whole new challenges when designing new systems and new architectures at the new companies in the Valley.

In summary, the book is a high resolution snapshot of the early days of the computer industry, before the internet started to permeate our lives in subtle ways - computerized tax processing, credit cards, ATM machines, and so on, leading up to the more overt ways it would later find its way in - Bulletin Board Services, E-Mail, and finally, proper web pages. People interested in the history of the computer industry will certainly find this fascinating. People who don't care about the history of computing can still find something in the profiles of the people in this project, and how the project's process slowly wears them all down.

Great start to the series. Not that much of a shift from the first few episodes of the show, but still pretty good.

The first of the Hugo Award nominees I've finished reading. This is much more of a mystery-thriller novel then the last one. It's still military SF, but it's a certainly different take than the last book.

I'm doing a vlog post on this book later, but to put a long story short, I feel that the travelogue part of the narrative and the conspiracy part of the narrative just didn't mesh, and ultimately made reading the book an unpleasant slog. Thus, I'm lemming this book.

I'd describe this book as being a sort of Science Fiction take on the Adventures of Baron Munchausen, but with the satire amped up some. This is a fun book which is definitely worth checking out.

Another really good book. The book follows the “series of vignettes” style of the last book, but with more of a serialized tone instead of an episodic one.

There are a few things I'm wondering though, which might not be answered in future books - in particular, what City was Interstellar Master Traders supposed to be, exactly? Florence? Rome? Jerusalem? Goodness knows that last one would have some serious Unfortunate Implications if that was the case.

Also, the comments about New York's subways in the story also kind of makes me wonder - when New York lifted for the first time, was it just Manhattan Island? Did some of the other boroughs come along as well? Inquiring minds want to know?