I just blogged about
starting a new writing project. Independent of whether I go public on a Wiki or do it the old fashioned way, here are the potential writing projects I'm thinking about.
Project A - Joint Avalon/Indigo project with ChrisAn
Either a single book or a jointly authored two volume book on the experience of writing Windows programs in an Avalon/Indigo world.
Pros
- A chance to work with ChrisAn
- My coauthor's availability constraints are similar to my own
- It would force us both to really grok each other's technology and hopefully come up with a coherent story that incorporates both.
- I'd buy and probably read this book if I weren't involved in the project
Cons
- The shape of the book is the least formed (at least in my head)
- Chris is already planning on doing an Avalon book, so I'm loathe to derail him
- Unknown how our writing styles would mesh
Project B - New book that would subsume my CLR book and include integrated Indigo and maybe even (gasp) COM
A book on how code loads, runs, and interacts on the platform I call home.
Pros
- The most logical successor to what I've written to date
- A chance to "fix" the stories from my previous books - I think of this project as Essential COM/XML/NET 3rd Edition
- The most architectural of the lot - I've been wanting to try to write for the "upscale" market :-)
- It would most likely be a solo project which is one of my motivations for writing
- I'd buy and read this book if I weren't involved in the project
Cons
- Solo projects get lonely, so I'd need an angel reviewer
- This book would likely be even less tutorial-like than anything I've written before, so readers may be disappointed if they're looking for something super-practical
Project C - Essential .NET Volume 2 - Indigo
The obvious technology book on Indigo - probably co-authored with one or more friends.
Pros
- A chance to work with friends and maybe get some new blood into the authoring game
- I have a lot of passion for the story and would love to tell it
- I would stop getting those "where's Essential .NET Volume 2" emails
Cons
- It's what people expect me to do
- I run the risk of alienating friends and co-workers if I don't give their feature adequate coverage
- I think the story is pretty baked (in my head at least), so the risk of getting bored is non-zero
- I'd buy and but probably only scan this book if I weren't involved
Project D - Essential .NET Volume 1, 2nd Edition
Update my last book for Whidbey/Orcas.
Pros
- There are a couple of chapters I'd love to rewrite
- If I target Whidbey, the technology would be out this year (and maybe the book would too)
- If I skip Whidbey and target Orcas, there'd be sufficient evolution to easily warrant a new edition. Doing a Whidbey edition is as much about me wanting to rewrite a few chapters as it is feature growth.
- The amount of work is potentially smaller assuming I can stop myself from rewriting the whole thing
Cons
- Least aligned with where my head is at on a day to day basis
- I'd buy this book if I weren't involved, but I don't know if I'd ever crack it open
- I'd probably need a co-author and it's not clear who I'd work with
Project E - Essential COM, 2nd Edition
Keep the first chapter (or perhaps 2) intact and rewrite the back 2/3rds to take into account contexts, the catalog, and remove references to the class store and NT5 :-)
Pros
- People love this book and continue to buy it. It's painful that at least one chapter (Apartments) is woefully out of date.
- It would be a lot of fun to write the sidebars on how the CLR and Indigo improved (or made worse) features and characteristics of COM
- The Raymond Chen crowd ain't going away anytime soon
- COM is (still) love
- I'd buy this book and read it immediately if I weren't involved in the project
Cons
- I run the risk of ruining a book that a lot of people love. Petzold should have stopped at the 3rd (or maybe 4th) edition of Programming Windows.
- The project has the least practical use for the generation of programmers entering the industry now
Comments/flames welcome.
Posted
Feb 26 2005, 10:32 PM
by
don-box