He does not speak. His code makes the world listen.
Leo Silva has never said a word. Autistic and non-verbal, he understands the world through patterns and signals. In the quiet of his father’s basement office, he talks in the only language that makes sense to him: network scans, scripts, and silent packets that cross borders without a sound.
Miguel thought he had buried that world. Years ago, he was known in the shadows as Kill-Switch, a hacker ghost who walked away to protect his family. Now, an echo from an old hard drive is enough to put his name back on the radar of Russian intelligence and on the screens of cyber defence analysts in Berlin.
Across Europe, agencies think they are chasing the return of a legend. What they are really seeing is Leo’s code.
As pressure closes in on the family, Miguel is dragged back toward the life he swore he had left behind. To protect his son, he has to expose who he really is and hope his past does not destroy what is left of their future.
He does not speak. His code makes the world listen.
Leo Silva has never said a word. Autistic and non-verbal, he understands the world through patterns and signals. In the quiet of his father’s basement office, he talks in the only language that makes sense to him: network scans, scripts, and silent packets that cross borders without a sound.
Miguel thought he had buried that world. Years ago, he was known in the shadows as Kill-Switch, a hacker ghost who walked away to protect his family. Now, an echo from an old hard drive is enough to put his name back on the radar of Russian intelligence and on the screens of cyber defence analysts in Berlin.
Across Europe, agencies think they are chasing the return of a legend. What they are really seeing is Leo’s code.
As pressure closes in on the family, Miguel is dragged back toward the life he swore he had left behind. To protect his son, he has to expose who he really is and hope his past does not destroy what is left of their future.
Berlin, night shift
Irina worked the night shift in Berlin's security operations center. One row of monitors was on. The rest slept to save power. Her mug was cold. She was clearing backlog. Calm night.
A blip hit the feed, not an alarm, but a dormant pattern. Partial, two fields off.
She opened the case index. A tag no one had touched in years. KILLSWITCH-08. Archived, no owner.
She read the old notes: redactions, short transfer chain, closure memo. No source, no willing victim. The pattern went quiet.
The new hit came from a home router on the west side. Tenant unknown. The traffic looked routine. The signature did not. It drifted the same way as the archive. One step off, then two.
She compared old and new. Four near misses. One clean match when she widened the window to six hours. The rhythm fit the tail of the old set.
02:16.
She pulled the raw data. Rebuilt it. Small. One request out, four-second delay, one answer back. No message inside, only a marker. The marker used a key that should not exist outside this building.
She reopened the case. Status: active, quiet.
No alerts, no pager, no group email. Quiet means watch first. Ask for help without naming the target. Do not let the other side know you are looking.
She queued four requests. Traffic records from the provider for the last 72 hours. A sample of network flow in a ten-block radius. A watch on two addresses tied to the archive. A flag for any device that matched the original hardware.
She typed a note: old timing pattern, partial match to Kill-Switch (KS), no damage seen, recommend silence watch, review 08:00.
She drafted tags to two teammates and a supervisor. The cursor blinked. She deleted the tags. Kept it internal. Quiet stays quiet.
She checked the archive again. Last time this pattern moved, it spread slow. Small systems. Old equipment. Places that made no noise when they failed. The notes mentioned missing logs and broken backups. Someone patient. Someone precise.
Back to live. Another signal, same shape, same drift. Then nothing.
She started a seven-day search. Logged to a private folder. If it woke again, she would see it.
She left the case open on a side screen. Sent a request to a utility contact. Power flickers on the same blocks. Last 24 hours.
02:29.
The ceiling fan clicked. The graph flattened. She sipped cold coffee. Opened a text window. Typed three words. Deleted them.
If the pattern was real, a hand was still on it. Not dead. Not gone. Waiting.
She saved the case.
Somewhere, something listened back.
Day by day, eight-year-old Leo maps his world through the comfort of computer coding and learning to watch and collect the intricate patterns that shape the boundaries of his life. Little does he know that others are watching – tracking his moves and targeting him because of his father, Miguel’s, involvement in a certain long-forgotten project. Though he escaped his clandestine past, those he left behind have caught up. Now, Miguel has the comfort of home and a family to protect. Has the former hacker gone too soft to save his prodigy from the world that gave the silent boy speech? And will his family find peace in the end?
​
Silence in the Code by Luciano Patrao introduces the complexities of computer coding through the eyes of an eight-year-old non-verbal autistic. In the first half of the book, the reader gets to explore Leo’s world while the young computer prodigy sets up his own network and learns the ins and outs of cyberspace. He maps patterns and gains confidence, even to the point of defending his older sister against cyber bullies through the use of his new skills. A sense of danger builds as the reader learns of the other computer analysts watching the young boy. Both friend and foe establish connections to the child, creating an urgency to find out whether Miguel will be able to clean up his past before it's too late to save his family.
​
The story includes a lot of coding language, text scripts, acronyms, and technical lingo, which sometimes makes the book difficult to follow. Occasionally, it’s also difficult to track the story as repetitive information, point of view changes, and several inconsistencies interfere. With the number of characters, it also became unclear who the real main character was, and the distance in the third-person narrative kept the reader from fully connecting with the characters in general. While the opening half of the book focused on Leo and his story arc, in the second half, he fades into the shadows. Instead, the focus changes to the conflict with Leo’s father and the other hacker connections he has from the past. This would be okay, but the resolution of this conflict felt rushed, without fulfilling the promised suspense foreshadowed.
​
The writing flowed in a pattern that mimicked the rhythm of typing on a keyboard, which fit the story’s themes of connection through coding. At times, the story seemed to drag or skip important details. Still, there were several shining moments as Leo demonstrated his skills, and it was comforting to experience the brotherly affection he shared through touching scenes with his sister Carol. Leo also gains a silent protector who monitors him from behind the scenes and relates to him through her own experiences with neurodiversity.
​
Silence in the Code is a solid choice for readers who are interested in neurodivergent characters and their interactions with the world. This book presents an interesting observation on the unique and fascinating ways that autistic minds function and navigate life. However, the complexity of the computer lingo may make this best suited for readers who enjoy technical language and computer coding.