February 13th (nope, not a Friday) was supposed to be the big day. The moment of triumph. The long-awaited, sweat-and-tears-fueled launch of Project DELAY. The countdown had begun, anticipation was at its peak, and then… The numbers started going up. Yes, dear readers. Up. Like some sort of cosmic joke, the countdown clock reached zero and decided, “Nah, let’s try the other way.” And that’s when mild panic turned into a full-blown existential crisis.
“I don’t know why I expected this to go smoothly,” confessed the brave but bewildered author JC Spark, who is still in recovery from this blow on their sanity. "But I obviously did. And that was my first mistake."
A DELAY in DELAY (Because of Course)
Now, let’s rewind. Project DELAY (yes, that’s really its name) had already lived up to its moniker several times, suffering delays that prompted hilarious (read: not hilarious) comments from onlookers. But after endless preparation and fine-tuning, it was finally time to launch.
Except, it didn't.
We decided to let JC describe it herself because I must admit I had a hard time not laughing and was reminded that I don’t write for the art section, thank you very much.
So this is from the interview I did with the author after the hilarious non-starter was falsely directed to our tech desk.
“After months (okay, years) of writing, editing, tweaking, second-guessing, and delaying (yes, I hear the irony), my book DELAY was finally ready to launch. The countdown began. The excitement built. This was it! The moment had arrived!
And then…
The countdown hit zero and started going back up.
Now, I’m no rocket scientist, but I’m pretty sure that’s not how launches work.
A DELAY in DELAY. Of Course.
Cue panic mode. Can you imagine? You pour everything into a project, push through setbacks, battle endless delays (and hear so many “hilarious” jokes about the title along the way), only for the launch to not launch?
So, there I was, staring in horror at a countdown that had decided time was an illusion, frantically messaging BackerKit’s support team, hoping they’d have some genius-level fix for this baffling glitch.
They did.
“You have to manually initiate the launch.”
Oh.
So, essentially, my book was sitting there, ready to go, waiting for me to, you know… press the button.
This felt exactly like calling IT support only to be told, “Have you tried turning the device on?” Or like realizing you spent an hour troubleshooting a device that just wasn’t plugged in. Classic.
With my newfound knowledge of how buttons work, I clicked the thing, and at long last—DELAY launched! 🎉
Finally, a Liftoff!
And at least two people noticed.
Was it the smooth, cinematic, confetti-filled launch I imagined? Not quite. But at this point, the how doesn’t matter. The book is out, the journey is real, and DELAY has officially left the launch pad.
And let’s be honest—would it really be my book launch if it didn’t involve some level of ironic chaos?
(Note: No countdowns were harmed in the making of this launch. Just my pride.)“
*Editor's note: At this point, the editorial team would like to apologize to the author for the unprofessional behavior of our technical editor. We recommended that he read the book Delay to raise his awareness. And we would like to share his conclusion here: “It reads like art – but I actually understand it, it's a story. And my husband fell in love with it so much that I now have to get it signed for him – I guess I'll just have to go through with it.”
Kommentar hinzufügen
Kommentare