Writing The Alchemist Triangle: Where the Idea Came From

People assume a book like The Alchemist Triangle: A Deadly Game of Science and Secrets starts with a plot. For me, it started with a discomfort. I spend my working life inside systems built on trust — cloud architectures, security frameworks, partnership agreements — where the entire structure depends on everyone believing the same version of reality. The question that wouldn't leave me alone was a simple one: what happens the moment that trust turns out to be misplaced, in a field where most people assume the science itself is neutral?

That question is the real seed of the book, long before there was a triangle, a game, or a single named character on the page.

Research as a side effect of curiosity, not a project plan

I didn't set out to research a thriller the way I'd scope a technology deliverable. The research happened sideways, as an extension of work I was already doing — reading around cloud security, data integrity, and the quieter ethical questions that come up wherever science, technology, and money intersect. A lot of what ends up dramatized in The Alchemist Triangle began as margin notes on things I was reading for entirely different reasons, questions I couldn't fully answer in a work context but couldn't stop turning over either.

Fiction let me ask the question I couldn't put in a slide deck: what does it cost a person to keep a secret that a system depends on?

Why a "deadly game," and why secrets

The title isn't decoration. Every serious technical environment I've worked in runs, underneath its official process, on an informal game of incentives — who gets credit, who takes the blame, what gets escalated and what gets quietly absorbed. Most of the time that game is harmless. I wanted to write the version where it isn't. Where the stakes of a hidden move are not a missed quarter but something irreversible. Setting that inside a world of science and secrets gave me a canvas large enough to dramatize something I genuinely believe: that the biggest risks rarely come from bad technology. They come from good people making quiet, defensible-seeming decisions that compound.

Writing at the edges of the day

The honest answer to "when did you write it" is: in the margins. Early mornings before calls started, on flights, in the gaps between one deliverable closing and the next one opening. I didn't have the luxury of long, uninterrupted writing stretches, so the book was built the way most enterprise transformation programs actually get built — in disciplined, imperfect increments, revised repeatedly, with the throughline held in my head across long gaps rather than on the page. If there's a craft lesson in that, it's this: a manuscript doesn't need continuous time to become coherent. It needs a writer who keeps returning to the same throughline even when the writing sessions themselves are scattered.

What I hope readers take from The Alchemist Triangle isn't a verdict on any particular industry — it's a genuine unease about how ordinary the road to a serious mistake usually is. That's the version of "science and secrets" I set out to write, and it's the one I'd write again.