Category: Craft & Confession · Tags: Indie Author, Infrastructure, Process, Vulnerability, Creative Independence
I thought I was signing up to write novels.
That sounds naïve when I say it out loud, but it is true. I imagined long hours wrestling with structure, obsessing over sentence rhythm, and shaping desire into something deliberate and exact. I did not imagine debugging server scripts at midnight or reading platform documentation written for people who already speak a language I am still learning.
No one explained that an independent author is also expected to understand API tokens, which are digital keys that allow one system to communicate with another. No one mentioned cron jobs, which are automated tasks that run on a server at scheduled times so a website can function without constant manual oversight. No one told me that I would spend evenings inside a business dashboard trying to determine which credential I was holding and why the system kept rejecting it without clearly explaining why.
This is not a tragedy. It is simply the reality of independence.
At some point, “independent author” stopped meaning “writer without a publisher” and started meaning “you are the publisher.” You are the writer, the designer, the marketer, the web administrator, and the person responsible when something breaks. You are the one who upgrades hosting because shared servers quietly sabotage email delivery. You are the one who learns about authentication protocols because you refuse to rely entirely on third-party tools that can disappear or change their terms without warning.
I do not always understand what I am doing.
There is a particular kind of quiet self-doubt that appears when you reread technical instructions for the third time and still are not certain whether you are about to fix the problem or create a new one. When a system returns an error message, it is difficult not to internalize it. You begin to wonder whether the failure is in the configuration or in you.
I am not wired like a growth strategist. I do not wake up thinking about engagement funnels or conversion metrics. I wake up thinking about narrative architecture and the emotional geometry of a scene. I think about cadence. I think about how masculinity fractures and reforms under pressure. That is the mind I trust.
But that mind does not automatically know how to configure DNS settings or manage server-side automation.
So I learn. Slowly. Sometimes resentfully. I search forums. I read documentation. I copy and paste code with the careful anxiety of someone who knows one misplaced character can unravel an entire system. I refresh dashboards more times than I want to admit. I build automation not because I enjoy it, but because I want control over how my work lives in the world.
And that is where the emotional toll shows up.
It is not the difficulty itself. It is the accumulation. The constant switching between creative mode and technical troubleshooting. The awareness that if something breaks, there is no department to escalate it to. The weight of knowing that the story, the site, the list, the distribution, and the infrastructure all sit on your shoulders.
Creative freedom is real. So is exhaustion.
The part no one talks about is how easily independence turns into isolation.
When something breaks, there is no team channel to drop into. There is no department whose job it is to care. There is only you, a screen, and the creeping suspicion that you might be building something no one will ever fully understand except you.
Some nights I wonder whether the infrastructure has become a proxy for control. If I can master the server, the automation, the distribution, then maybe I can protect the work from being ignored. Maybe I can protect myself from the quieter fear that none of this will matter anyway.
That is the uncomfortable layer beneath the technical learning curve.
I write queer, mythic, explicit work that refuses to soften itself for comfort. I ask readers to sit inside masculinity and desire without flinching. I claim that discomfort is part of honesty. And then I spend three hours troubleshooting an authentication error because the idea of depending on someone else’s system feels like a different kind of exposure.
What if the machine is not just stewardship. What if it is armor.
What if the endless configuring and optimizing is a way to avoid the more vulnerable admission that the work might stand on its own, or it might not.
Creative independence sounds noble. In practice, it often feels like standing in the middle of a room you built yourself and asking whether anyone will ever walk in.
So I will ask this without polish.
If you are building something alone, how much of your effort is creation, and how much is self-protection dressed up as competence?
And if the machine disappeared tomorrow, if all that remained was the work and your willingness to let it be seen, would that be enough?
C.N. Halden
The Record Extends.
This space is for correspondence, not performance. Messages are reviewed and won’t appear publicly by default. If you want to engage—agree or disagree—email is the right channel.