Today’s Friday Fun post, as most of these are, is a little silly and a little educational. Because I obviously am avoiding getting any real work accomplished, I worked on a little project that would add a border around a string of text. I often write formatted text to the screen to display information and thought it would be nice to be able to add sometime of border.
At long last it is finished! Don Jones and I have recently published the first iteration of The PowerShell Scripting and Toolmaking Book. This project was first announced in January 2017 with an early release program. The first edition was finished and in reader’s hands by the end of February 2017. We appreciate all of your enthusiasm and support but I also realize there are some questions around this title so I thought I’d touch on them.
What about the Toolmaking Month of Lunches book?
This is perhaps the number one question. Don and I refreshed the Learn PowerShell in a Month of Lunches book published by Manning, primarily to reflect a few minor changes in PowerShell v5 and to at least recognize that PowerShell is moving into the open source world. In terms of learning PowerShell from the very beginning the essential fundamentals are unchanged which is I think of the book more of a refresh than revision.
We considered doing the same with the Toolmaking book. But there was no real technical requirement to do so. PowerShell had not changed enough that the book was obsolete. It is still very relevant. But there were things Don and I had long wanted to do with the subject that couldn’t fit into the Month of Lunches model. So we decided to venture off on our own.
Who or What is LeanPub?
You may wonder why we didn’t simply publish again with Manning? They are great people to work with and they offer one of the top line-ups when it comes to tech books you should have on your shelf. However, there is a tough challenge facing Manning, and other tech publishers: how to keep up with a rapidly changing world. Traditional book publishing is a long process so that you end up with a properly produced and edited book. When we went 3 years between software releases that worked just fine. But now, at least in our world, we get new releases on a much faster cadence. it is not uncommon for a tech writer to finish a manuscript only to have a new version come out before the book can be published.
So if that world is agile, we need to be as well. Think of LeanPub as a “books as a service” platform. Don and I could write the book, with the capable technical assistance of Michael Bender, and publish as we went along. Did someone find an error? Was there a formatting goof? We can fix it and publish a new edition. In fact, the version you can buy on LeanPub is considered our “Forever” edition. When you buy a copy you are buying into the future. At some point we may add new content or fix errors. We’ll republish and you get that new version. LeanPub offers a variety of digital and ebook formats. I personally love the Send to Kindle feature. And interestingly the majority of readers are opting for the PDF format.
Oh, and all of the book’s sample code and exercises is published as a module (PowerShell-Toolmaking) to the PowerShell Gallery.
Can I get a hard copy?
The whole point of using LeanPub is to quickly publish new versions as necessary. But some of you like holding a real book. You can, but here’s the deal. First, you can order from Amazon. If you pay close attention you’ll see that right now this is labeled as a First Edition. Hard cover editions will be essentially point-in-time snapshots of the “forever’ manuscript. At some point we may make enough changes or add enough new content that warrants a 2nd edition. If you own a hardcopy 1st edition and want the content from the new edition, you’ll need to purchase it. That’s why the hardcover edition is offered at a lower price point. Owner’s of the LeanPub “Forever” edition don’t have to worry. Of course, feel free to buy both!
If you are interested in the Forever edition, head over to http://bit.ly/PSToolmaking and order a copy. If you scroll to the bottom of the page you’ll also see that this title is being offered as part of a bundle with other PowerShell books. A lot of people have been taking advantage of that offer.
Finally, we’d sincerely appreciate any kind words you can spread about the title. One drawback to not using a publisher like Manning is that we have no advertising or marketing budget. We rely 100% on word of mouth. So any blog posts, Amazon reviews and even a simple tweet would help.
If you have questions or comments about the book, using the feedback and discussion features on the book’s LeanPub page.
Thank you for support.
Recently I posted a PowerShell tool for creating a GitHub repository. In continuing my exploration of the GitHub API I wrote another PowerShell tool to create a GitHub gist. A gist is simple way to store and share snippets or code samples. I use them to share simple PowerShell scripts or other works that aren’t full blown multi-file modules. Now I can create these gists directly from PowerShell and the PowerShell ISE.
Yesterday I showed you a class-based PowerShell script. My intention was to have a little bit of fun and teach you the basics of using a class. But what I gave you was really just the first step. If you wanted to create an actual tool around a class, you will most likely want to package it into a module. I’ve done that with my Christmas class. Let me explain why and the changes I made.
I’ve been diving a bit deeper into the Nano waters now that Windows Server 2016 is out the door. As I deployed a few servers I realized there was a potential long-term management issue. During the technical preview, Nano installations were recognized by their Tuva designation. But now, a Nano server is just another Windows Server 2016 installation. So how can I tell if a server is a Nano installation? Here’s the solution I came up with.