TL Mercer

I write books between shifts. Not metaphorically — literally. The trilogy got written in the cracks: early mornings, lunch breaks, the hour before sleep when the brain is tired enough to stop second-guessing. If you’re building a writing career on top of a day job, this one’s for you.

Stop waiting for the big block of time

The biggest lie day-job writers tell themselves is “I’ll write when I have a free weekend.” The free weekend never comes. There’s always a shift, a bill, a car breaking down, life doing what life does. The writers who finish books on a day-job schedule are the ones who stopped waiting and started stealing: forty-five minutes before work, thirty minutes at lunch, an hour after the kids are down.

A page a day is a book a year. That’s not motivational-poster math, it’s just arithmetic. Small sessions compound. Protect them like they’re shifts — because they are. You wouldn’t no-show your job. Don’t no-show your book.

Energy management beats time management

You don’t have a time problem, you have a depletion problem. After eight hours on your feet, your brain is soup. So stop trying to write your best prose at 11 PM. Match the task to the energy: low-energy windows are for editing, outlining, dictating notes, fixing continuity. Save the precious high-energy hour — whenever yours is — for new words.

Mine is early morning, before the world starts demanding things. Yours might be different. Find it, guard it, and don’t spend it on social media.

Tell people. Seriously.

For years I treated writing like a secret hobby, something slightly embarrassing I’d mention with a laugh. Mistake. When I started telling people — coworkers, family, the guy at the gas station — two things happened. First, some of them became readers. Second, and more important, saying “I’m an author” out loud made it real. It stopped being a thing I did and started being a thing I am. Identity is fuel. Use it.

Rest is part of the schedule

Burnout doesn’t announce itself; it just quietly makes the blank page feel like an enemy. If you’re working full-time and writing, you need actual rest built into the week — not “rest” where you feel guilty, but scheduled, guilt-free time off. One day a week where you don’t open the manuscript. Your subconscious will keep working; that’s its job. Let it.

The goal is a career, not a sprint. Sprinters with day jobs end up injured.

The job funds the dream — respect both

It’s easy to resent the day job for stealing writing hours. Flip it: the job is your patron. It pays the rent while you build the thing that might one day pay the rent instead. Every shift is buying your future catalog. That’s not cope, it’s strategy. Plenty of full-time authors started exactly where you are, writing between shifts and wondering if it was delusional.

It wasn’t delusional. It was the plan.

Written between shifts, like everything else: the I Was Married to a Monster Girl trilogy.

Nobody remembers the choreography. Ask a reader about their favorite fight scene and they won’t describe footwork — they’ll describe the moment the hero realized the sword was stuck, or the punch they didn’t see coming, or the split second of quiet before everything went wrong. Fight scenes aren’t about fighting. They’re about fear, and stakes, and consequences.

I write action-heavy fantasy, and here’s what I’ve learned about making violence on the page hit like it matters.

Choreography is the least important part

New writers describe fights like sports commentary: he swung, she blocked, he swung again. It’s technically accurate and completely boring. Readers can’t visualize twelve consecutive moves, and they stop trying around move four. What they can feel is intent. He swung to kill. She blocked because there was nowhere to run.

Describe the goal of each exchange, not the geometry. “He drove her toward the cliff edge” beats three paragraphs of blade angles. Give the reader the shape of the fight — who’s winning, who’s desperate, what changes — and let their imagination fill in the swings.

Short sentences hit harder

Read your fight scene out loud. If it sounds like a lecture, it’s too long. Action runs on short sentences and fragments. Quick beats. Like this. Long, rolling sentences with multiple clauses are for aftermath — for the ringing ears and the shaking hands when it’s over.

Vary the rhythm deliberately. Fast and choppy during the exchange, then one long breathless sentence when something goes wrong, then short again. You’re scoring music, not transcribing it.

Injury has to cost something

