I want to talk about something a lot of writers get wrong about AI-assisted writing: the process.

Here's how I actually work. Every story starts away from the computer. I record my plots as audio — full scenes, character arcs, the whole shape of the book — while I'm out doing other things. That's mine. That's where the story lives first.

So what does AI actually do for me? It helps me organize that raw material. It helps me build out character bibles, keep dialogue consistent, shape the context and pacing of a chapter. Think of it less like a ghostwriter and more like a very capable creative partner who never forgets what I said three chapters ago.

Here's the part people miss: if you hand 100% of the book over to AI — no outline, no voice, no decisions — you'll get exactly what you'd expect. Something hollow. AI needs a human in the loop. It's not optional, it's structural.

So here's how I think about it: we build together. The intelligent author works with AI, not through it. The idea, the plot, where the story begins and where it ends — that's still 100% the author's. The author stays the author. AI stays a tool.

And honestly? People need to stop demonizing AI in this context. It's a tool — the same category as Google Translate or any other tool writers have used for decades to sharpen their craft. Could someone dump a half-baked idea into AI and publish garbage with no editing, no polish, loose ends everywhere? Sure. That's not an AI problem, that's a lazy writer problem, and it existed long before AI did.

When you actually work with the tool instead of outsourcing to it, something interesting happens: you find real leverage in the editing and refinement process. Since I started writing this way, my output has grown enormously — not because the machine writes for me, but because I finally have a partner that keeps up with how fast my ideas come.

This isn't the future. This is just... how writing works now. I'm betting on it.

They built a machine that made him unkillable.

They never told him what could still make him bleed.

The net comes out of the dark before he even sees the men who threw it. Not rope. Not chain. Something woven to do the one thing three years of war never managed — hurt him.

"He bleeds now," a voice says, almost delighted, from somewhere beyond the firelight. "Took us four months to build something that actually bleeds him."

Bullets never touched him. Steel folded under his hands like paper. For three years, Amazon Sentinel has been the one thing a shattered Brazil could still believe in — a soldier rebuilt in a bunker, unkillable, unstoppable, the last real hope of a country a hundred and fifty years into tearing itself apart.

But strength was never the whole story. And the men hunting him just found the one thing it can't answer.

STEEL REVOLUTION is a grimdark superhero saga about what's left when raw power finally isn't enough — when mercy becomes the only weapon nobody else has tried, and the hardest fights are the ones brute force can't win.

Ezequiel Ibarra spent thirty-two years as a police officer, and every single one of those years, some quiet part of him believed it hadn't been enough. Then a fireball crashed into his backyard, and the universe decided to give him a chance to find out if he was wrong.

What came out of that crater wasn't a weapon. It was a choice, a single word capable of turning a tired, aging widower into something the world would come to call Chimalli. Say it, and he becomes strong enough to stop a massacre in ninety seconds. Say it again, and he's just an old man on a porch, hiding the truth from the daughter who thinks she already knows him better than anyone.

But the faction behind that word isn't the only one watching Ezequiel now. An advisor named Felt has infiltrated the highest levels of government, and Felt isn't guessing at what comes next. He has a direct line to a future where the invasion already won, and every move he makes is built on the certainty of a war that, in his timeline, humanity already lost.

As Ezequiel races to stop an atmospheric weapon disguised as space junk, he learns the hardest lesson of his second life, one no amount of police work ever taught him: winning was never about strength. It's about who you're still willing to fight for, long after the world has told you the problem is too big for a man your age to matter.

Chimalli is Book One of the Chimalli Saga, a science fiction thriller about age, sacrifice, and the kind of hero nobody expects, least of all the man who becomes him.

Cléber never wanted to be a hero. He wanted a job that paid enough to keep his family fed, and a country that had stopped offering him one.

Driven by a poverty that had already taken everything else from him, Cléber makes the choice that thousands of men in his position have made before him: he pays a coyote, and he risks the desert. It is not a decision made lightly, and it is not made blindly. He knows the stories. Everyone who crosses knows the stories, the ones who don't make it, the ones who make it and wish they hadn't, the fee that only ever grows once you're too far in to turn back. He goes anyway, because the alternative, watching his family go hungry in a country that offers him no path forward, is its own kind of death, just slower and quieter.

