First, let me say that the premise for this book is fantastic. I loved the idea of blending autonomous vehicle technology with "the grid" and technology DOTs have in place currently for the purpose of streamlining traffic and reducing (or actually eliminating) traffic accidents/fatalities. It's a future we're likely to see in a decade or so, and the idea of a terrorist cell hacking in to manipulate the system once it's set up is a perfect thriller novel...
I attempted to get into this book three times. I wanted to love it. I wanted to get swept up in it and get swirled into an action-adventure-thriller-mystery novel that put a civil engineer in the driver's seat. On this third attempt, I got to page 84 before I gave up.
I can't tell what year the story is supposed to be taking place, but a professor mentions colleagues hiding in bomb shelters they built in the sixties; this puts a limit on how far in the future the action can realistically be happening, yet the main character (Jake) not once in 84 pages attempts to access the Internet via a smart phone...and he's made it very clear that he MUST get on a computer and access the Internet ASAP to start solving problems.
The mechanics of storytelling matter to me, and too many quirky phrasings took me out of the story. Examples: (from page 8, when contemplating being kept in a safehouse) "Similar to the way a dehydrated desert wanderer would crave an entire pool full of cool water, he desired more than anything to be free again and to make sure his family was safe." (from page 9) "He loved his country, but after what he had been through, his faith had been shattered like a cheap wine glass on a Spanish-tile floor." (from page 25, describing the terrorist) "With his sixty-two-year-old arms crossed over his plain white cotton shirt which hung loosely on his chest, and his gray beard with streaks of black running throughout, he swayed back and forth like the pendulum of a grandfather clock on meth." (from page 59, when Jake is talking to two new FBI agents) "They stared at him like hot-headed football coaches at a quarterback who'd thrown a third interception."
In just the first 84 pages, a guard pulls a "hood" out of thin air and an FBI agent pulls a hat and shades out of thin air. It was glaring enough that it bothered me and I stopped to make a note in the margin: "things keep appearing out of thin air". Jake and the professor he goes to visit (and I found it improbable that his FBI agent friend would risk letting him go to a meeting alone, given the danger he's in) have similar problems with cursing. The first time the characters use a "non-curse word," it's almost striking because the narrative and the dialogue are speckled with expletives and unnecessary cursing. It makes the reader think, "oh, hey, this guy must be a goody two shoes and we're getting that signal by the use of a silly word," and then the next time he speaks he uses an f-bomb. So...no. Not a goody two shoes...just strange.
These are things that pulled me from the story, which was being explained and re-explained by Jake and the FBI characters again and again. I fully understand that Jake was part of a team of six engineers who developed an awesome transportation system that took many years and multiple millions of dollars to build and implement. Then a terrorist got in through a back door in the coding and at least five thousand people (as of page 84) are dead. The terrorist is a bad guy. Bad.Guy. But on page 84, the author goes too far for me. I had put up with the needless swearing, the bizarre similes, the wordiness, the cliche FBI characters, Jake's illness every time he was in a small moving vehicle (well, almost every time), the repetition, and a number of grammar mistakes, but when the author stooped to racial slurs on page 84...I quit. I get that the terrorist is to be portrayed as a mentally unstable and totally unlikable dude...but that doesn't mean I have to read those kinds of words. I don't want them in my brain.