The fastest way to drain tension from a fight is consequence-free violence. If your hero takes a sword through the shoulder and fights at full strength two pages later, the reader learns that nothing in your fights matters. Pain should change what the character can do. A wounded leg means no running. A broken hand means the sword goes to the other one, badly.

This is doubly true in LitRPG, where health bars tempt you to treat damage as arithmetic. A health potion that erases everything erases the stakes too. Make healing cost time, or resources, or leave something behind — a scar, a limp, a hesitation next time.

The fight is never about the fight

The best fight scenes are arguments with weapons. The hero isn’t just trying to win; they’re trying to prove something, protect someone, or avoid becoming the thing they’re fighting. When the emotional question is clear — will he abandon his code to survive? — every blow lands harder because it’s asking that question again.

Before you write the scene, finish this sentence: “This fight is really about ___.” If you can’t, the scene is just noise. Cut it or find the argument.

End it ugly

Real fights don’t end with a cool one-liner and a sheathed sword. They end with someone gasping in the dirt, or winning by accident, or realizing the cost was too high. Let your endings be messy. The hero who wins clean learns nothing, and the reader feels nothing.

Violence in fiction is a promise: this mattered enough to bleed for. Keep that promise, and your readers will flinch, gasp, and turn the page.

Plenty of fights where it hurts in my trilogy — I Was Married to a Monster Girl. The action’s crunchy and the consequences stick.

Let’s be honest: most writers didn’t get into this business to dance on camera. We got into it to sit alone in a room and make things up. Then someone explained that “discoverability” means posting three times a day on platforms designed by people half our age, and suddenly the dream involves learning trending audio.

I hate social media. I’m doing it anyway. Here’s how to survive it without losing your mind or your dignity.

Pick one platform and ignore the guilt

You do not need to be everywhere. The gurus will tell you to repurpose everything across seven platforms, and the gurus sell courses, not books. Pick the one platform where your readers actually hang out — for genre fiction right now, that’s TikTok and Instagram Reels — and let the rest go. One platform done consistently beats five platforms done anxiously.

I chose short video because my books are visual and ridiculous, and a ten-second clip of a dragon sells the vibe faster than any ad copy. Your mileage will vary. The principle doesn’t: go where the readers are, not where the experts tell you to be.

Document, don’t perform

The best advice I ever got about content: you don’t need to perform, you just need to document. Nobody wants to see you doing a trending dance. They do want to see the book cover reveal, the typo that made it to print, the moment you realize chapter twelve makes no sense. Your writing life is already content. You just have to point a camera at it occasionally.

Talk about your books like you’d talk about them to a friend at a bar. That’s the whole trick. Enthusiasm is contagious; polish is optional.

Batch it or it’ll eat you

The algorithm wants consistency, and consistency will destroy you if you try to create daily from scratch. So don’t. Once a week, spend an hour making five or six short videos. Post them across the week. Done. You just bought yourself six days of not thinking about it.

I make mine in batches on weekends — a few AI-generated teaser clips, a couple of talking-head rants about writing, whatever I’ve got. Then I schedule or queue them and go back to the actual job, which is writing books.

Engagement is a chore; treat it like one

Reply to comments. Not because the algorithm demands tribute (it does), but because a reader who comments on your video is a reader who might buy your book. Fifteen minutes a day, morning coffee, reply to everything. Then close the app. The infinite scroll is engineered to keep you there; your willpower is not engineered at all. Set the boundary.

Remember what it’s for

Social media is a tool, not a career. The goal was never followers — it’s readers. If your follower count is climbing but nobody’s clicking the link in your bio, something’s wrong with the funnel, not the content. Every post should, directly or indirectly, point at the books. That’s the job.

I still hate social media. But my books have readers I never would have found otherwise, and that’s the trade. An hour a week of mild embarrassment for a career. I’ll take it.

The books I’m awkwardly promoting: the complete I Was Married to a Monster Girl trilogy. Link in bio, as the kids say.

