So What About That Book, Allan?
This is a post I’ve been meaning to write for some time and one of the hardest. I’m not sure where to begin, so I’ll start somewhere.
Some of you may know I’ve been working on the book Mission Critical SQL Server for a long time … way too long. Sometimes the most well intentioned plans take a left turn at Albuquerque. Let me explain.
Change, Change, Change
I wanted to write the spiritual successor to my SQL Server 2005 book – one big honkin’ volume that would be the reference for all things business continuity. In theory it was an awesome idea.
At the time I started writing there was no Linux, virtualization was still on the rise, and not many were using any cloud provider. We all know the landscape today; so much has changed. That has had its own negative as well as positive impact. There are completed parts that I’ve probably written over again or revised four or five times but have never seen the light of day because every time I thought I was there, something else needed to be added. Multiply that over multiple operating systems, SQL Server versions, and environments (physical, virtual, and cloud) … it became paralyzing.
I can’t tell you how many hours I’ve stared at a screen with Word up and nothing was coming out. Perfection is the enemy of done.
Being Honest
At some point in the process, the book became an albatross and quite frankly, I felt a lot of shame around it not being done. The more time went on, the bigger the shame. I felt like a failure. The book became a mythical, larger than life “thing” overshadowing so many other things in my life. I started to think it would never live up to expectations – real or perceived – which made me shut down. Disappointing people is a terrible feeling and on top of it all, I also gave my detractors plenty of ammo for it not being done. Any time someone would ask me about I had a sense of dread. All of this felt like a 10,000 pound weight on my shoulders.
Last year I decided to do get some help – especially with the shame. For the first time in a long time, I can say I am in a good head space with the book. Recently, I’ve been able to start writing again which has been very freeing. I’ve approached someone to help me with the book, too. One thing as I’ve gotten older is that I’ve realized sometimes you just can’t do it all. This book has been one big life lesson in how not to go about things. If I could screw it up, boy have I with this one.
I’m also learning to be kinder to myself. I have impossibly high standards that can be unrealistic from time to time. It’s ok to be human, not superhuman.
The New Timeline
I know many of you are wondering: is the book ever going to be finished? Yes.
The realistic and, most importantly, achievable goal is to have it done as soon as possible after the release of SQL Server 2022. Since there is no set release date, I can’t say when that is but realistically if it hits the shelves later this year, I’m looking at sometime early in 2023. It won’t just be about SQL Server 2022 but ensuring the latest release is covered makes a lot of sense and keeps it relevant for quite some time.
One thing that I am still debating: instead of one big honkin’ volume, release it in smaller, digestible chunks. Is this something you would want or prefer? It may also allow me to get sections out earlier. Let me know below.
That’s it. I have felt awful about not saying anything or answering questions but understand it was not because I didn’t want to; the shame prevented me from doing so. This blog is me finally putting the shame behind me to move forward and remove the weight from my shoulders.
Allan, I think releasing the book in smaller chunks is a great idea. I’ve been really happy with Manning’s MEAP program, where chapters are released as they are completed. It’s nice to have something to look forward to and I find it easier to digest in smaller chunks.
Chunks is definitely where I am leaning and consensus so far from Twitter comments.
If lean towards chunks myself. Easier to then update those in the future
Thanks, Steve.
I second/third/Nth the idea of releasing the book in chunks!
I’m so, so, SO glad you’ve come around to being kinder and more understanding to yourself. Your story here is a very, very familiar one for me. The longer I live, the better I understand myself and others, and how critical it is to help and heal (ALL of us). Again: I’m so very happy for you.
Secondarily, I’m happy that you’re making progress on your book again. I know how good something like that can be. Well done, friend.
Thanks, Jen. I’d like to think I’m getting wiser (not necessarily smarter – ha) as I get older.
Hi Allan,
I agree with the growing “chunks” consensus. I’m trying to chew my way through an 800 page C#/.NET book right now and sometimes the sheer size is overwhelming. Good to take it in stages. In any form though, put me down for a signed copy! 😀
Bill
Thanks, Bill!
And here I was hoping you were writing the definitive book on Rush rather than on SQL Server. 🙂
Seriously though, this post rings true with a similar book-related experience of mine. The line about learning to be kinder to yourself is particularly resonant.
Best wishes for continued progress with the book at whichever rate works best for you!
There are enough books on Rush out there 🙂
This is not my first book but the hardest. Sometimes you swing and miss, but that isn’t a strikeout.
I will throw another vote on the pile in favor of chunks. I will also gush enthusiasm for Manning and their MEAP program.
I first learned about Manning through PASS and the SQL Server Deep Dive books. I love Manning’s approach, and I’ve been very impressed with their staff. The MEAP program is very good for most topics and authors because it doesn’t just allow but actively encourages active feedback from interested isers/readers.
As I’ve said before, you are one of the smartest people I know of on the topic. You have great intelligence, offer great insight and have massive experience. Perfect is the enemy of done. Go with the MEAP if you can, let the community help you!
Thanks, Pat. Manning is not publishing my book and I was doing something similar in a way 10 years ago. I’m not decided on what it looks like yet.
As one of the original “pre-orders”, I’m happy to see you’re getting on with an ever evolving application stack.
While there’s certainly an argument for breaking it upp in modules, I can only offer my limited knowledge of the subject by plaaying relative newbie.
So aside from the basic explanation of how it works, I’m quite interested in how to set it up when you hasven’t full control over the networking, troubleshooting and operating systems. This doesn’t include topics like operations , upgrades, machine migrations and the like.
I recall you offered a basic outline in the past, that might help understand what it’s covering when it comes out.