Where Honesty Never Ends.
Disclaimer: A copy of this book was provided to The Review Board in exchange for an honest review.
Atlas is a war hero caught between his wife’s love or saving the survivors of Earth which has been destroyed by unknown forces. The closest thing to organized leadership are the packs of scavengers that take what they want. To keep his wife safe, he builds an army. To give her the life she wants, he fights. To win back their home, he must go to war. But she doesn’t believe that his sacrifice is for her and his selflessness is driving them apart. As he struggles for his wife’s devotion he is caught in a war with a tyrannical dictator. To win the war and his wife’s safety he must give her up and fight a war where defeat is expected. To fight a dictator he must become a warlord.
Hovering over everything is the threat of an alien invasion which Atlas slowly pieces together through unreliable stories told by the survivors. He soon learns that his fight is only a small part in a war that has been raging for hundreds of years and reaches throughout the galaxy.
A gritty and realistic action adventure book blends with minimal use of science fiction elements to create a rich, believable contemporary fiction story of one soldier’s heart-wrenching post apocalyptic journey to keep his family alive.
Hello and welcome to The Review Board. Today, Mini Truth speaks on “Code Name Atlas” by Tony Evans.
It’s difficult for me to put my thoughts about the premise of this book in any cohesive order as it’s truly a convoluted mess of happenstances. All I can say for sure is that it’s a dystopian novel based in the not so distant future when man is invaded by some sort of force and then has to fight to survive. It’s definitely a story that focuses on “war” more so than anything else.
Nevertheless, I will give it my best attempt at providing some sort of insight to the premise.
The main characters, whom we come to know as Atlas, is at odds with life. His wife is pregnant—about to go into labor at any moment—the world as we know it has fallen apart, and he finds himself having to take on the roll of the leader of a group of people he barely knows.
Later on in the story we discover that the “unknown force” that has destroyed the planet are aliens.
That’s about it. That covers most of the plot.
I have to start by saying something.
I am a lover of all things Science Fiction. I am always enamored by the idea of a great science fiction, dystopian story. However, the key (for me at least) is that the book must be well written, cohesive and easy to follow.
With that said, I find that I must push forward with my thoughts on this book as there are lots of them.
I’ve found in the past year or two, that it is really easy, in this age of advanced technology and self-publishing, to come across a book that has absolutely no Pros whatsoever. “Code Name Atlas” is one of them.
With that being said, I’ll dive right into the malfeasances of this book.
I went into this book with high hopes and looking forward to an amazing adventure. Instead what I found was heap loads of horse-pucky.
“Did ANYONE edit this book? Anyone? Anyone at all?“
This book was terribly written. What it reminded me of was a First Draft that was never edited, proofread or looked at, and published that way. I have screenshot after screenshot of grammatical and editorial blunders. I will share some with you.
I make no joke when I say that I have 28 screenshots of blatant mistakes inside of the book. The kicker is that I ONLY have 28 because after I hit 10 I opted to JUST take screenshots of the “really bad” mess ups.
In the images above you will see things like incomplete sentences, to misplaced modifiers, to nonsensical grammar, to bad spelling.
Also, the author SIMPLY COULD NOT get the spelling of the word “nauseous” correct. It was always spelled “nauseas” as seen below.
PS: I did cross examine this with the Cambridge English Dictionary to see if it might be an American English vs British English spelling differential. It was not.
Long Sentence Armageddon
I am not a fan of long, run-on sentences. Never have been, never will be. Even with that, I do realize that sometimes long sentences are inevitable. Sometimes, they just happen.
Yet, there is a difference with “the inevitable long sentence” and ruining your book with continuous long sentences.
“Code Name Atlas” LOVES run-on sentences, to the point of utter annoyance. Here are a couple of examples.
I was exhausted by the time I finished most of them! Kind of like I’d run a marathon or something.
Have you ever read a book and thought to yourself, “Where is the feeling?”
“Code Name Atlas” is the embodiment of unemotional. There are scenes that should have been replete with emotions and/or compelling descriptiveness. Instead, we find that the most sentimental parts of the story are skimmed over and delivered dryly just to make more space for war and/or methodical combat jargon.
Examples of this are when Atlas and Amori’s newborn daughter dies during delivery, and when Amori falls in love with Hector.
One scene in particular, stands out like a sore thumb.
Atlas gets shot, and judging by the description, one is led to believe that he is dead. The very next scene he is alive and well, and back at war. *shocked face*
HOW DID THAT HAPPEN?
Now, it’s not impossible for the hero of a story to survive a shooting, but please, for the love of all things holy, tell us HOW!
The Presence of Presumption
There is a huge dilemma with First Person Omniscient narrative. It is this:
The ONLY way the main character can tell what the other characters are thinking and feeling is if he/she is of a preternatural/supernatural origin. This is to say, conveying a story in First Person Omniscient can only be done if the main character slash narrator is a ghost, spirit, angel, god, and thing of that sort.
An average, every day, person CANNOT, BY ANY MEANS, chronicle a story in Omniscient form! Why? Because THEY CANNOT SEE AND/OR FEEL what the other characters are feeling!
“Code Name Atlas” is a prime example of how presumptuous First Person Omniscient narrative is as the main character take it upon himself to tell the reader exactly what is happening, or the other characters are feeling even when he is not there.
This story could have easily been cut in half—that is NO exaggeration—had it been properly weeded through.
I can never understand why authors tend to be so repetitious. Things don’t have to be constantly reiterated, unless they are of absolute importance.
That is all I’m going to say about that.
Holocaust of Holes
There are a wide array of plot holes in this story that have no resolution whatsoever. Things are mentioned, and not resolved. Inconsistent scenarios are a constant and do nothing but besmirch the story. Inconsistency is another form of plot hole.
Suffice it to say that “Code Name Atlas” was a very big let down. I could not, no matter how hard I tried, see any redeeming quality in this story. Which is sad, because at the very beginning I thought that the story had some sort of potential. Yet the further I got in, the more I realized that it did not. I’m flabbergasted by the many reviews that rave about this story, because I feel as though I read the wrong book.
I suppose what infuriated me the most was the fact that this book was first published in 2010. You would think that the author would have taken the time to take it off of the market, make it better and then republish it.
With all of that being said; survey says 1 out of 10 TRB Stars.
Thanks for checking out The Review Board. Feel free to share, subscribe, and like, Have a wonderful day.