Preorders sound like free money: readers buy before release, sales stack up for launch day, and you get a marketing runway. So why do so many experienced indie authors skip them? Because preorders are a trade — and like every trade, you should know what you’re giving up.

The case for preorders

The big advantage is the runway. A preorder listing gives you a live product page weeks or months before release — a URL to put in the back of your previous book, in your newsletter, on social media. Every “also by this author” page in your catalog can point at the next book before it exists. For series authors, that’s powerful: book two’s back matter sells book three on preorder, and readers who would’ve forgotten by launch day are already committed.

Preorders also concentrate your launch. All those early sales hit on release day, which can spike your rankings and visibility in a way that dribbles of day-one sales don’t. And psychologically, a preorder number ticking up is excellent motivation to finish the manuscript.

The case against

Now the costs. First: deadlines with teeth. Amazon requires your final file ten days before release, and if you miss it, they can block you from preorders for a year. A year! That’s not a slap on the wrist; that’s a strategic amputation. So preorders convert a soft personal deadline into a hard platform deadline, and life doesn’t care about your launch calendar.

Second: you can’t test anything. No blurb tweaks based on real conversion data, no cover swap if it’s not clicking, no price experiments. The page is locked while you’re flying blind. Authors who iterate aggressively — and iteration is an indie superpower — find this maddening.

Third: review risk. Preorder readers are your most excited fans, which is lovely until the book doesn’t match the hype they built in their heads for two months. A book released to warm anticipation gets judged harder than one discovered by accident. It’s not fair, but it’s real.

When to use them (and when to skip)

Use preorders when: the book is essentially done (edited, not “I’ll finish it during the preorder”), it’s part of an existing series with an audience waiting, and you want that catalog cross-promotion. A 30-day preorder on a finished series installment is nearly pure upside.

Skip them when: the manuscript isn’t finished, it’s your first book (you have no audience to preorder from, and the runway is a runway to nowhere), or you want launch-week flexibility. There’s no shame in the surprise release — “my new book is out today” is a perfectly good marketing message.

One middle path: the short preorder. List it two weeks out with the final file already uploaded. You get the product page, the back-matter link, and the launch-day stacking, with almost none of the deadline risk. Most of the benefit, fraction of the danger.

Preorders aren’t good or bad. They’re leverage — and leverage only helps if you’re standing on solid ground.

Want to see the result of getting the release strategy right? Check out my books — launched the indie way, on purpose.

Rapid release is the indie publishing strategy everyone has an opinion about and almost nobody explains straight. So here’s the straight version: what it is, who it works for, and when “fast” becomes “too fast.”

What it actually is

Rapid release means publishing books in the same series close together — typically every 30 to 90 days, with the whole series out inside a year. The logic is simple and real: retailers’ algorithms favor new releases, and a new release boosts visibility for every book in the series. Book three’s launch lifts books one and two. Readers who binge the series in a weekend buy all of them at once.

The math is honest too. Say a standalone sells steadily. Now imagine three books in a series, each launch pushing the earlier ones, each earlier book funneling readers forward. A rapid-released trilogy can earn multiples of what the same three books would earn released a year apart — because the momentum compounds instead of decaying.

That’s the pitch. Now the fine print.

Who it actually works for

Rapid release works for authors who write fast, write in series, and write in genres where readers devour books quickly — romance, LitRPG, cozy mystery, thriller. It works for plotters who can draft cleanly and revise quickly. It works for authors with a backlog or a co-writer. It does not work by magic; it works because the author can sustain the pace without the quality collapsing.

It does not work for everyone, and the genre matters enormously. Literary fiction readers will wait three years. LitRPG readers will riot after three months. Know your audience’s metabolism.

When fast becomes too fast

Here’s where the horror stories come from. Rapid release turns toxic when the schedule starts dictating the quality — when you’re publishing the draft instead of the book. Readers forgive a lot, but they don’t forgive feeling rushed. One sloppy installment can poison a whole series, and rebuilding that trust takes longer than the time you “saved.”

