Marlowe's Reviews > Boneshaker
Boneshaker (The Clockwork Century, #1)
by
by

Sixteen years after Leviticus Blue undermined the city's banks with his Russian-commissioned Boneshaker machine, Seattle is a very different place. The boring caused a gas to be released from deep underground, corroding whatever it touched and raising the dead as "rotters." A wall has been built around the city to keep the gas in, but it's only a matter of time before it comes spilling out.
In the meantime, Blue's son, Zeke, ventures under the wall, into the Blight, hoping to find the truth about his father. After an earthquake traps him inside the city, his mother comes in the hopes of rescuing him.
With airships, fantastical machinery, and zombies, it's hard to see where Boneshaker could go wrong. Unfortunately, there were a few key issues that prevented me from really liking the book. The first was the over use of coincidence. I can ignore it if it's used only very occasionally, or if it gets the ball rolling, and it works in a series like The Wheel of Time where it's explained by the world-building (in that case, it's the pattern weaving itself toward certain outcomes). But in Boneshaker, major aspects of the plot were directed by coincidence - an earthquake that blocks an exit just when a character goes through a tunnel, an airship crashing into a tower just when a character happens to be inside it, another airship that just happens to be repaired and ready to take off when the characters need to escape, etc. Far too much of the plot relied on these big coincidences, and it stretched my ability to suspend disbelief.
Overall, it gave the impression that Priest was writing on the fly, coming up with the plot as she went. Sadly, I found the characters suffered from the same problem; I found them very underdeveloped. They are always reacting, getting thrown about the city by circumstances as though they've paid for the tour. I was often confused by a decision, which seemed out of what I'd been able to construct of their character, until I realized that it was necessary to get them to the location of the next adventure, or to show us a new area of the city. (view spoiler)
Many of the side characters seemed interesting at first, until they stuck around long enough for me to realize that Priest had chosen one interesting image for them, and that was it. They had cool armour, or an interesting look, or an implied backstory, but no depth. In fact, the only character that seemed to have any real personality was the setting. Which leads me to the book's real strength: Seattle.
There were some anachronisms, but the alternate history provided some cover there. I still always enjoy it when books have a sense of place, and the landmark details certainly did that. Priest also clearly put a good deal of thought into how the city might look in the Blight. The ambiance, with the need to wear gas masks and the moaning of the rotters, was fairly well done, and Priest certainly did a reasonably good job of building tension, except that I just didn't care what happened to any of the characters. As long as I could tour the setting along with someone, I found that I really didn't care much if it was Briar/Zeke, or if they were switched out midstream for some other "guide."
The mechanics of writing were mostly solid, but there were some very odd word choices that threw me. One that stood out in particular was the use of the word "for" instead of something more conventional, like "because." It's oddly archaic, and stands out from the text around it. I noticed the same thing in Huntress by Malinda Lo, and it bugged me there, too.
My final gripe is about the ending. The plot structure is what could be described as an "onion" plot, in which the real goal is the discovery of a piece of information - in this case, what happened with the Boneshaker machine. The question is raised at the very beginning, with a reporter approaching Briar for information, and it is finally answered at the very end. Unfortunately, the answer that had all the characters guessing, and at least one character risking his life and the lives of others to uncover, was almost immediately obvious. I read the whole book knowing the ending's big reveal, and my disappointment was dampened only by the fact that Priest seemed to care as little about it as I did. Sadly, it came with a missed opportunity, as I think that much more could have been made of the connection between Angeline's daughter and Briar, if only the characters had had a little more depth to them.
I found this to be a fun fluff book, and the setting is certainly interesting enough to make it worth reading. It could have been a lot better, though, and it's a shame that the characters and plot weren't able to better complement the location.
In the meantime, Blue's son, Zeke, ventures under the wall, into the Blight, hoping to find the truth about his father. After an earthquake traps him inside the city, his mother comes in the hopes of rescuing him.
With airships, fantastical machinery, and zombies, it's hard to see where Boneshaker could go wrong. Unfortunately, there were a few key issues that prevented me from really liking the book. The first was the over use of coincidence. I can ignore it if it's used only very occasionally, or if it gets the ball rolling, and it works in a series like The Wheel of Time where it's explained by the world-building (in that case, it's the pattern weaving itself toward certain outcomes). But in Boneshaker, major aspects of the plot were directed by coincidence - an earthquake that blocks an exit just when a character goes through a tunnel, an airship crashing into a tower just when a character happens to be inside it, another airship that just happens to be repaired and ready to take off when the characters need to escape, etc. Far too much of the plot relied on these big coincidences, and it stretched my ability to suspend disbelief.
Overall, it gave the impression that Priest was writing on the fly, coming up with the plot as she went. Sadly, I found the characters suffered from the same problem; I found them very underdeveloped. They are always reacting, getting thrown about the city by circumstances as though they've paid for the tour. I was often confused by a decision, which seemed out of what I'd been able to construct of their character, until I realized that it was necessary to get them to the location of the next adventure, or to show us a new area of the city. (view spoiler)
Many of the side characters seemed interesting at first, until they stuck around long enough for me to realize that Priest had chosen one interesting image for them, and that was it. They had cool armour, or an interesting look, or an implied backstory, but no depth. In fact, the only character that seemed to have any real personality was the setting. Which leads me to the book's real strength: Seattle.
There were some anachronisms, but the alternate history provided some cover there. I still always enjoy it when books have a sense of place, and the landmark details certainly did that. Priest also clearly put a good deal of thought into how the city might look in the Blight. The ambiance, with the need to wear gas masks and the moaning of the rotters, was fairly well done, and Priest certainly did a reasonably good job of building tension, except that I just didn't care what happened to any of the characters. As long as I could tour the setting along with someone, I found that I really didn't care much if it was Briar/Zeke, or if they were switched out midstream for some other "guide."
The mechanics of writing were mostly solid, but there were some very odd word choices that threw me. One that stood out in particular was the use of the word "for" instead of something more conventional, like "because." It's oddly archaic, and stands out from the text around it. I noticed the same thing in Huntress by Malinda Lo, and it bugged me there, too.
My final gripe is about the ending. The plot structure is what could be described as an "onion" plot, in which the real goal is the discovery of a piece of information - in this case, what happened with the Boneshaker machine. The question is raised at the very beginning, with a reporter approaching Briar for information, and it is finally answered at the very end. Unfortunately, the answer that had all the characters guessing, and at least one character risking his life and the lives of others to uncover, was almost immediately obvious. I read the whole book knowing the ending's big reveal, and my disappointment was dampened only by the fact that Priest seemed to care as little about it as I did. Sadly, it came with a missed opportunity, as I think that much more could have been made of the connection between Angeline's daughter and Briar, if only the characters had had a little more depth to them.
I found this to be a fun fluff book, and the setting is certainly interesting enough to make it worth reading. It could have been a lot better, though, and it's a shame that the characters and plot weren't able to better complement the location.
Sign into Å·±¦ÓéÀÖ to see if any of your friends have read
Boneshaker.
Sign In »
Reading Progress
Started Reading
July 17, 2015
– Shelved
July 17, 2015
–
Finished Reading