This piece originally started life as part of my submission of One Fight At A Time to Jessica Kingsley Publishers. They asked for a separate sample of my own writing alongside the manuscript, so this was what I wrote.
The submission ultimately went no further, but I liked the piece enough to come back to it. It felt worth keeping, partly because it documents something I hadn’t expected when I started the book: writing it changed the way I think about writing itself.
When I first started writing One Fight At A Time, I thought I knew what it was going to be about.
That turned out to be the first thing I was wrong about.
The original idea was much narrower. I have spent much of my life working in hospitality, where getting on with it is part of the job. You turn up, deal with whatever has gone wrong, get through the service and start again tomorrow. There was something in that mentality I wanted to explore outside the kitchen: discipline, momentum, rebuilding yourself when things had slipped.
At the beginning, I thought the job was mainly to explain that well enough. It took quite a lot of writing before I realised that explaining an idea and writing a book are not remotely the same thing.
The more I wrote, the more real life kept getting in the way of my arguments about discipline and momentum. Sometimes people do not need more discipline. Sometimes they are just knackered. Sometimes the problem is not that somebody doesn't know what to do. They know perfectly well what they should be doing, but they are working too much, worrying about money, trying to be a decent partner or parent, and gradually becoming somebody whose main skill is keeping everything moving.
That changed the book. It also changed the way I wrote it.
One of the mistakes I made early on was starting with the answer. I would have an idea, decide what the lesson was, and then write towards it. That seemed sensible enough, especially with nonfiction, but it often produced something too neat. I wasn't really exploring anything. I was building a case for something I had already decided was true and then choosing the examples that supported it.
The passages that became more interesting were usually the ones where I wasn't completely certain what I thought when I started. Sometimes all I had was an uncomfortable realisation, a question, or something that didn't quite fit with the argument I thought I was making.
As a chef, a large part of my working life has involved making decisions quickly and being judged on whether those decisions work. There is usually a point when talking has to end and somebody has to decide what is going on the plate. You cannot stand at the pass indefinitely considering the philosophical implications of whether the sea bass needs another thirty seconds. At some point, somebody has to call it.
Writing did not work like that.
That took some adjustment because uncertainty initially felt like a weakness. If I was the person writing the book, surely I was supposed to know what I thought. Surely the point was to arrive with something useful and explain it clearly.
Eventually I realised that certainty too early could be its own problem. In a kitchen, a decision normally gives you feedback fairly quickly. The food works or it doesn't. Service moves or it doesn't. Writing can let you be confidently wrong for several thousand words before anything stops you. A neat argument can look completely convincing while you're writing it, especially when you've chosen all the examples yourself.
Sometimes the better thing was to resist closing the question simply because I knew how to write a tidy answer to it.
One of the bigger examples was identity. At some point I asked myself what was left when I stopped defining myself by what I could do for everyone else.
I did not have a particularly good answer.
Earlier on, I would probably have seen that as a problem and gone looking for one. I could have written something reassuring about rediscovering yourself outside work and responsibility, found a neat conclusion and moved on.
Eventually I began to understand that not having an answer might actually be the point. If you have spent years understanding yourself through work, usefulness, providing, parenting and being the person who sorts things out, perhaps there isn't a fully formed hidden identity underneath it all waiting to be uncovered. Perhaps I don't know is sometimes the honest place to start.
That changed my idea of authority as well. I became much more comfortable writing from experience without pretending that experience had made me an expert on everybody else's life.
There are things I know because I have lived through them. I know what high-pressure work feels like. I know what it is to be responsible for other people. I know what happens when family, money, physical tiredness and your own expectations all pile up together.
But that does not mean I know exactly what somebody else should do.
The book improved when I stopped pretending those were the same thing.
I started thinking of it less as standing at the end of the road explaining the route and more as writing from somewhere on the road itself. I could describe the pothole I had just fallen into, point out the turning I had missed and admit where I had gone in circles. What I couldn't honestly do was pretend I had reached the destination and was now handing everybody else directions.
Another thing I learned was how easy it is to mistake repetition for emphasis. A book of around 108,000 words gives you plenty of opportunities to make the same point fifteen different ways, and I took most of them.
While I was writing, each version often felt different because I had arrived at it from a slightly different direction. One might be about work, another about exercise, family or money. In my head they were separate thoughts because the examples were different. When I stepped back and looked at the manuscript as a whole, it became obvious that some of them were making essentially the same point.
That led to a less enjoyable lesson: liking something is not the same as needing it.
There were paragraphs that had taken ages to get right and sections I liked as pieces of writing, but the amount of effort I had put into them did not mean they needed to stay. I had assumed editing meant improving sentences. Sometimes it does. Quite often it meant asking much less satisfying questions.
Does this section need to exist? Have I already said this? Am I explaining something because the reader needs it, or because I'm pleased with the explanation? Is it actually clearer, or just longer?
That last one still catches me. I can nearly always add another example or explanation. There is nearly always another angle available. The danger is that eventually you explain the life out of something.
Writing from real life helped with that. If I started with an abstract idea, I could waffle for pages. If I started with something that had actually happened, the writing had something solid underneath it. A missed workout could lead into a bigger question about failure and restarting. A difficult day at work could open into responsibility or identity. A small moment at home could tell me more about pressure than another page explaining pressure in the abstract.
Things I would once have dismissed as too ordinary to write about became some of the most useful material.
That changed the process too. I stopped expecting useful writing to arrive in chapter order, or even in the right shape. Sometimes I needed to write far too much before I knew what I was trying to say. Eventually that stopped feeling like evidence that I was doing it badly and just became part of how I worked.
I would get the thought out first, then look at what was actually there. Find the bit with some life in it. Cut things. Move things around. Realise the paragraph on page four was actually the beginning. Discover that the point I thought I was making had quietly disappeared and a better one had taken its place.
It wasn't elegant, but it worked better for me than staring at a blank page waiting until I understood everything before beginning.
I became much less precious about unused material as well. Early on, deleting something felt like wasting it. If I had spent two hours on a passage and then removed it, those two hours seemed to disappear with it.
I don't see it like that anymore. A paragraph can have done its job even if nobody ever reads it. Sometimes you have to write the wrong page to find the sentence that takes you in the right direction. Sometimes 1,500 words exist mainly to show you which 200 actually contain the thought.
Sometimes the writing wasn't the finished product. It was the thinking.
Some of the process was much more modern. AI was a significant part of how I developed the manuscript, and there is no honest version of this essay where I pretend otherwise.
I used it to analyse structure, compare drafts, find repetition and identify places where I was overexplaining. I could put two versions next to each other and examine the differences much faster than I could have done alone.
Sometimes it suggested wording too. Some of it was useful. Some of it was awful.
That became another lesson in editing, because AI can make a sentence cleaner than mine and still make the paragraph worse. It can smooth away the awkwardness that made something sound like me. It can make an uncertain thought sound certain. It can produce a beautifully balanced conclusion to something I deliberately hadn't solved.
It is very good at producing language that looks finished.
That is not necessarily the same as language that is true.
Other readers presented the same basic question in a different way. I deliberately asked people who would notice different things. A poet friend might pick up on rhythm or emotional impact. Somebody else might care more about clarity or whether an argument actually landed.
The useful distinction was that listening to feedback did not mean obeying it.
If one person dislikes something, that is information. If several people independently stumble in exactly the same place, that is different information. Either way, the job is not to defend every sentence, but it is not to hand the manuscript over either.
Whether the suggestion came from software or another person, the final decision still had to be mine. I had to understand why a change belonged rather than accepting it because it sounded clever or because somebody else was confident about it.
That doesn't mean protecting every clumsy sentence simply because it came from me. Some of my sentences deserve all the help they can get.
It means I still need to recognise the finished thing as mine.
Reader feedback also exposed something I hadn't expected. After months inside a manuscript, you stop reading only what is actually on the page.
You remember earlier versions. You know the anecdote that used to sit between two paragraphs. You know the explanation you removed because it had started feeling obvious. You know what a sentence is meant to connect back to because three drafts ago that connection was much clearer.
The reader knows none of that.
They cannot see your intentions. They cannot see the deleted paragraphs still sitting in your head. They only have what is actually there.
There were times when somebody's feedback showed me that I had removed the bridge but was still mentally walking across it.
That may be one of the stranger parts of editing a book: trying to forget what you know for long enough to see what somebody else actually receives.
I'm still not sure I'm particularly good at that, but I'm better than I was.
The most uncomfortable part was when the writing started showing me gaps between what I believed and how I actually behaved.
There were things I understood intellectually at the start which took much longer to understand properly. I knew perfectionism could be counterproductive, but that did not mean I had stopped behaving like a perfectionist. I knew that a missed day did not erase previous progress, but that didn't mean I always reacted that way when I was the one who had missed it. I knew people were more complicated than simply being disciplined or undisciplined, then repeatedly caught myself applying much harder rules to myself than I would ever apply to anybody else.
Writing made those contradictions difficult to ignore because I had to keep putting the belief next to the life.
There is something uncomfortable about spending pages arguing that a bad week is not a verdict and then noticing how quickly you turn your own bad week into one. Or writing about good enough being good enough while trying to improve a paragraph for the nineteenth time. Or writing about identity beyond usefulness while still feeling most comfortable when you are being useful.
At first I treated those contradictions as problems. If I was writing the idea but not living it perfectly, perhaps that weakened the argument.
Eventually I began to think the opposite.
The contradiction was often the argument.
People can believe one thing and do another. We can understand something and still struggle to live it. We can make progress, lose ground, start again, become convinced we have finally worked something out and discover six months later that we have not.
Pretending otherwise would have made the writing less honest.
In that sense, the book became a strange sort of audit. Not a diary, and not an attempt to document every part of my life, but a repeated opportunity to notice where my ideas collided with my actual behaviour.
Sometimes the life improved the writing. Sometimes the writing made me notice the life. By the end, I don't think those two things stayed entirely separate.
That messiness became much more interesting to me than the tidy version. It also made me suspicious of writing that promises transformation too easily. There are enough books telling people that everything changes if they follow the system properly. I became more interested in what happens when life interrupts, when the burst of motivation disappears, or when you understand the lesson and still get it wrong on Tuesday.
That made the book less impressive in one sense. There are fewer grand answers.
I think it made it more honest.
It certainly made it more mine.
I started One Fight At A Time believing that writing a book required having something worthwhile to say, and I still believe that. What I understand differently now is that having something worthwhile to say does not mean knowing exactly what it is before you start.
I know more about how I write now.
I know I need to circle things before I understand them. I know I repeat myself when I'm trying too hard to make sure I've been understood. I know I'm better when I start with something real rather than an argument I'm determined to prove. I know plain words usually beat clever ones. I know something I worked hard on can still need deleting.
And I know uncertainty is not necessarily something that needs editing out.
The next book, if there is one, will probably begin differently because of all of this.
I will still make mistakes with it.
They will probably just be more advanced mistakes.
That seems fair enough.
Originally written in September 2026 as part of my submission of One Fight At A Time to Jessica Kingsley Publishers. Revised for chefstu.co.uk in November 2026.
Add comment
Comments