The other cost is the human one. Writing a novel every 60 days for a year is a marathon at sprint pace. Burnout is real, it’s common, and it doesn’t announce itself — it just shows up one morning as an inability to open the document. The authors who rapid-release sustainably build in rest: they bank manuscripts ahead, they take weeks off between series, they treat recovery as part of the schedule.

The honest middle ground

You don’t have to choose between “a book every month” and “a book every two years.” Plenty of successful indie authors release two to three books a year in the same series and get most of the compounding benefit with none of the burnout. Consistency beats speed. A reader who knows your next book lands every four months is a reader who sticks around.

Rapid release is a tool, not a religion. Use it if your process and your genre support it. Skip it if they don’t. The only wrong pace is the one that breaks you or the books.

Curious what a consistently-released series looks like? Check out my books — the trilogy that taught me everything about momentum.

LitRPG lives or dies on its crunch — the stat screens, skill descriptions, level-ups, and loot tables that make the genre the genre. But there’s a trap every new LitRPG author falls into: mistaking a wall of numbers for excitement. A full-page character sheet isn’t immersive. It’s homework.

I write monster-girl harem fantasy with heavy game mechanics, and here’s what I’ve learned about making the numbers sing instead of snore.

Only show what changed

This is the golden rule. Readers do not need the full character sheet every time it appears. They need the delta — what changed, and why it matters. Level up? Show the new level, the points gained, the one skill that evolved. Skip the eighteen stats that stayed identical. Think of the stat screen like dialogue: it should only appear when it’s saying something new.

A trick that works: show the full sheet once early (establishes the baseline), then show partial screens after that. Your readers will build the full picture in their heads, and they’ll feel smart for doing it.

Stat screens are rewards, not interruptions

The best game mechanics land right after effort. The character survives the boss fight, the screen pops, and the reader gets the dopamine hit alongside the hero. That’s the loop that keeps pages turning. What kills momentum is the reverse — a stat screen that pauses the action to deliver exposition. If the building is on fire, nobody wants to read about the +2 to Carpentry.

Time your screens like punchlines: at the end of scenes, after victories, in the quiet beat before the next problem. Never mid-chase.

Tie every mechanic to the story

A skill is only interesting if the reader understands what it costs or enables. “Fireball II” is a line of text. “Fireball II — the spell that can finally hurt the thing hunting his wives” is a plot development. Every level, skill, and item should connect to something the character wants or fears. When a reader sees a new ability and immediately thinks “oh, that’s how he survives the dungeon,” you’ve done it right.

This is also why loot works: not because the sword has +15 damage, but because the sword changes what the character can attempt. Numbers describe. Consequences compel.

Be ruthlessly consistent, then ruthlessly brief

Nothing breaks trust faster than mechanics that contradict themselves. If a skill costs 50 mana in chapter three, it costs 50 mana in chapter thirty. Keep a bible — a simple document with every skill, stat, and item — and update it as you write. Your most obsessive readers will catch errors, and they will tell everyone.

And when in doubt, cut. The stat screen you delete is never the one readers miss. The one you trim to five lines is the one they’ll quote.

Game mechanics are seasoning, not the meal. Use them to make victories sweeter and choices harder, and your readers will never skim a screen again.

Want to see stat screens done the fun way? Check out my books — the numbers are crunchy and the stakes are real.

Let’s start with the uncomfortable truth: you need reviews, you can’t buy them (legally, anyway), and the first bad one will feel like a personal injury. Every indie author goes through this. Here’s how to handle it without losing your mind.

How reviews actually happen

Nobody reviews a book unprompted at scale. The authors swimming in reviews aren’t luckier than you — they’re more deliberate. The mechanics are simple:

First, build an ARC team. Start small. Ten reliable readers who get the book two weeks early and agree to leave an honest review on launch week. Ten reviews on day one changes everything about how a book looks to a cold browser. You find these people in genre Facebook groups, on your newsletter, or in reader communities — offer the free book, be clear about the ask, and never require a positive review. Honest only.

Second, ask inside the book. A short note at the end — “If you enjoyed this, a review helps more than you know” — converts readers who finished (and finishers are your best reviewers) at a small but real rate. Keep it short and genuine. Nobody finishes a book and thinks “ah yes, finally, a three-paragraph guilt trip.”

Third, your newsletter. Every release announcement should include a gentle review ask. Your subscribers are your warmest audience. Warm audiences review.

That’s it. There’s no secret hack. It’s volume of asks, pointed at the right readers, sustained across every book.

What to do with 1-star reviews

You will get them. A book with only five-star reviews looks suspicious, and readers know it. Somewhere around fifty reviews, you’ll get the one that says your book is an abomination and the reviewer regrets the hours of their life. Here’s the protocol:

Do not respond. Ever. Amazon lets you respond to reviews; authors doing it is always a disaster. No exceptions. Even a polite correction reads as defensive.

Do not argue in your head at 2 AM. This is the rule I break most. You’ll read the review, compose the devastating rebuttal in the shower, and accomplish nothing except ruined sleep. Read reviews during business hours, once a week, like a professional reviewing customer feedback. Then close the tab.

Mine them for signal. If three different reviewers say the middle sags, the middle sags. One angry reviewer who hated your genre isn’t data — they’re a wrong-fit reader. But patterns are free editing advice. The trick is separating the pattern from the pain.

What reviews actually do

Reviews are social proof, not algorithm juice. A book with 200 reviews doesn’t outrank a book with 20 because of the number — it converts better because browsers trust the crowd. Your job isn’t chasing a review count; it’s making the book easy to trust. Early ARC reviews seed that trust. Everything after is maintenance.

So build the team, ask honestly, never respond to the bad ones, and stop checking at midnight. Your sleep schedule will thank you.

Want to see what honest reviews look like on a monster-girl harem series? Check out my books — the reviews are real, and so are the one-stars.

Every new indie author pictures the same fantasy: launch day arrives, the book goes live, and readers stampede. I’ve seen the other side of enough launches to tell you the truth — a launch isn’t a lightning strike. It’s a month-long campaign, and the boring weeks before and after release day matter more than release day itself.

Here’s the 30-day plan I’d follow. Adapt freely, but don’t skip steps.

Pre-launch: Days 1–22 (do the boring work)

A launch succeeds or fails before the book goes live. During this window, lock down the three things that sell the book: cover, blurb, and first 10% sample. Get the cover in front of readers in your genre — not your friends, not your mom — and ask one question: “Would you click this?” If the answer is vague politeness, fix it now. Vague politeness costs money later.

Build your launch stack during these weeks. That means: an ARC team (even ten people counts), a newsletter announcement queued, promo slots booked (the affordable newsletter-promo sites fill up — book them two weeks out), and your Amazon categories researched and locked. Categories are free real estate. Pick ones where you can plausibly rank in the top 100, not the giant ones where you’ll drown at #8,432.

Also: tell your existing readers. If you have an email list, they’re your ground troops. If you don’t — which is why you should build one, past me is nodding — your social followers and ARC team are the list.

Launch week: Days 23–30 (stack everything)

Launch week isn’t one day. It’s a rolling push, and the trick is stacking. Your newsletter announcement goes out on day one. Your ARC team posts their reviews (the ones who finished — never hassle the ones who didn’t). Your booked promos fire across the week. If you run ads, start them day one so they have a full week of data to learn from.

Here’s what most people get wrong: they announce once and go quiet. Don’t. You are allowed to talk about your own book every single day for a week. Tease a favorite scene. Share a one-star-worthy spicy excerpt (if your genre allows — mine does). Post the “thank you” milestone updates. Momentum is a signal, and readers can feel it.