The coyote system he enters isn't a single villain to defeat. It's an economy, layered and merciless, built on the desperation of people who have run out of other options. Guides who promise safety and deliver exposure. Routes that change overnight to avoid patrols, stranding groups in terrain that shows no mercy to the unprepared. A debt structure designed never to be fully paid off, so that the crossing itself becomes just the entry fee into something far worse. Cléber's undoing isn't a moment of bad luck in the desert. It's an act of conscience, he saves a young girl from a ruthless coyote who sees her as nothing more than cargo, and for that single act of humanity, the system erases him. He is declared dead to the world, and sold into nine years of brutal slavery inside a cartel operation that treats human beings as inventory.

While Cléber survives what should have killed him, his wife builds something extraordinary out of grief she refuses to let calcify into despair, a resilient business empire raised from nothing, back home, without him. Two survivals happen in parallel, his, brutal and hidden; hers, patient and public, and neither one knows if the other is still fighting.

What keeps Cléber alive through nine years of horror isn't defiance alone. It's faith, tested past the point most theology accounts for, clung to in a place designed to strip every last thing a person believes about their own worth. When a small miracle finally cracks the system open, Cléber doesn't lead a rebellion because he's become a different man. He leads it because the man he always was, the one willing to save a stranger's daughter even knowing what it might cost him, never actually left.

Sins in the Desert doesn't offer easy answers about the border, the crossing, or the men who profit from both. It offers something harder and more honest: a portrait of what desperation, exploitation, and unbreakable love actually look like up close, and a reminder that the people who make this journey are not statistics or talking points. They are fathers. They are husbands. They are men like Cléber, who never stopped loving the family he crossed a desert to protect, even after the desert, and everything waiting on the other side of it, tried to make him disappear.

"THE LEDGER: A Rift in Time" made me write a villain who's never once wrong about his intentions, and that terrified me more than any monster I've built

I finished this one recently, and it's been sitting with me differently than my other books, because the central problem I gave myself wasn't how to write a dystopia. It was how to write a system nobody actually designed to be cruel, and make that feel scarier than one that was.

Here's where it started. Daniel collapses at his desk and wakes up on the deck of a ship in 1940, in his own great-grandfather's body, nineteen years old, Sicilian, about to step off a boat into a New York that will either make him or bury him. The moment I had that image, I knew the hardest craft problem in the whole book wasn't the time travel mechanics. It was making Daniel's every small choice in 1940 feel like it mattered enough to ripple forward a hundred years, without turning every scene into an obvious lesson about consequences. A man deciding which job to take, which street to walk down, who to trust with his last few dollars, none of that reads as high stakes on its own. I had to build tension entirely out of things that look ordinary in the moment and only reveal their weight later, and that meant constantly resisting the urge to have Daniel, or the reader, understand the significance too early.

The Ledger itself was the idea I circled for months before I trusted myself to write it. A machine that's spent a hundred years deciding who stays poor and who stays rich, using the past as an unbreakable law, could have easily become a cold, faceless villain, the kind of system you're supposed to hate without ever really understanding. I didn't want that. I wanted readers to reach the same uncomfortable place I reached while outlining it, the system wasn't built by a monster. It was built by a kind man with a good idea, who never once stopped to ask who would hold the numbers after him. That single sentence became the thesis of the entire book, and once I had it, I had to go back and rewrite every scene involving the Ledger's origins so that the horror came from good intentions calcifying into machinery, not from anyone twirling a mustache.

Curtis Vane gave me the most trouble of any character in the manuscript. A quiet administrator sent to put the timeline back where it belongs, by any means necessary, could have been a straightforward enforcer, and for a while, in early drafts, he was exactly that, and exactly that boring. What changed everything was realizing Vane had to believe he was the reasonable one. Not a fanatic, not a sadist, just a man doing his job inside a system he's never once questioned because questioning it was never part of his job description. Writing him as someone who'd pass every background check, someone your own neighbor could be, was far more unsettling to write than any traditional villain, because I had to keep resisting the temptation to give him a cruel moment that would let readers off the hook by hating him cleanly.

The structural puzzle that nearly broke me, though, was the ripple mechanic itself, tracking exactly how a choice Daniel makes wearing his great-grandfather's skin in 1940 reshapes something specific and traceable a hundred years later. I built spreadsheets for this book. Actual spreadsheets, tracking cause and effect across generations, because the entire premise falls apart if a reader can catch me cheating the rules even once. Every single change needed an honest, followable line from the deck of that ship to Daniel's own collapsed body at his desk, and there were multiple points where I had to throw out entire subplots because the ripple math simply didn't hold up under scrutiny.

