I didn’t grow up dreaming of becoming a writer. I grew up solving problems. Fixing systems. Tracking down the thing that was broken before anyone else noticed it was broken. For most of my career, that meant working in environments where precision wasn’t optional — air traffic control, cybersecurity, infrastructure protection. The kind of work where a missed detail doesn’t just cost money. It costs lives.
Writing found me the way most important things do: not as a choice, but as a necessity.
The Moment It Became Necessary
There was a specific day. I was reviewing an incident report — a real one, not a drill — involving a vulnerability that had been sitting in a production system for over two years. Not a sophisticated zero-day exploit. Not some elite nation-state attack. A misconfigured access control list. Something a junior analyst should have caught in a routine audit. And because nobody caught it, an attacker had been quietly exfiltrating data for months. The breach affected thousands of people who would never know exactly what happened to them or why.
I sat with that report for a long time. Not because it was technically complex — I’d seen worse. But because I realized something that had been building in me for years: the public has no idea. They have no idea how fragile the systems they depend on actually are. They have no idea that the power grid, the air traffic control network, the financial infrastructure, the water treatment systems — all of it runs on layers of technology held together by underfunded teams, legacy code, and institutional inertia. And the people making policy decisions about these systems often understand them even less than the general public does.
I’d been telling colleagues this for years. Writing internal reports. Giving briefings. Recommending fixes. And I kept running into the same wall: technical accuracy doesn’t move people. Data doesn’t change behavior. You can put the most alarming statistics in front of a decision-maker and watch them nod, thank you for the briefing, and change absolutely nothing.
That was the day I understood that if I wanted people to actually grasp what I’d spent my career seeing, I couldn’t write another white paper. I had to write a story.
The Intersection of Cybersecurity and Storytelling
Cybersecurity and storytelling have more in common than most people think. Both are fundamentally about understanding human behavior. Both require you to think like someone else — in security, you think like an attacker; in fiction, you think like every character on the page. Both demand that you see the system as a whole while tracking dozens of individual threads. And both punish you severely for getting the details wrong.
The difference is reach. In cybersecurity, I could protect one organization at a time. I could harden one network, train one team, close one vulnerability. Important work. Necessary work. But limited. A novel reaches thousands of readers. A good novel reaches them at a level that no briefing or training module ever will — it reaches them in their gut, in their imagination, in the part of the brain where fear and empathy and understanding actually live.
When someone reads a thriller where the technology is accurate and the threat is real, they walk away with something that no news article gives them: an intuitive sense of what these systems feel like from the inside. They understand, not just intellectually but viscerally, what it means when someone says the grid is vulnerable. They understand what cascading failure looks like. They understand that the people defending these systems are human beings making judgment calls under pressure, not omniscient guardians with unlimited resources.
That’s what I set out to build. Not entertainment disguised as education, and not education disguised as entertainment. Just honest stories set in worlds I know, written with the accuracy those worlds deserve.
Building Something Permanent
There’s a particular frustration that anyone in technology knows intimately: everything you build gets deprecated. The system you spent two years architecting gets replaced. The code you optimized gets refactored by someone who never read your documentation. The security framework you designed gets abandoned when the organization restructures. You pour years of expertise into something, and five years later it might as well have never existed.
Books don’t work that way. A book, once written, is permanent. It exists independently of any platform, any organization, any budget cycle. It doesn’t require maintenance. It doesn’t get patched. It doesn’t go end-of-life. A hundred years from now, someone can pick up a novel and experience exactly what the author intended. There is no equivalent in technology. There is no equivalent in almost any other field.
That permanence matters to me. Not out of ego — I don’t need my name to outlast me. But because the things I’ve learned and the things I’ve seen deserve a form that endures. The lessons embedded in a well-crafted story survive in ways that technical documentation never will. Procedures change. Regulations change. Technology changes. But the human dynamics — the pressure, the trade-offs, the moral weight of protecting systems that people trust without thinking — those are constant. And fiction is the right vessel for constants.
What Stories Do That Code Doesn’t
I’ve spent enough years writing code and writing prose to know exactly where each one fails. Code is precise. Code is logical. Code does exactly what you tell it to do, which is both its power and its limitation. Code cannot make someone feel what it’s like to be the analyst who discovers a breach at two in the morning and has to decide, in real time, what to escalate and what to investigate quietly. Code cannot convey the specific dread of knowing that a system is compromised and not yet knowing how deeply. Code cannot make a reader care about a fictional character enough to stay up until three in the morning turning pages.
Stories do all of that. Stories create empathy for people the reader will never meet in situations the reader will never face. Stories make invisible threats visible. They take abstract concepts like “critical infrastructure vulnerability” and turn them into scenes with human beings in rooms making decisions that have consequences. That translation — from abstract to concrete, from technical to emotional — is the most important work I do.
And it matters beyond entertainment. When readers internalize a story about a cyberattack, they become better citizens. They ask better questions. They hold their institutions to higher standards. They stop assuming that someone else is handling it. Fiction, done right, is a form of public education that bypasses every defense mechanism people have against being lectured.
The Gap Between Thriller Fiction and Reality
I read thrillers voraciously before I started writing them, and I kept running into the same problem: the technology was wrong. Not in small ways — in fundamental ways. The hacking scenes read like they were written by someone whose understanding of cybersecurity came from movie montages. The procedures were invented. The timelines were impossible. The organizational dynamics bore no resemblance to how agencies and corporations actually function.
I don’t blame those authors. Most thriller writers are outsiders to the worlds they write about, and they do their best with research. But there’s a difference between research and experience. Research tells you what a SOC (Security Operations Center) looks like. Experience tells you what it smells like at hour fourteen of an incident response — the stale coffee, the tension in the room when you realize the attacker is still inside the network, the particular silence when a senior analyst says “we need to escalate this.”
That’s what I bring to the page. Not just technical accuracy, though I insist on that. The texture. The rhythm of how these environments actually operate. The jargon people really use versus the jargon that sounds impressive in fiction. The bureaucratic friction that shapes every real-world security decision. The gap between what the protocol says and what actually happens when you’re running out of time.
I write the thrillers I wish existed — the ones that get it right.
The Broader Vision
But Caliana Press is not just a thriller imprint. It’s the expression of something larger.
Under the pen name Evelyn Martinez, I write literary fiction — stories about identity, inheritance, silence, and the things families carry across generations without ever naming them. These are quieter books, slower books, books that sit with ambiguity instead of resolving it. They matter to me as much as the thrillers, because not every important story involves a countdown clock.
Under the pen name Daniel K. Wanyama, I’m building something I’ve wanted to build for years: a multi-volume historical fiction saga that traces a single family from pre-colonial East Africa through the centuries — through displacement, through the Middle Passage, through Jim Crow and the Great Migration, through the Civil Rights movement and into modern America. It’s a project that demands years of research and an unflinching commitment to getting the history right. The scope is ambitious. Twenty books. Five centuries. One unbroken bloodline. I don’t take that lightly.
And beyond fiction, Caliana Press publishes educational materials — resources built to the same standard of quality, designed to help students and professionals achieve what they’re capable of.
The common thread across all of it is simple: respect for the reader. Every reader who picks up a Caliana Press book is trusting me with their time and their attention. I don’t take that for granted.
The Caliana Standard
“Caliana” comes from a word meaning beauty, excellence, and grace. The name is a commitment. Every book that carries the Caliana Press imprint goes through rigorous development. Research is exhaustive. Facts are verified. Prose is crafted sentence by sentence. There is no shortcut, no rush to market, no compromise in the name of speed.
I don’t write fast. I write right.
That’s not a marketing line. It’s the operating principle behind everything I publish. In an era when the market is flooded with content produced quickly and carelessly, I believe there is still a readership that values craft. Readers who want to trust that the author did the work. Readers who can tell the difference between a book that was assembled and a book that was built. Those are my readers, and I will not let them down.
What’s Ahead
The CRITICOM Files is the beginning, not the end. The ALARIS Protocol explores the emerging intersection of artificial intelligence and national security. The BLACKWOOD Dossier takes readers inside intelligence dynasties and digital warfare. The OBSIDIAN Line moves the action to Kampala, Uganda, and confronts the geopolitics of technology in East Africa. Blood Unbroken spans five centuries. And there are projects I haven’t announced yet that I think about every day.
The roadmap is long. The standards are fixed. And the work continues.
If any of this resonates with you — if you want to follow the journey, get early access to new releases, and hear directly from me about what’s coming — subscribe to the Caliana Press newsletter. I don’t spam. I don’t sell your information. I just write to readers who care about the same things I care about.
The best stories are still ahead.
— Martin
