On Monday, January 16th, the pre-sale for my Docker Recipes for Node.js Development ebook opens up. As I said in the last post, I need to sell 100 copies in the pre-order period, to ensure the book moves forward.
But before the pre-sale starts, though, I wanted to give you a sneak peak at the first bits of content that I’ll have ready, for the pre-sale.
Writing That First Recipe Was Difficult
I mentioned previously that the first bits of content would likely be around debugging, and that has held true in the content I’ve worked on, so far. But things didn’t quite work out the way I had expected.
When I sat down to write the first recipe, I had intended to write a small bit on how to use the built-in Node.js command-line debugger within a container. But after doing that and asking a few friends for some feedback, I realized that I had not shown enough to get a sense of what the book would be like.
So I decided to write a few additional recipes to get a better sense of the flow and layout, and things started changing pretty quickly.
I’m still not completely happy with the writing at this point, but I think the recipe structures are starting to solidify, and I want to give you a peak into what that content will look like.
A Preview of Debugging In A Container
The content around debugging will likely be it’s own “Part ##” in the book, since I already have 3 recipes basically written as rough drafts and may one or two more.
The opening for that part of the book is roughly outlined, here:
Within the recipes (chapters), there will be a short scenario description to help you understand when the recipe in question would be best suited.
There will be recipe listings, of course, which are meant to be copy-and-paste chunks of code and configuration, to solve a specific problem.
And each recipe will come with cooking instructions, to provide additional description and detail on how to use the code and configuration found in the recipe listings.
Depending on the specific recipe, there will also be some additional detail about specific commands, or notes on items related to the recipe in question. I’m trying to keep the book as short as possible, while still providing enough information to be valuable.
This won’t be an introduction, but a collection of solutions for someone familiar with Docker, but not yet comfortable using all their favorite development tools and techniques within Docker.
To Be Edited … Heavily
I do have a fair number of pages written already, but I don’t expect the content and structure that I’ve shown to be the final form of the book. Remember, the goal of the pre-sale is to get feedback, input and ideas from early readers. That’s where you come in.
The pre-sale starts on January 16th, and ends on the 31st.
If you buy the ebook in that period, you’ll have the opportunity to provide direct feedback on how to best move forward with the content and structure. You’ll receive updates to the book as they happen. And you’ll get much more content than just the ebook (some screencasts, cheatsheets, etc) at a significantly reduced price.
Stay tuned in to the pre-sale and how it’s going, by joining my mailing list (below). And be ready for the pre-sale launch – it starts in only a few days!