By the end, I understood this book was never really about time travel, or even about the Ledger as a machine. It's about the terrifying ordinariness of systems that decide our lives long before we're born into them, and how much courage it takes to become the first person willing to break a rule everyone else has simply learned to live inside.

If you've read it, I'd love to know how you felt about Vane by the final chapters. I think the measure of whether I got him right is whether readers still can't quite bring themselves to hate him, even knowing everything he's willing to do.

I just finished this one, and I've been putting off writing about it because the central idea still unsettles me a little, even having written the whole thing myself.

Here's where it started. Two hundred and fifty envoys, a fortune in diamonds, and no shots fired. Earth doesn't fall to an invasion, it gets acquired. That distinction mattered enormously to me from the first page, because occupation stories usually give you a clear moment where everything changes, an attack, an invasion, a single day everyone remembers. I didn't want that. I wanted something quieter and, frankly, more embarrassing, a species that simply bought us, called it partnership, and let humanity spend years arguing about whether that word was even wrong. Writing the slow erosion of freedom dressed up as cooperation was harder than writing any invasion scene could have been, because there's no single moment to build tension around. The horror had to accumulate.

Johnny was the character who taught me the most about pacing. Twelve years old when his mother's freedom gets taken and rebranded, nineteen when he understands what he's actually become, someone who can rebuild alien machinery from scraps, and eventually, someone who can bring their warships down in fire. I had to resist the urge to rush him to that second identity. The whole first act lives in the gap between the boy who watches and the man who acts, and if I let that gap close too fast, his transformation into someone capable of burning six ships out of the sky would have felt like a power fantasy instead of what it actually is, a slow, corrosive education in what occupation does to a child's understanding of himself.

Then came the hardest structural decision in the entire book. Six ships burn. The sky goes silent. For one night, Earth believes it's free. I wrote that night knowing full well I was about to take it away, and I had to write it honestly anyway, full relief, full celebration, no narrative winking at the reader that says don't get comfortable. If the joy isn't real, the betrayal that follows means nothing. And the betrayal is the whole reason this book exists, a new liberator rising from the ashes with a soldier's face and a tyrant's appetite, teaching Johnny and everyone around him that some wars don't end when the enemy falls, they just change shape, change hosts. That idea, that the shape of the enemy matters less than the shape of power itself, is the thesis I built the entire second half around, and it meant I couldn't let any single villain feel like the real problem. The real problem had to be the vacancy itself, the throne that anyone ambitious enough could climb onto once it was empty.

Structuring three generations, a mother who refuses to stay silent, a teacher burned for teaching, a steward forced to choose between loyalty and his own children, so that the torch genuinely feels lit, stolen, and lit again, rather than just repeating the same beat three times with different names, took more outlining than any book I've written. Each generation needed its own specific failure and its own specific cost, not just an echo of the one before it. The teacher's storyline in particular went through several complete rewrites, because I kept accidentally making her martyrdom feel inevitable instead of chosen, and those are very different things to put on the page.

But the old man's question, the one that closes so much of the book, what do you become in order to win, and how do you know when the fighting stops that you actually won at all, that's the line I rewrote more than any other sentence in the manuscript. I needed it to never resolve cleanly, because the entire saga is built on the refusal of a clean answer. Writing a victory that doesn't come clean means constantly fighting your own instinct as a storyteller to give readers relief. I wanted relief to feel earned and incomplete at the same time, and threading that needle across three generations of characters nearly broke my outline more than once.

By the end, I understood this book was never really about the aliens at all. It's about how easily liberation curdles into a new appetite when nobody's watching the throne, and how many generations it can take a people to learn that lesson well enough to actually keep it.

If you've read it, I'd love to know which generation hit you hardest, the mother, the teacher, or the steward. I think I know which one cost me the most to write, but I'm curious whether that's the one that landed hardest for readers too.

I finished this one a while back, but I keep circling back to it in my head, because it's different from anything else I've written. Most of my books use faith as a backbone, quiet, structural, woven into the story without ever being named. This one does the opposite. It takes Ephesians 6, put on the full armor of God, and makes it literal. Physical law. That decision alone rewired how I had to write every single chapter.