Watch your numbers daily but judge them weekly. Day-two panic is how you end up rewriting the blurb at midnight. Give every tactic at least five days before deciding it failed.

Post-launch: Days 30+ (the part everyone skips)

Most indie authors launch, exhale, and vanish back into the writing cave. That’s a mistake. The month after launch is when you convert early reviews into social proof: update the blurb with a pull-quote if you’ve got a good one, add the paperback, and start your ad tests now that you have real conversion data.

Then — and this is the real launch strategy — start the next book. A single launch is an event. A series of launches is a career. Every book you release makes every previous book easier to sell.

Thirty days. Three phases. No magic, just stacking small advantages until they look like luck.

Want to see a launch that followed this playbook? Check out my books — each one launched the indie way.

Every few decades, humanity invents something powerful, stares at it for a while, and concludes it’s the end of the world. The printing press would destroy memory. The telephone would destroy conversation. Television would rot our brains. The internet would end privacy, bookstores, and possibly civilization.

Now it’s AI’s turn in the panic barrel. And I get it — this one feels different. It talks. It writes. It codes. It can pass exams and paint pictures and argue philosophy at 2 a.m. When something feels that close to thinking, it’s natural to wonder what happens when it starts thinking for itself.

But here’s my prediction: we’re going to look back on the AI panic the way we look back on the panic over the locomotive — remember when people genuinely believed traveling over 30 miles per hour would suffocate passengers? — and wonder why we were so nervous.

Not because AI doesn’t matter. It matters enormously. But because the fear is built on a confusion about what AI actually is, what consciousness actually is, and how human beings actually handle new technology. Let’s take those one at a time.

We’ve been here before

Roy Amara, the American scientist, nailed it decades ago: we tend to overestimate the effect of a technology in the short run and underestimate it in the long run. That’s Amara’s Law, and it explains every tech panic on record.

In the short run, we imagine the most dramatic version of the future — the robots rise, the jobs vanish overnight, the machines decide we’re obsolete. In the long run, the real transformation happens quietly, looks nothing like the panic, and mostly involves humans adapting the way we always do.

The Luddites weren’t wrong that mechanized looms destroyed their livelihoods. They were wrong that it meant the end of prosperity. The jobs transformed. New categories appeared that nobody in 1811 could have imagined. Living standards rose beyond anything the pre-industrial world could conceive.

Disruption is real. Extinction isn’t. Those are very different predictions, and we keep confusing them.

Nobody can agree on what consciousness is

Here’s the awkward foundation the whole AI doom debate is built on: the people who study consciousness for a living can’t agree on what it is.

Ask a philosopher what consciousness means and you’ll get different answers depending on who you ask. The philosopher Ned Block drew a famous distinction between two completely different things we call “consciousness”: phenomenal consciousness — what it feels like to be you, the raw inner experience of seeing red or tasting coffee — and access consciousness — information being available for reasoning, reporting, and guiding action. A system can have the second without the first, and we’d have no way to tell from the outside.

Thomas Nagel made the point uncomfortably vivid in 1974: we can’t know what it is like to be a bat. Not really. We can study its brain, map its sonar, predict its behavior — but the inner experience, if there is one, is sealed off from us. Now replace the bat with a chatbot. Same problem, except we built the thing and we’re still guessing.

Then there’s David Chalmers’ “hard problem”: why does brain activity feel like anything at all? We can map every neuron firing when you see the color blue, and still have no explanation for why there’s an experience of blueness attached. It’s the deepest unsolved problem in science, and the experts are split into camps — materialists, panpsychists, illusionists — who barely agree on the terms of the debate.

John Searle’s Chinese Room argument put it even more bluntly: a system can manipulate symbols perfectly — producing flawless Chinese responses — without understanding a word of Chinese. Syntax isn’t semantics. Fluency isn’t comprehension.

