rickumali (130) [Avatar] Offline
#1
I've decided to write a short blog-type post every week here on this forum. These posts are exclusive to this forum, and they will primarily be about the writing of the book.

Revisions are an arduous part of writing for a publisher. It's only now, deep into this project, that I can fully appreciate just how arduous.

This week I've been writing Chapter 12, which is hard enough (it's the chapter on understanding Git remotes). But in between this new writing is me revising Chapters 08 and 09, chapters on branching and merging. Talk about context switching!

I'll put it this way: writing new chapters is "more fun" than rewriting old chapters. Moving text, removing text, and changing text to fix older chapters is "not so fun." Sort of like programming, really. It's always more fun to start with a clean slate, than to wrestle with legacy code.

Maybe that's how I should think of revisions: like "text support" or "text maintenance" (substitute tech for text). Revisions are tune ups. Ultimately, revisions make the book better, and that's what I have to keep in mind.

Thank You for reading!