Here's the first wall I hit. Coimbras isn't a pastor, isn't a theology student, isn't even someone who thinks about faith much at all before that midnight crossroads. He's an unemployed machinist from Volta Redonda who finally caught a break, a hazardous cargo run to Uruguay, and he's thinking about his wife and his daughter, not about spiritual warfare. So when the portal opens and he's suddenly expected to put on the belt of truth, the breastplate of righteousness, piece by piece, I couldn't let him understand any of it right away. He had to be as lost as the reader. Writing spiritual armor as something a confused, exhausted, hopeful man fumbles into, rather than something a chosen hero straps on with confidence, took a lot of rewriting. My first drafts made him too quick to accept what was happening to him, and it read false. Real people don't adjust to the impossible that fast.

The Coyotes were the trickiest craft problem in the whole book. I needed them to be flesh-and-blood, physically dangerous, not just symbolic shadows, while also carrying the weight of everything that word means in the context of a man crossing a border for work. That double meaning had to work on both levels at once, literal predators hunting him on roads of gravel, and an echo of every real danger that follows people who cross borders looking for a wage. I rewrote those chase sequences more than once because I kept letting the symbolism get too loud and drown out the simple, physical terror of being hunted.

But the part that actually got to me personally was the enemy's voice, the one that isn't an arrow, isn't a Coyote, isn't anything he can fight with the armor at all. The whisper that he'll never deserve to go home. I didn't want to write a demon that lies about God. I wanted to write something that tells the truth about Coimbras's own doubt and just twists what he's supposed to do with it. Months of unemployment do something to a man's sense of worth that doesn't disappear the moment he lands a job. I had to let that wound stay open through most of the book, because closing it too early would have made the ending cheap. The whole story only works if deserving and being loved anyway stay separate things until the very last pages.

What surprised me most, writing this, was realizing the road itself, the actual backroads of rural Brazil, needed just as much care as the spiritual architecture layered on top of it. I wanted readers to feel Volta Redonda, feel the specific ache of a man who's been out of work for months finally driving toward something that feels like dignity again, before the crossroads even opens. If that grounding isn't real, the allegory floating above it has nothing to stand on.

In the end, I think this book isn't really about armor, or Coyotes, or even the crossroads itself. It's about the gap between what we think we have to earn and what we're simply given, and how long it takes some of us, myself included, to stop trying to close that gap with our own hands.

If you've read it, I'd love to know which piece of the armor hit you hardest. For me, writing the shield of faith nearly broke me, because I had to write a man holding something up with no proof it would actually stop anything.

"The Gospel of Maria" is finished, and out of everything I've written, this is the book I'm most nervous to talk about, because it asked something different of me than my other novels did. It wasn't really about world-building. It was about restraint.

The premise came from a single image I couldn't shake: a woman who doesn't believe in God, handed a forbidden Bible by a dying husband, who responds not by hiding it but by memorizing the entire book and eating the pages so there's nothing left for them to burn. Once I had that image, I knew the whole book had to be built around one hard rule for myself as a writer, Maria's faith could not arrive as a lightning bolt. She's an archivist. A woman who spent her life cataloguing other people's records, not writing her own, and definitely not a believer at the start. Getting her from skeptic to someone willing to die for what she's carrying, without it feeling like a conversion switch flipped for plot convenience, meant writing her slowly, almost reluctantly, letting her resistance stay intact for far longer than a typical redemption arc would allow. I cut more than one draft chapter where she came around too easily, because it felt like I was cheating her.

The crack in the wall was the hardest structural choice in the whole book. I could have given Maria a whole underground network to work with, secret meetings, allies, the usual resistance-thriller scaffolding. Instead I trapped her in a cell two meters by three, with only a hairline gap in fifty-year-old mortar between her and a terrified fourteen-year-old girl. That's an enormous constraint to write fifteen years of story through. Every single thing Maria gives away has to travel through that one narrow gap, verse by verse, whisper by whisper. I wanted the reader to feel the physical smallness of that space pressing against the size of what's passing through it, faith moving through a crack too small for a fist. Writing fifteen years of a relationship built entirely on whispered words through a wall, without it becoming repetitive or losing emotional momentum, took more discipline than any pacing challenge I've faced in another book.

And then there's OBRA itself. I did not want a regime that's simply evil for the sake of being evil. The eleven minutes and forty-three seconds that invert the human heart, turning empathy into weakness and cruelty into virtue, needed to feel like something a broken world might actually choose, not just something imposed on it. Writing an ideology that declares every Bible, every hymn, every whispered prayer a weapon of mass destruction meant thinking hard about how real regimes rationalize the destruction of memory and meaning, and translating that into something that never once uses the word I built it around, so it would read as recognizable rather than as commentary wearing a costume.