So when someone tells you with total confidence that AI is “about to become conscious” or “already is,” ask them a simple question: conscious in which sense? They usually can’t answer, because the field can’t answer. We’re building confident doomsday scenarios on top of a concept nobody has managed to define.

What AI actually is right now

Strip away the marketing and the science fiction, and today’s AI systems are prediction machines. They were trained on vast oceans of human text, and they’ve become extraordinarily good at predicting what comes next — so good that the predictions read like thought.

But fluency is not a mind. A team of researchers put it memorably in 2021: these systems are “stochastic parrots,” stitching together linguistic patterns without understanding what the words point to. That’s not an insult — it’s a description of the mechanism. Parrots can recite Shakespeare. It doesn’t mean they’ve read him.

This matters because the doomsday scenarios quietly assume something we have no evidence for: that these systems have goals, desires, or a drive for self-preservation. The classic superintelligence nightmare — the AI that turns the world into paperclips because it was told to make paperclips — assumes an agent with persistent drives pursuing them across contexts. What we actually have are systems trained to predict text, with no inner life we can detect, no desires we can identify, and no evidence of the thing philosophers can’t even define.

Could that change someday? Maybe. “Someday” is doing an enormous amount of work in every AI panic, and it’s worth noticing how quickly the conversation slides from “this system writes good emails” to “this system will inevitably want to survive.” Those are different claims separated by a chasm of missing evidence.

The real risks are boring (and that’s good news)

None of this means AI is harmless. It means the real dangers look nothing like the movies.

The actual risks are human problems wearing a technology costume: bad actors using AI to scam, manipulate, and deceive. Power concentrating in the handful of companies and countries that control the best systems. Deepfakes eroding our shared sense of what’s real. Biases in training data getting laundered into “objective” decisions.

These are serious. But notice what they have in common: they’re problems of people misusing tools, and people have a long track record of eventually building laws, norms, and institutions to handle exactly that. We did it with the printing press (libel law), with the automobile (traffic codes, licensing, insurance), with the internet (still messy, still working on it, but working on it).

Mundane risks have mundane solutions: regulation, liability, transparency, competition. Existential risks have no solutions, which is precisely why they’re such compelling stories. But a compelling story isn’t evidence.

Why everything is going to be okay

Here’s the part the panic merchants leave out: human beings are absurdly good at adapting to new technology. It’s our signature move. Fire, agriculture, writing, electricity, antibiotics, the internet — every single one rearranged civilization, and every single one left us, on balance, better off than we were.

AI will take jobs. It will also create categories of work we can’t yet name — just as the internet destroyed the travel agent and created the app developer, the content moderator, and about ten million livelihoods nobody predicted in 1995. The transition will be bumpy and unfair in places, and we should be honest about that. But “bumpy transition” and “human extinction” are not the same forecast.

And on the other side of the transition is something worth getting excited about: the most powerful problem-solving tool our species has ever built. Cures we couldn’t find. Science we couldn’t do. Creativity amplified for everyone, not just the credentialed few. The printing press democratized knowledge; AI is democratizing capability.

The view from the future

Someday — maybe twenty years from now, maybe fifty — our grandchildren will read about the Great AI Panic of the 2020s the way we read about the panic over the telephone. They’ll find the op-eds, the open letters, the solemn warnings from very serious people, and they’ll feel the way we feel reading Victorian doctors warning that trains would unsettle the uterus or whatever the concern of the week was.

They won’t think we were stupid. They’ll recognize the pattern, because by then they’ll be panicking about something new — some technology we can’t yet imagine, doing something that feels uncomfortably close to magic.

And someone, sitting where I’m sitting now, will write an essay explaining why it’s going to be okay. I hope they get half as much comfort from writing it as I got from writing this.

We’ll be fine. We always are, eventually. The future isn’t the absence of problems — it’s problems we’re capable of handling, met by people who refuse to stop adapting.

Further reading, for the curious:

Thomas Nagel, “What Is It Like to Be a Bat?” (1974) — the classic essay on why inner experience can’t be observed from outside.

