Enjoying This Moment
I’m sitting at my computer on Sunday morning with “nothing” to do (I mean, I could always work, but my team is good about taking weekends off). This morning comes after 3.5 months straight of evenings and weekends working on the Avalon book (I’m talking 20+ hours/week on the book on top of the 50-60 hours/week I spent getting up to speed on my new job). The final push was this week, which I took as vacation from work (“you took vacation to work!” my wife likes to say…).
Last night, I produced the 2nd draft of my last 1st draft chapter (which I was happy to trim by 17 pages w/o losing anything useful) and composed comments on a 2nd draft of Ian’s chapter that was in my queue.
This morning, I took care of a reviewer comment that’s been nagging me, sent Ian my feedback and composed a detailed schedule of the rest of my day which consists of:
- wait for feedback on non-finalized chapters
- apply feedback and finalize my last two chapters (30-60 minutes)
- produce 2nd draft of book preface (1-2 hours)
- review anything Ian sends my way (1-2 hours)
- (maybe) review 1st draft of chapter from the WinForms 2.0 book (1-2 hours)
Compared to how I have been spending my time lately, that’s an extremely light day.
This book has been particularly difficult to write. Most of my writing has been on insights that I or the other members of the community have discovered in the use of the technology. These kinds of insights come after the technology is shipped and we’ve all had a chance to get to know it. Avalon, on the other hand, has a ways to go before it ships and the developer community is very small. Plus, some parts of Avalon don’t work very well or have changed significantly since I first learned about them. The consequence of this is that most of my writings on Avalon have had to have at least one massive overhaul as I a) learn the best way to think about them and b) update them to actually reflect the latest bits.
The rub is that by the time the book sees the light of day (it should be on the PDC show floor), the Avalon team will likely have shipped another version of the bits, obsolescing what Ian and I have worked like dogs to ship. Of course, we’ll post the errata and we’ll update the book for the Avalon RTM, but still, it hurts that most of you won’t be able to read the book when it’s a perfect match for the bits.
I get to read it, though, and I’ll tell you — right now, the book rocks. : ) And the reason it rocks? Ian and I have worked hard to make sure it does, of course, but it’s mostly been the internal and external reviewers that have done such a great job pointing out where we got it wrong. It’s tough to hear, especially when it means a complete chapter re-write (I just finished one of those last night), but I’m so happy with the results that I’m willing to love them anyway.
Now I’ve raised the bar impossible high, but screw that — I’m enjoying the moment…