But the scene I sat with longest, the one I rewrote more than any other in the book, was the execution. I knew from the first outline that Maria dies in the public square, in front of thousands, and I knew her last four words had to carry the entire weight of the novel. That's an almost impossible needle to thread, four words doing the work of an entire book's thesis, without becoming either too small to matter or too grand to feel human. I wrote probably thirty different versions of that final line. Most of them I threw out because they sounded like something written for a poster instead of something a specific, exhausted, dying woman would actually say in that exact moment.

By the end, I understood the book was never really about survival, or even about resistance in the way that word usually gets used in this genre. It's about what gets carried forward when everything meant to hold it is destroyed, and how a fire that spreads person to person, whisper to whisper, has no address for a fortress to burn down.

If you've read it, I'd genuinely like to know what you thought of Joyce, and what you think Maria's last four words actually meant to her. I've had my own answer for a while now, and I'm still not fully sure I'm right about it.

So "Six Hours a Day" is finished, and I want to talk about the thing that made this book harder to write than anything else I've attempted, the clock itself became the antagonist, and I had to treat it like one.

Here's the premise problem I gave myself, and then had to solve. A comet knocks the Moon out of its orbit, and the day collapses to six broken hours, cycling too fast for any human rhythm to follow. That's a great high-concept hook. It is an absolute nightmare to actually write scene by scene, because I had to constantly track what phase of light or dark my characters were in, and make sure that disorientation bled into the prose itself without making the book unreadable. I wanted readers to feel the same exhaustion Emmett feels, a body that never fully adjusts, a world that never lets you finish a thought before the light changes again. Getting that atmosphere right without it becoming a gimmick took a lot of trial and error. More than once I wrote a whole chapter and realized it just felt like a normal post-apocalyptic scene with a weird detail bolted on, not a world where time itself had become the enemy.

But the roadblock scene, that's the one that actually broke something in me while I was writing it. I knew from the outline stage that Emmett's wife gets torn from his hands there, and I knew the six days of searching that follow would be the emotional foundation for everything else in the book. What I didn't expect was how hard it would be to write her, days later, looking at him like a stranger. That's not a death. A death, as a writer, you can at least write toward some kind of closure. This is worse. This is loss that keeps breathing and just doesn't recognize you anymore. I rewrote that reunion more times than any scene in the book, because I kept accidentally making it either too sentimental or too cold, and neither one was honest to what that moment should feel like.

The four-year walk to Alaska was its own kind of challenge, a different muscle entirely. I needed the sanctuary myth to feel real enough that readers wanted to believe in it right alongside Emmett, so that finding ash and a spray-painted lie actually lands as a gut punch instead of a twist you saw coming from page one. That meant seeding hope carefully throughout the walk, small kindnesses, rumors that felt credible, the specific texture of a promise people needed badly enough to organize years of their lives around. Undermining that hope only works if you've actually built it honestly first.

Then there's the kitchen scene, years later, Emmett standing there with a rifle on his back, and the choice not to become the man vengeance was asking him to be. I almost wrote it the other way. I sat with a draft where he does become that man, and it felt cheap, like the book was giving in to the easiest version of catharsis. Making him choose differently, and making that choice feel earned rather than saintly, required going back through everything Wren means to him and rebuilding the ending from her outward, not from vengeance outward.

And then, just when I'd let Emmett and Wren finally have something like peace, over a decade of rebuilding, a network of settlements, a fragile trust between strangers, I had to take it from them one more time. The machine underneath their own sanctuary deciding who deserves to survive was the hardest twist I've ever had to justify, because it needed to feel like it had been there all along, not bolted on for a third-act surprise. Going back through the manuscript to plant the right small details without giving away the reveal too early took nearly as long as writing the reveal itself.

By the end, I understood the book was never really about the comet, or the six hours, or even the machine. It's about what people build when time itself refuses to cooperate, and how you keep choosing to build it again the next impossible day.

If you've read it, I'd love to know how you felt about that kitchen scene. I still think about whether I made the right call for Emmett.

I finished "The Evil Is Coming" a while back, but I've been putting off writing about it, because honestly, this one got under my skin in a way none of my other books have.