John Searle, “Minds, Brains, and Programs” (1980) — the Chinese Room argument: perfect symbol-manipulation without understanding.

Daniel Dennett, Consciousness Explained (1991) — the materialist counter: consciousness as explainable machinery, no magic required.

David Chalmers, “Facing Up to the Problem of Consciousness” (1995) and The Conscious Mind (1996) — the hard problem: why brain activity feels like anything at all.

Ned Block, “On a Confusion about a Function of Consciousness” (1995) — the distinction between phenomenal and access consciousness.

Giulio Tononi’s Integrated Information Theory and Bernard Baars’ Global Workspace Theory (see also Stanislas Dehaene, Consciousness and the Brain, 2014) — the two leading scientific theories of consciousness, which disagree with each other.

Nick Bostrom, Superintelligence (2014) — the book that launched the modern AI doom debate; worth reading to understand what you’re disagreeing with.

Stuart Russell, Human Compatible (2019) — a calmer, more grounded take on AI risk from one of the field’s founders.

Melanie Mitchell, Artificial Intelligence: A Guide for Thinking Humans (2019) — what AI can and can’t actually do, from a working researcher.

Kate Crawford, Atlas of AI (2021) — the human, material, and political costs behind the technology.

Emily M. Bender, Timnit Gebru, and colleagues, “On the Dangers of Stochastic Parrots” (2021) — the paper that named what large language models actually are.

Future of Life Institute, “Pause Giant AI Experiments” open letter (2023) — the most famous artifact of the panic itself; useful as a primary source.

For my first year as an indie author, I treated writing like a hobby that sometimes paid me. Then I started treating it like a business. Everything changed.

This isn’t about loving money more than art. It’s about a simple truth: hobbies cost you money, businesses make you money, and the difference is almost entirely mindset.

The hobby trap

The hobby mindset sounds like this: “I’ll write when I feel inspired.” “I’ll figure out marketing later.” “I don’t want to think about numbers — I’m a creative.”

There’s nothing wrong with writing for fun. But if you want publishing to pay — your bills, your cover designer, your future — fun isn’t a strategy.

The hobby author writes one book, publishes it, checks sales every hour for a week, gets discouraged, and starts book two eighteen months later with no plan. The business author has a catalog strategy, a production schedule, and a marketing budget. Guess who eats.

What “business” actually means

It’s less glamorous than it sounds. Treating it like a business means:

Track your numbers. Sales, ad spend, read-through, mailing list growth. Not obsessively — monthly is fine. You can’t improve what you don’t measure.

Reinvest. The first profits don’t buy a celebration dinner. They buy the next cover, the next ad test, the next audiobook. Businesses grow by feeding themselves.

Think in quarters, not days. A bad launch week means nothing. A bad year means something. Zoom out.

Schedule production. “A book every six months” beats “a book whenever inspiration strikes” every single time. Professionals show up.

Separate the accounts. Even a simple spreadsheet separating writing income from writing expenses will change how you think. When you see the real numbers, you make real decisions.

Art and commerce aren’t enemies

Here’s what the hobby mindset gets wrong: it assumes business thinking corrupts the art. The opposite is true.

When your books pay for themselves, you get to keep writing them. When they don’t, you eventually stop — not because you lost the passion, but because life is expensive and passion doesn’t cover rent.

The most artistically free authors I know are the ones whose businesses work. Financial stability buys creative risk. The starving artist isn’t noble; they’re just one emergency away from quitting.

You don’t need permission

Nobody’s going to hand you a business license for your writing career. There’s no gatekeeper to impress, no boss to promote you. That’s the whole point of indie.

But it also means nobody’s going to do the unsexy work for you. The spreadsheet. The schedule. The reinvestment plan. The honest look at what’s working and what isn’t.

Make the shift. Keep the art sacred — and run the business like you mean it. That’s how you get to do this for decades instead of dabbling for a year.