Show Your Work Saturday! · AI Pro Writers Studio

Show Your Work Saturday!

What has everyone been up to this week? Post a response below:

*****

This is unfortunately yet another one of my long wordy posts

If you've kept up with some of the postings of late I've been spending a lot of time with genre's and and the new BookWeaver app. Below is a sample of a Chapter from a BookWeaver book I'm about to publish. This is the first one I have brought in to WordCrafter.Pro to run through the editorial room and finish. It is unfortunately not a favorite story, but the writing is very good.

This was a test of multiple things. This was a budget model, Gemini 2.5 Flash, which doesn't write bad prose, but does need a good outline and beats to stay consistent. Enter the story threading engine for this, that does some interesting tings under the hood that I need to add in to the editorial team or a light chapter by chapter pass in the Writer's room. Because the apps are FUNDAMENTALLY different in operation there are a couple jumps to make. There is NO N8N in use here at all. I do not like its outputs and how slow it is. 22K Words in half an hour from a basic premise. I read through the Story Bible and Outline created and did some light edits here and let it roll. I ran the consistency checker on it and dis some more editing a couple regenerations.

Any guess's as to the cost to create this? 25K Words, 9 Covers, Editing, and export to epub. Answer is at the bottom of this post.

Okay, so I did cheat on this one. Remember I said I took this to WCP for final editing? I do not yet have an accounting of how much I spent there in the editorial room, so that function has been added as well. I spent several hours last night in the editorial room in WCP with this one and cleaned it up a bit more and followed their suggestions for most of the fixes.

And also learned something new and interesting I will document in a video later today. In the Editorial skillroom I let Oracle do her cold read and let the editorial team do their first pass analysis. I answered their questions and asked them to "show me their fixes" and reciedved a very long chapter by chapter set of repairs to copy/replace or do by hand. This is supposed to be a mostly automated book right? My response to them after this was this "make the changes above to the actual chapter context chapter by chapter, stop at the end of each chapter so I can save them" And it did just this for the 4 chapters that need major fixes. I saved them to the binder, renamed them properly, moved the old versions to a folder named "old" and read through it.

The first chapter excerpt is below. Would you keep reading it? I think total I have maybe 4 hours invested in this one

*****

Chapter 1: The Weight of Expectation

The relentless hum of the server room was a dull counterpoint to the vibrant music Julie’s mind was playing, a stark reminder of the chasm between her two lives. Here, under the fluorescent glare of Quantum Analytics, every surface was beige or gray, every sound a muted echo of industry. The air, conditioned to a sterile coolness, did little to stir anything beyond a lingering sense of quiet purpose. Julie sat hunched over her triple-monitor setup, lines of Python sprawling across one screen, SQL queries on another, and a perpetually open ticket system on the third. Her fingers, usually so agile and expressive, now moved with a deliberate, almost mechanical precision across the keyboard, each click a tiny punctuation mark in the endless sentence of her work.

Today’s task: optimize the data retrieval algorithm for the Q3 financial forecast. A necessary evil, she told herself, as a particularly convoluted nested loop threatened to swallow her focus whole. Her brow furrowed, a tiny crease forming between her eyebrows, but her expression remained otherwise placid. Outwardly, Julie Vance, Senior Software Engineer, was a picture of calm competence. Inside, a different kind of rhythm pulsed, a syncopated beat yearning for release. She could almost hear the Allegro con brio of Beethoven’s Fifth Symphony, a defiant, insistent melody that had been trying to break through the drone all morning.

A shadow fell across her desk. Julie did not look up immediately. Mark. She recognized the scent of his cologne—overly sharp, faintly citrus—before his voice chimed in.

“Still wrestling with that beast, Vance?” Mark leaned against the edge of her cubicle, a mug of steaming coffee clutched in one hand. His shirt, crisp and blue, seemed to hum with an entirely unearned confidence.

Julie finally lifted her gaze. “Almost done, Mark. I’ve optimized the algorithm to reduce latency by nearly 15%.” Her voice, though soft, carried the quiet authority of someone who knew her numbers. She gestured to a line of code on her screen, a tight, elegant solution she was disproportionately proud of.

Mark peered at the screen, a vague nod accompanying his half-comprehending glance. “Fifteen percent, eh? Impressive. Remember that little suggestion I gave you last week about refactoring the data structures? Glad to see you took it to heart.” He offered a wide, toothy grin that never quite reached his eyes.

Julie’s jaw tightened almost imperceptibly. The “little suggestion” had been a throwaway comment about a generic programming principle she had already considered and dismissed as inefficient for this specific problem. She had spent the last two days meticulously re-architecting the entire backend processing, hours blurring into a single-minded pursuit of efficiency. She had even stayed late last night, fueled by lukewarm instant coffee and the stubborn refusal to be beaten by a database bottleneck.

“Yes, Mark,” she said, her tone level, devoid of any inflection that might betray her irritation. “Valuable insight, as always.” She turned her attention back to the monitor, effectively dismissing him. The Beethoven faded, replaced by the grating dissonance of her own unexpressed frustration.

Mark, oblivious or simply uncaring, lingered for another moment, taking a noisy sip of his coffee. “Right. Well, keep up the good work. We’re all counting on you to deliver this one on time.” He patted the cubicle wall, a gesture of camaraderie that felt more like a brand on her skin, then ambled off, leaving behind a faint trail of his cologne and a lingering film of resentment.

Julie took a deep breath, letting it out slowly. She forced her shoulders to relax, the tension a familiar, unwelcome guest. The weight of expectation, not just from Mark, but from the entire project, pressed down on her. Here, her value was measured in lines of code, in percentages of improvement, in the cold, hard logic of data. It was a life of silent compromises, where her true self, the self that vibrated with music and movement, remained carefully hidden beneath a façade of corporate efficiency.

$0.53 using Gemini Flash for 22K words in 30 minutes

I accidentally used the Gemma 4 31B (Free) model for the editorial room. I really meant to use Gemini Flash 2.5 throughout, but this means....

$0.53 for a book that is not a terrible read.

3 comments

Show Your Work Saturday!