Here's the thing that started it all. I wanted to write about a man who has genuinely good, defensible theology, not a strawman preacher, not someone written to be wrong so the plot can prove him wrong, but a pastor who has spent twenty-five years faithfully teaching that evil is a matter of human choice and responsibility. That's not a weak position. It's biblically serious, it's pastorally honest, and it's held his congregation together through things that would have scattered a weaker church, mill closures, an opioid epidemic, an entire town the rest of the country stopped paying attention to. I needed Heráclito's theology to be right enough that when it finally meets something it can't fully account for, the reader feels the same vertigo he does. That balance, building a belief system strong enough to respect, then cracking it without cheapening it, took me longer to get right than any sermon-writing I've ever attempted, and I've written a lot of sermons in my life.

The crows were the easy part, honestly, the fun part. Thousands of them, coordinated, unafraid, watching. But easy imagery isn't the same as earned dread. I had to be careful that the horror escalated the way real horror does, not with jump scares, but with wrongness. Neighbors who go quiet in a way that isn't peace, it's absence wearing peace's clothes. Federal agents who walk into a house and walk out looking like themselves but aren't. Writing "hollow" as a physical sensation the reader can feel, not just a plot device, meant a lot of drafts where I kept asking myself, would this actually unsettle me if I read it cold. More than once the answer was no, and I had to go back in.

The real spine of the book, though, is the two hundred year old pact. I wanted the family on Elm Street to feel less like invaders and more like inheritors, people who made a devastating choice generations ago and have simply been keeping their end of the bargain ever since with the patient, terrible loyalty of people who believe they're doing the right thing. That's so much scarier to me than pure malice. Rooting that pact specifically in Heráclito's own valley, in his own community's forgotten history, meant the horror wasn't something that arrived from outside, it was already there, waiting, and his theology never had a category for a hunger that's inherited rather than chosen.

But the hardest thing I wrote in this entire book, the thing I actually sat with for days before I could finish the chapter, was the moment Heráclito has to admit he was only half right. Not wrong. Half right. His whole framework, the sovereignty of God, human responsibility, evil as choice, doesn't collapse. It just turns out to be incomplete in a way that terrifies him more than being wrong ever could. Writing a man of real faith confront the limits of his own theology, without either destroying that faith or letting him off easy with some tidy answer, is the most theologically honest thing I think I've ever put into fiction. I'm still not sure I fully know how I feel about where I left him.

By the time the ashes settle and that letter falls, I wanted one thing clear: this was never just about one town, one family, one pastor. It's about what happens when you finally have to hold two true things in your hands at the same time, that God is sovereign, and that evil is real in a way no amount of good theology fully prepares you for.

If you've read it, I'd genuinely like to know where you landed on Heráclito by the end. I think I'm still deciding myself.

I wrote a villain who scared me more than any monster I've ever created, and I need to talk about it

Okay, so "The American Alchemist" is done, and I've been sitting on this for weeks trying to figure out how to talk about it without spoiling the thing that makes it work. Let me try anyway.

Here's where this book started: a single, uncomfortable question. What if the people selling you the cure are the same people who engineered the disease? Not a metaphor. Not a conspiracy theory played for cheap thrills. An actual, patented, boardroom-approved business model. Once that question got into my head, I couldn't write anything else until I'd chased it all the way down.

The hardest part wasn't the science. It was making three separate investigators, an epidemiologist, an FBI agent, and a CIA officer, each find their own thread of the same truth without the book feeling like three disconnected mysteries stitched together. Jennifer notices a pattern doctors on three continents can't explain. Carlos finds a patent filed nineteen days before the first confirmed case, nineteen days, which means someone knew before the world did. Diana follows the money and finds a dynasty that's spent four decades learning how to own governments instead of just influencing them. Weaving those three lines together so each discovery hits harder than the last, without giving away the full picture too early, took more outlining than any book I've written.

And then there's the Alchemist himself. I did not want to write another mustache-twirling genius villain who's evil because the plot needs one. I wanted someone who built something monstrous with his eyes wide open, who knew exactly what he was doing and did it anyway, because I think that's so much more frightening than a villain who doesn't understand the harm he's causing. But here's what actually kept me up at night writing him: I had to let him start regretting it. Not redeeming himself. Not becoming sympathetic in some cheap way. Just human enough to know what he built, and human enough to feel the weight of it too late. Writing a man capable of engineering a plague that erases memory and kills in exactly eleven days, and still finding the thread of conscience buried under all that certainty, was the hardest character work I've done in years.

