I Canceled My Book Deal
Key topics
A writer's decision to cancel their book deal has sparked a lively debate about contract obligations and the impact of AI on the publishing industry. Commenters are dissecting the details of the advance payment and whether it needed to be returned, with some arguing the publisher didn't do anything wrong since the author "froze" the contract instead of canceling outright. The discussion takes a futuristic turn as one commenter provocatively suggests that all future books will involve AI, prompting another to wonder who will buy books in this era. As the author clarifies their side of the story, a consensus emerges that neither party acted improperly.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
39m
Peak period
120
0-6h
Avg / period
16
Based on 160 loaded comments
Key moments
- 01Story posted
Dec 31, 2025 at 1:26 PM EST
9 days ago
Step 01 - 02First comment
Dec 31, 2025 at 2:05 PM EST
39m after posting
Step 02 - 03Peak activity
120 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Jan 3, 2026 at 10:30 AM EST
5d ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
> They offered a $5000 advance with the first half paid out when they approve of the first third of the book and the second half when they accept the final manuscript for publication.
> I continued to get further behind on delivering my revised draft of the first 1/3.
> Around this time, there was a possibility of me changing jobs. Oh, and my wedding was coming up. That was the final nail in the coffin.
> There were too many things going on and I didn't enjoy working on the book anymore, so what is the point? I made up my mind to ask to freeze the project.
> They agreed.
They never got to that point.
You “froze” the contract instead of telling them you intended to stop all together and it also seems like you didn’t return their advance.
The publisher didn't do anything "wrong". It was their suggestion to freeze it instead of cancel immediately. I didn't intend on giving up on the book even then. I didn't return the advance because I never received the advance.
I would certainly not argue that. LLMs do not understand anything, and are thus prone to non-deterministic inaccuracies in their output. Due to that, I think it is extremely foolish to use one for learning unfamiliar topics. Give me a book every time, because (if it's a good book) I am guaranteed to actually learn something. Not so with LLMs.
With books the author can give advice that's not as widely known and is thus much less likely to show up in an LLM output.
I think there is still a place for a book here. I think I might buy a book (or may have done 10 years ago when I was still coding) of things you should know (especially from a respected publisher), that being a longer form book I could work through over time.
You might want to look at their outlines to see what they're teaching. Then, decide if you can do something similar and/or cheaper.
I hope this trend is not industry wide. A publisher chasing fads and trends over enduring quality, so sad. I wish I knew who the publisher was to avoid but I can foresee their pivot to AI authors with titles like "From Zero to Hero, ChatGPT 5.2 Top Prompting Secrets for Dummies"
It's exactly the sort of financial pressure that will make them chase fads and trends, and it gets worse in difficult economic times.
That is true of many industries, including films, vc software startups, games and books. As the Internet increases competition and opportunity, it is likely to become more true.
The thing is, it’s not about getting chapters published on AI. The publishers are keenly aware that AI is using their content to steal their market and so anything they publish on AI will be obsolete before the final manuscript is published. It’s about getting potentially difficult first time authors to quit before their first third gets approved - that’s when the author is owed their first advance.
It’s a lot easier to slaughter sheep if the most docile select themselves.
Publishers are going to demand chasing the hot-new-thing which will most likely be irrelevant by the time the book is on the shelf.
"How to write x86 ASM... with the Copilot Desktop app! - Build your bootloader in 15 seconds!"
I hope you finish the book. I would buy it.
I think the same is true for tech books but I don't know as I haven't written one.
A novel or other fiction is the opposite; there you do have to write the whole thing first.
This is absolutely not true in the world of technical publishing. I mean books published with publishers like O'Reilly, Manning, No Starch, etc. Usually you either come to them with just a proposal and a couple chapters. Or their acquisition editors actually reach out to you. It's the exception (not quite rare, but definitely less than 20% of books) that comes to them with a finished manuscript. I did that with my last book and I've published 4 technical books before that across three different technical publishers, so I know a bit about this business...
I'm just replying to this comment to not discourage people who just have an idea and not a finished book yet but have the motivation to finish and want to get a deal.
The upshot is, they don't want to do the hard part - continuity editing, developmental editing, hell, just finishing the dang thing. Even the boring chapters you didn't really have any idea what was going to go on there.
Writing, as an occupation, is a whole lotta schmoozing, attending conferences, volunteering, promoting. Maybe 1 month of writing a year, for 11 months of the hard stuff.
I have a buddy who says he always wanted to start a bar. I said, You like budgeting? Taxes? Hiring? Firing? Stocking? Remodeling? Promoting?
Nah; turns out, he just likes to hang out in bars.
The only reason you start a business is, because you like to run a business.
The only reason you become a writer is, because you like the business of writing.
The usual accounts I've heard from my friends who published with Wiley, Addison-Wesley, or O'Reilly is that they sign up, get some in-depth feedback on the first couple of chapters, and then are on their own. I've never heard of a tech publisher exercising this level of creative control. I don't doubt that this happened, but it just sounds out of the ordinary.
Does it matter which exact one if all the publisher oligarchs behave exactly the same?
If any folks want to talk about nonfiction publishing, I'm always happy to chat as many people were incredibly generous with their time for me and I'd like to try to pay it forward.
Rebooting a Nation: The Incredible Rise of Estonia, E-Government and the Startup Revolution Paperback by Joel Burke
1) https://news.ycombinator.com/item?id=46398265
Some of them already replied saying the proposal seems interesting but they want to read a few chapters. I don't know if I am in the right path or not, but I'd love to read more about your experience and what can be shared!
I think I lack all the last parts (that some publishers are requiring for) such as a social media platform to reach your potential readers. I find that a bit unfair because it means you first have to play the Instagram game and once you are popular there, you can write a book.
If you give me an email address I'd love to tell you more about my book!
It's not always a dealbreaker, I didn't have any social media following or anything -- the way I pitched it was by figuring out a bunch of conferences, niche podcasts, etc. and highlighting that there was an audience there I could activate (and marketing is a big part of the book process I've learned).
My bio has my email now!
Seriously, I’ve seen this exact genre of comment daily on hn lately and I don’t get what you’re gaining by trying to sniff out bots. Not what anyone has to gain by truly botting on here. Nobody is selling their HN accounts right? And how many pretty run-of-the-mill comments like the above would it take to have an account worth selling anyway even if there was a market for that? 100,000?
The prestige probably isn't what you'd expect. Having an ISBN to one's name carries ~zero weight for the people that actually matter for your career (it may mildly impress some future coworkers in a decade's time, though). The real value of having written a book is that then you have written a book.
Having a publisher carries one extra benefit that was merely implied in the post: you get assigned a professional editor. If you're lucky (I was), the editor has a really good understanding of how to wield language and the lessons you get from the editing process are going to far outweigh any direct financial benefits. When I wrote mine, I had been doing freelance writing for a large IT magazine for nearly ten years - and as a direct result had been taught how to use written language as a weapon by a good number of old-guard journalists. The year I spent on the book project taught me a LOT more still, because I was assigned an editor who herself was studying (in a university) to become a language teacher.
The skills I picked up from that process are with me to this day, and ironically have been the single most valuable asset I have as an engineer and/or engineering leader. Being able to write well to a varying audience is a superpower. You also learn to appreciate professional authors, because what they do is decidedly not easy.
In the end my book sold well enough to earn out its advance, so I guess it was a non-failure for the publisher as well. I also picked up a lesson for all aspiring authors:
Writing a book is easy. You sit down by the keyboard, slit your wrists and pour it all out.
Goodreads seems to think so. https://www.goodreads.com/author/show/14291276.Joel_Burke
Edit: Added some context and I'd also mention that one thing that was quite helpful is that at the start of the writing process I created a massive spreadsheet where I'd add in quotes, writing, and anything interesting I thought I might pull from (some of it manually written, like when watching documentaries). This was hugely helpful when I was going back but also during the writing process so I had a single source of truth I could keyword search. I've just checked it and its got 4787 rows, with most entries being about a paragraph long
Still, that's what it takes to reach N > friends+students.
It's beyond ironic that AI empowerment is leading actual creators to stop creating. Books don't make sense any more, and your pet open source project will be delivered mainly via LLM's that conceal your authorship and voice and bastardize the code.
Ideas form through packaging insight for others. Where's the incentive otherwise?
As a banker, I see the "Advance" not as a loan, but as an Option Fee paid for the author's future output. The publisher tried to exercise that option to force a pivot: "Inject AI into this classic book." They tried to turn a "Shinise" (classic craftsmanship) product into a "Trend" product. The author refused to dilute the quality, so the deal fell through.
Keeping the advance is financially justified. The "R&D" failed not because of the engineer's laziness, but because the stakeholders demanded a feature (AI) that broke the product's architecture. In finance, if the VC forces a bad pivot and the startup fails, the founder doesn't pay back the seed money.
You are right—if the carpenter just ran away, he would usually be sued. But in this specific case, the client (publisher) agreed to let him go. It’s more like: The carpenter said "I'm quitting to join the circus," and the client said, "Fine, keep the deposit, just leave."
In finance, we call this a "Write-off" to maintain relationships or avoid legal costs. It seems the publisher decided it wasn't worth fighting over.
> this is a textbook case of a "Failed Pivot" driven by investors
It was a rejected suggestion. In no way did this actually cause the deal to fail.
What killed this deal is that the author did not set aside enough time to do the work, and then lost interest. This seems pretty clear from the post. From my reading, it looks like the author was missing deadlines before they even brought up the topic of AI. And then continued missing deadlines and pushing out the schedule even after they said no to the AI ideas. And then ultimately put the whole thing on hold and never picked it back up.
If the publisher said “put AI in this or we kill the project”, your reading would be correct. But I don’t see that anywhere in this write up. I see an author who didn’t deliver. Not even the first third, so there wasn’t even an advanced payment.
And to be clear, I am not hating on the author here. Life happens. Interests change. All I’m saying is that this project was not canned because of the refusal to put AI into it.
Perhaps the root cause of the missed deadlines was actually a "loss of conviction." The author touches on his own doubts: "With LLMs around, no one needs this book anymore." While the publisher didn't legally force him out, the "AI pressure" (both from the publisher and the market) might have eroded his belief in the product's value.
It wasn't a murder (firing), but it might have been a death by loss of passion.
It didn’t sound like they got the advance (or rather the first half) as they never fully completed the first 1/3 of the book before the deal fell through.
I’m doing it again soon for my next book. It’s fantastic, though having a following online is helpful to get the word out
Amazon and companies like them must be broken up because they harm the producers and consumers with dictating buying and selling pricinf.
The whole experience was wonderful. I had basically none of the problems that this fellow experienced with his publisher, and I am delighted about how it went.
I did some things differently. For one, I had already been selling the book on my own for a few years, and was essentially on the 3rd self-published edition. Because of this, they were able to see what the almost-finished product was.
I told them I would not make massive changes to the book, nor would I contort it to the AI trend (the book barely mentions AI at all), and they never pressured me once.
Their biggest contribution was their team of editors. This book has code on just about every page. I had 3 technical editors go through it, finding many bugs. How many? Let's just say "plenty".
And the feedback from the non-technical editors was, to my surprise, even more valuable. Holy crap, I cannot express to you how much they improved the book. There were several of these folks (I had no idea there were so many different specialties for editors), and all of them were great.
(They also accepted my viewpoint when I disagreed with them, immediately, every time. The final published version of the book was 100% my own words.)
From all of that, I made improvements on what must have been almost every page, and rewrote two chapters from scratch. I also added a new chapter (I volunteered for it, no one at any point pressured me to do that). The result was making a book that IMO is at least twice as good as what I was able to accomplish on my own.
I do not resonate with the article author's comments about compensation. He negotiated a pretty good deal, I think; it's not realistic to get much better than what he did, since the publisher is a business with their own expenses to pay, etc.
I was pretty disciplined about meeting deadlines that we agreed to for certain milestones. That helped my relationship with the publisher, obviously.
All in all, it was a great experience, and I am glad I did it this way.
Reading the article, it sounds like my publisher (oreilly) was better to work with than his, but I think he could have done some things differently also. In the end, though, I agree with him that it was best to walk away in his situation.
I will say I was very happy with the animal they came up with! If I was not, I would have asked them to change it, and I bet they would have. They showed me a preview version early on, so there would have been plenty of time to do so.
The publisher he worked with will push you but also make a better book in the end. You have to be willing to do your part.
(Not naming the publisher because I don't want to out myself.)
I've come to hate every cookbook that starts with 100 pages of here is a tour of my pantry, which sounds a lot like, here is how to use pip!
Another bonus feature, would be to remove: breakfast, appetizers, and salads from all cook books, or put them in the back where no one needs to look at them.
I find it quite difficult to find quality programming books that actually deal with the details and waste no pages explaining the basics that can be found in literally any other book about a specific language/technology.
When it was mentioned that the publisher demanded the book be "dumbed down" it wasn't a surprise to me at all. I also think it's hurting sales of programming/SWE books at large as beginners are more likely to just use up-to-date Internet tutorials than books, but those more experienced who would benefit from in-depth books can only find the dumbed-down ones.
To each their own. As someone who learned to cook as an adult, I’ve appreciated seeing both what someone has and what nonsense I own that they manage just fine without.
Yeah I agree. I hate when books do more hand holding than the reader clearly needs to the point of tedium. And Austin was clearly not writing an absolute beginners book.
That's why when I pitched both the Classic Computer Science Problems series and Computer Science from Scratch I explicitly told publishers in the proposals that I was not writing a beginners book (been there, done that). I was clear that I was writing an intermediate book for people that already know programming.
It's a different, more narrow audience. But you can be successful if you write a good book. It's also a less tapped market and luckily publishers were able to see that.
I wrote a similar blog post a month ago describing the process of creating the book and getting it published called "Writing Computer Science from Scratch":
https://www.observationalhazard.com/2025/12/writing-computer...
Some in this thread have wondered what publisher Austin was working with. Based on my experience working with three different technical publishers and the setup and terms Austin was offered, my guess would be Manning. But that's just an educated guess.
I will critique the blog post a little bit. It's presented as a critique of the experience of working with the publisher, but ultimately I'm reading between the lines that the book failed because he was missing deadlines and as he wrote "life got in the way" and he lost his motivation, only partially because the publisher wanted AI in more of the book. Many of the trials he had along the way: dealing with a development editor who wants to tailor your style to a particular audience, a technical editor who needs a couple chapters to warmup, back and forth on the proposal, etc. these are all really par for the course when writing a technical book. Ultimately you have to be self-motivated to finish because of course the development editor, technical editor, etc are going to disagree with you from time to time and try to push you in different directions. If that alone is so demotivating to you, it's just not for you to work with a publisher.
In fairness to the author, he presents a reasonably balanced view and it did not read to me like “my publisher sucked.”
I assume that was about competing with LLMs writing content, rather than including LLM-related technical projects.
Glad the author got out relatively unscathed.
Self publish - especially with AI available to get you through the stuff where you just need superficial or process knowledge, like which firms to hire and how to market a self-published work, what boilerplate legal protections you need. You'll get 99% of the value of a big publishing firm at a small fraction of the cost, and you won't have to put up with someone else taking a cut just because they know a few things that they don't want to tell you in order to justify taking your money.
-Do you release a physical book? If so, what are the mechanics of that and how much does each book cost?
-Do you release it in an electronic format? If so, what format and how do you stop it being mercilessly pirated?
Bandcamp learned this lesson. GOG learned this lesson. They both provide services users love, without DRM, and just accept that there is no capitalistic scarcity inherent to digital goods like there is to physical ones. An indie ebook publisher would be wise to heed those teachings.
Putting aside for a moment that nobody should be trusting a frequently-hallucinating AI algorithm with any of the above...
Your world-view is one of those that returns to the old adage "it only works if you value your time at zero".
Its the sort of thing we see in tech the whole time. Some dude saying "oh, I can just fix my motherboard myself".
Well, sure you can dude. Because you've got the domain expertise, you've got the kit AND you are willing to value your time at zero.
However in the majority of cases, if you do not value your time at zero, then spending even just a few hours waving a soldering iron over the proverbial motherboard is time better spent on other tasks and the "more expensive" option suddenly does not look that expensive any more.
I’m glad I did it but I’m not sure how much the publisher added beyond some prestige and a few bucks. The first edition in particular I felt I needed to pad out a bit to meet length requirements.
What if you self publish yourself using Amazon toolings? Will the numbers be worse? At least you will be in charge of your own quality and deadlines.
And by "most" there I mean "all". Yes, there are exceptions, but those exceptions prove the rule.
I've written 2 technical books, for incredibly niche audiences, where the total number of potential buyers is numbered in the low thousands.
I self published as a PDF. and charge $200 a copy, of which I keep $200. It's -marginally- worth it. But the hourly rate is much lower than my day job.
The marketing benefit (as it affects my actual business in the same field) is likely real, but hard to measure. Still, having "written the book" opens doors, and brings credibility.
The publisher expended time and money on the author and got nothing in return. This isn’t surprising, and it’s why first-time author royalties are so low.
That was my read as well. The book deal fell apart because the author never wrote most of the book.
While writing I have had similar feeling as the author to publisher/editor comments, especially related to:
> The unhelpful feedback was a consistent push to dumb down the book (which I don't think is particularly complex but I do like to leave things for the reader to try) to appease a broader audience and to mellow out my personal voice.
I also remember being very frustrated at times with the editor needing things "dumbed down". I used to get very annoyed and think "didn't you pay attention! We covered that!" But then I realized: If I can make this easy to understand by a fairly non-technical editor at a first pass, it absolutely will make this book better for the reader.
Publishers have a lot of experience publishing books, so I've learned that their advice is often not bad.
There was also plenty of advice from the editors I vehemently didn't agree with, so I pushed back and quickly realized: publishers need you more than you need them, so very often you do get final say.
But you still have to actually write the book. Book writing is hard, and a much more complex process than writing blog posts. Personally I feel all the editorial feedback I've gotten over the years has made not only my books better, but also has really pushed my writing to be higher quality.
The author had all the leverage regarding content. It’s not like the publisher could actually incorporate what they were asking for with AI, they still need an author to do that and it was a totally new subject at the time. Their demands were empty.
I don’t think the author would have finished the book if it was self-published. They clearly didn’t want to write a book that badly.
Not to say that finishing a whole-ass book is easy, I’m certainly not going to pretend that’s the case.
I’ve lately been trying to finish more side project type things in my life because these dead ends themselves feel empty to me. I am trying to set scope reasonably and then just finish even if it’s painful or there’s no confetti-style payout and nobody else cares.
Another constraint of a technical book that I didn't see mentioned here was that time almost has to be very limited during the writing process. I worked on a couple mobile development/design books, and an iOS 18 programming and design guide is worthless after Apple announced Liquid Glass last summer. At 2+ years into the project and seemingly only 1/3rd complete, the publisher really needs to be sure the content will still be relevant after released.
I think you should self-publish. With your existing audience, you'd sell plenty of copies, and nobody would push "AI" into your work.
Isn't it obvious? Because the ChatGPT output wouldn't be reviewed!
You buy books like these exactly because they are written by a professional, who has taken the time to divide it up into easily digestible chunks which form a coherent narrative, with runnable intermediate stages in-between.
For example, I expect a raytracing project to start with simple ray casting of single-color objects. After that it can add things like lights and Blinn-Phong shading, progress with Whitted-style recursive raytracing for the shiny reflections and transparent objects, then progress to modern path tracing with things like BRDFs, and end up with BVHs to make it not horribly slow.
You can stop at any point and still end up with a functional raytracer, and the added value of each step is immediately obvious to the reader. There's just no way in hell ChatGPT at its current level is going to guide you flawlessly through all of that if you start with a simple "I want to build a raytracer" prompt!
https://kevmo.io/zero-to-code/
I inked the deal in 2023, but shortly after felt like the market was too dead for newbies. When I initially removed the website for the book, I got a small wave of complaints, so I guess some folks still found it helpful.
I'd say that almost no one should work with the major technical publishers more than once. There's some good basic skills you learn but otherwise, they contribute very little that you couldn't get done on your own.
But, I totally understand author's reasoning, and it's one of the reasons I want to explore different publishers as I want to deviate from writing strictly technical books.
What an incredible take. It is both so wrong on so many levels and also technically correct, akin to saying "All of our future books will involve spellchecker."
I hate it.
Me: That doesn't sound too bad! They keep 12% of the profit, leaving him 88%!
".. and then 15% [after that]"
This reminds me of the scene in Queen of the South. FL (female lead) is new to power, negotiating some deal.
Guy: How much?
FL: Unsure how much to take 10%.
Guy: Thinking her cut is only 10%, seeing her as weak Oh.. heh.
FL: Detects her mistake For you.
Guy: Face gets red, angry But.. but..
One important aspect to this is that a typical first-book technical author knows well the subject matter, and sometimes knows how to write too (but usually not, as was my case), but does not know how to edit, typeset, publish, market, and sell well. That's what the publisher knows best. And of course, they want sales, and they understand that overall beginner books sell better than advanced/expert level books.
I encourage the author to continue writing and self-publish, and at a later time a publisher come to package and market a mostly finished product.
But my consecutive attempts of writing a book failed because of my ADHD and missing guidance. I can't do employment, but I really need someone to "nag" me 2-3 times a month to keep focus.
Maybe write a book about "Classic projects using AI", whether it makes sense or not. And use AI to write that.
200 more comments available on Hacker News