This book was incredible. I loved the story, characters, descriptions, and writing style.

I don't normally read stuff like this, but I found it held my interest the whole way and I really enjoyed it.

This book has *many* basic eng.comp. problems, but a good s/f world is inside of it. If you cannot get past poor punctuation and grammatical errors - do not start. If you are more used to reading books on twitter or are able to skip the surface to think about what the world-building inside the book is - then it's got a great story for you.

The way this title downloaded made it impossible to read. Instead of being a full page, it was two pages and I simply could not read the words. I still do want to read the book and I will get it from the library.

Poorly written and little to no editing. This book reads like an outline rather than any thought out tale. I do not recommend.

I wanted to like this book, alas it did not happen. The premise was good, the reading... not so much. If found this book to be very wordy but didn't tell you anything. It was to vague at the beginning and very slow throughout the whole book.

Ames: Book One by Jeremy Whitehead
My rating: 2 of 5 stars

Thanks to Netgalley for the ARC!

I'm afraid I'm going to have to be rather harsh on this one.

I don't like to think that grammar issues bother me because I'm fairly well-read in poetry and much is left to the reader's discretion, but after counting perhaps hundreds of misplaced commas, wrong words, clunky wording and odd repeats, I have to wonder if this manuscript is a first-draft. I can easily ignore 5 or 6 of them, and if the rest of the text is solid, I can totally ignore the fact that the commas are outside of the quotations, but there was just too much to ignore. It was difficult reading. The flow was constantly interrupted.

Now, assuming that I can get beyond that and focus right on the story, or, failing that, the interesting features of the world-building, I still have some major issues.

I love the basic premise of a big city of robots, but the two warring factions basically annoyed me to death right off the bat, Orwellian or not. I loved some of the action scenes and I thought the basic virtual reality premise and execution was interesting, but there was way too much filler. I didn't care so much about the robot's fascination with toilets. There's a lot more going on in the background for me to really care about a toilet, and that's just a single tidbit out of hundreds of prosaic bits that could be utterly excised in favor for interesting action and espionage and explosions and big mystery reveals, of which this book HAS PLENTY. I mean, right off the bat, there's enough big happenings going on that we can keep the pace up without issue and have a fast-paced, idea-rich, world-building adventure in half the pages. No problem. Instead, we have *actual* virtual world-building and a clunky romance that seems ridiculous while we've got the granddaddy of all AIs thrashing about the house and a cabal of other AIs gathering to destroy whole civilizations.

I mean, it could work, but it doesn't. And that's where my other main concern lay: the characters. They were cookie-cutters. They all sounded alike, and in one case that might be intentional, but I didn't believe for a second that one or the other was a super brilliant scientist or a mastermind genius AI able to overcome any obstacle. I'm told that they are. Repeatedly. But, again, this is where a second or a third pass on revision could have REALLY helped out. It's almost as if all these characters were placeholders for actions but they weren't really intended to be a vital part of the grand story except as an afterthought to all the world-building.

I'm not saying this couldn't be a great novel. I think it has potential to be a real blast! BUT, I think it needs the careful dedication of a serious editor. This release is too soon! Sorry.

I do, however, wish the author much luck!

(This review will be posted at the CCLaP website [cclapcenter.com] on January 30th, 2017. Any questions concerning it can be addressed to Jason Pettus at cclapcenter@gmail.com.)

To review Jeremy Andrew Whitehead's <i>Ames</i> is an inherently frustrating experience, and a great example of why it can be so difficult to give a fair shake to self-published literature. Because to be sure, there's a great science-fiction novel buried within this manuscript, based on a really thought-provoking premise that brings to mind Charles Stross' cult favorite <i>Saturn's Children</i> -- namely, what would happen if a ship full of human colonists in suspended animation were sent to a planet to sleep underground for a thousand years, while a team of artificially intelligent robots spent a millennium terraforming that planet into a habitable state, just for those robots to realize a couple hundred years in that they don't actually need the humans at all, and that they could start their own civilization just fine?

That's a great concept, and gives Whitehead room to explore all kinds of interesting world-building questions related to a society that was built specifically for robots that are intentionally modeling themselves after humans; a world with no bathrooms but with recharging stations built into every vehicle and piece of furniture, a world where a small cabal of "first gen" AIs deliberately create millions of less intelligent minions that they control like Orwellian fascist nation-states. And what would happen in such a world if one of those long-dormant underground humans was finally woken up to reassert control? That's another fascinating question, one that fuels the action-adventure plot seen here; so what a shame that this book still needs so much basic work when it comes to proofreading and editing in order to be taken seriously as a piece of literature. And that's the problem with self-published novels in a nutshell; that in an age where it's so incredibly easy to convert a Microsoft Word document into a finished and published paper book for sale to the public at Amazon, it's becoming harder than ever for such authors to secure professional editing services to make those books worth reading in the first place.

<i>Ames</i> is essentially a 500-page book with only about 250 pages of actual interesting content, written by an aerospace engineer who mistakes the detailed procedural lists that come with product analysis for a compelling narrative; and so while that generates some really heady ideas for us to ponder, those ideas are couched within pages upon pages of mind-numbing filler, adding up to a wash whose bad parts equally cancel out the good ones. (Just as an example, the act 1 setup of the story takes Whitehead an entire 125 pages to get across, when it should've been over and done with by page 30 or so.) And this is not to mention the literal hundreds of basic grammatical errors found within the manuscript, things that spell-checks will never catch like Whitehead's habit of putting his dialogue's punctuation outside of his quotation marks instead of inside, which as a heavy reader drove me crazier and crazier with each successive page.

This could've been easily solved if he had had an extra thousand bucks to hire an actual professional editor to give this a once-over; and therein lies the problem, in that actually publishing the book through a place like CreateSpace only costs a tiny fraction of that, leading most self-published authors to skip this expensive and time-consuming but such critical step. I'm still giving <i>Ames</i> a decent score, because just the concepts alone being bandied about is worth giving it a look, especially for extra hardcore SF fans who aren't as bothered by basic grammatical mistakes; but for general-interest readers who are, this is going to be a frustrating read, something one hopes that Whitehead will fix before releasing part 2 of this planned trilogy.

Out of 10: <b>7.4</b>, or <b>8.4</b> for hardcore science-fiction fans