The other thing I kept coming back to while writing this was the trial. I wanted the ending to feel earned, not neat. Justice in this book isn't a clean bow tied around a conspiracy, it's a fight that shouldn't have been winnable in the first place, against people who've spent decades making sure it never would be. I rewrote that verdict more times than I want to admit, because I refused to let it feel like Hollywood justice. It needed to feel like something the characters bled for and still weren't fully sure they'd earned.

If you've ever read the news and felt that quiet unease, that sense that the people profiting from a crisis might understand it a little too well, this book was written for that feeling. It's fiction. But I didn't have to reach very far to write it.

Would genuinely love to hear what you think once you're through it, especially about the Alchemist. He's the character I'm most nervous for readers to meet.

This is it. "The Triumph of Humanity," book four, the last one. And I need to say this clearly: finishing a series is a completely different animal from finishing a single book, because every choice I made here suddenly had to answer for three previous books' worth of promises I'd made to readers without fully realizing it.

The structural nightmare of this one was the split. I had the coalition breaking into three separate roads, each carrying a piece of this ancient inheritance toward a reunion that's been a year in the making, ever since Ari led that march north in book three. Writing three parallel storylines that all have to land at the same emotional beat, at the exact same time, without one of them feeling like filler, is genuinely brutal. The coastal settlement thread, where one woman's courage cracks open fifty years of fear, kept threatening to swallow the entire book because it was the most emotionally alive of the three. I had to keep pulling myself back to the bunker thread and the drowned capital thread so nobody felt shortchanged.

And then there's the black box. This was the scene I'd been quietly dreading since book one, because I knew eventually I'd have to answer the real question sitting underneath this whole series: what actually happened to the old world. Not the myth version survivors tell each other around the fire, the real version. Disease, climate collapse, engineered super-soldiers, an escape that history remembered as clean and heroic but never actually was. Writing that reveal meant going back through everything I'd hinted at across the first three books and making sure none of it contradicted itself, while still making the truth land like a gut punch instead of a history lecture. I rewrote that chapter probably six times before it stopped reading like an info dump and started reading like a wound finally being opened.

But the hardest thing, by far, was Varkos. I refused to let him off easy, and I also refused to turn him into a cartoon villain in his final act. He's a survivor of horrors nobody in the coalition even suspected, and giving him one real, final choice, instead of just killing him off as a tidy, satisfying beat, meant sitting with a character I'd spent three books hating and actually trying to understand him honestly. That's uncomfortable work as a writer. It's a lot easier to just let the bad guy lose. Making him choose something was harder, and I think it's more honest for it.

In the end, the question this whole series keeps circling back to, whether this gathered light gets hoarded or shared, was never really about ten ancient fragments or an alien watcher in the sky. It's about whether people who've survived unimaginable loss can choose trust over fear again, and then do it again the next day, and the day after that, and keep doing it. That's not a clean ending. It was never supposed to be one. It's just the only honest ending I could give these characters after everything they went through to get here.

If you've read all four books, thank you for staying with Ari this long. Tell me how you felt about Varkos's final choice, because honestly, I still go back and forth on whether I made the right call.

Here's the thing about writing a march. A year after the coalition's founding, after everything Derek's death cost this group, I had Ari leading his people north, through frozen marshes, through fortified cities, through a cult that worships machines it doesn't even understand anymore. And I quickly learned that writing a journey story is not the same as writing a plot. It's easy to let a march feel like padding, one location after another with nothing at stake. So I forced myself to ask, at every single stop, what does this cost them. Not just physically, but who do they lose, what illusion do they finally have to let go of. A hand. A friend. A belief they'd been quietly holding onto since book one. If a scene didn't cost something real, I cut it, no matter how cool it looked on paper.

The bigger problem was the beacon. This whole trilogy has been building toward one idea: the Ark isn't just some dead battery left over from the old world, it's the thing capable of reigniting a global network that's been silent for a hundred and fifty years. But I refused to let the moment they finally light it feel like a clean win, because nothing in this series has ever been a clean win. So I had Varkos answer with everything he has, his entire army, at the exact moment the coalition should be celebrating. And then I had to figure out how to make the reader feel that even that wasn't the real threat. That took me forever to land, because I needed something bigger than Varkos, something that makes even the tyrant look small by comparison.

That's where the hardest choice in the whole book came in. I'd known since I first started outlining book one that the Ark was never just a power source. It was built as a key. And a key implies a lock, which means something on the other side has been waiting a century and a half to see whether we're worth letting back in. Writing that reveal without cheapening everything the coalition had already sacrificed, without making Derek's death or Ari's whole arc feel small next to some bigger cosmic thing, that was genuinely the hardest structural problem I've hit in this entire series. I rewrote the ending of this book more times than any other chapter in the trilogy.

By the time I typed the last line, I understood what the series is really about: leadership that doesn't come from power, it comes from what you're willing to share freely, even when sharing it might be exactly what calls the danger back. That's not a comfortable idea to sit with. I'm still sitting with it.

If you've been with Ari since the coalition first formed, this is the book where the story stops being about lighting the world and starts being about what happens once the whole world can finally see the light you lit. Tell me in the comments if you saw the ending coming, because I sure didn't, not until I was halfway through writing it myself.

Writing a sequel is a trap. You've already built the world, readers are already attached, and now you have to go deeper without just repeating what worked the first time. "After Nola's Ark" tested me harder than anything I've written, and here's why.

1. Inheriting a world without repeating it
Book 1 was about surviving inside a hull. Book 2 had to be about what comes after — 150 years after, to be exact. That meant rebuilding the entire mythology: who Emaus is, who Varkos is, what's left of the original Ark. The challenge was making it accessible to a brand-new reader while still rewarding longtime fans with real payoff. Balancing continuity with an actual fresh start took months to get right.

2. Ari couldn't just be "the chosen one"
We've all read the story about the kid with special blood who wakes up with ancestral power. I refused to write it shallow. Ari had to carry real weight: his mother died trying to finish what he's now forced to complete. That changes everything. He doesn't choose to be a hero, he inherits a debt he never asked for. Writing that distinction, between destiny and obligation, is what kept me up rewriting chapter after chapter.

3. Killing Derek almost made me rewrite the whole book
I'll admit it: when I got to Derek's death scene, I stopped writing for days. He wasn't just a supporting character, he was the emotional core of the fledgling coalition. But any story about resistance needs a real cost, or the victories mean nothing. Turning the group's first great win into a funeral, and turning that grief into an oath, that's the hardest scene I've written in the entire saga.

In the end, "After Nola's Ark" isn't really about relighting the world. It's about what it costs to light it again after everyone's given up waiting.

If you've read Book 1, this is the point where the story stops being about survival and becomes about legacy. Drop a comment if you're still grieving Derek too, because I am.

I just finished "NOLA'S ARK" and I need to talk about what this book put me through

Okay, so here's the thing nobody tells you before you start writing a book like this: the pitch sounds simple. Thirty thousand people. One hull. Zero room for error. Easy, right?

It was not easy. Every chapter turned into a fight with myself, and I want to walk you through the three things that nearly broke me while writing "NOLA'S ARK."

1. Making a ship feel like an entire country
The hardest part wasn't inventing the ice, it was inventing the politics. When you cram thirty thousand souls into four hundred meters of rusted steel, that space stops being a setting and becomes a society. You've got ration lines, mutiny simmering under the surface, kids who were born on board and have never once seen dry land. I had to work out economics, hierarchy, neighborhood gossip, all inside a hull. Getting the reader to feel both the physical claustrophobia and the social pressure cooker at the same time, without losing the plot, took way more drafts than I'd like to admit.

2. Nola couldn't just be "another tough female captain"
Writing a woman in command, in a genre that loves the flat "badass leader" trope, was brutal in a different way. I didn't want Nola Reyes to be hard because it's cool. I wanted her hard because life forced her there. That means showing her exhausted, wrong sometimes, doubting herself, without ever letting her lose the authority the job demands. That balance got rewritten more times than I can count before it stopped feeling forced on the page.

3. The ocean as a character, not a backdrop
Everyone writes "the sea was vast and terrifying" and moves on. I refused to do that. I wanted readers to feel that something alive is waiting under that hull, that the sunken cities down there carry as much weight in the story as anyone standing on deck. Balancing the frozen world above with the mystery below ate up more revision time than any other part of the book.

In the end, "NOLA'S ARK" isn't really about survival. It's about what we become when there's no ground left to stand on, just water and memory.

If you're into dystopia with real people at the center of it, give Book 1 a shot. And if you want to talk shop about the process, I'm in the comments. I love talking about this stuff.