1x04 Chatbots for the Conversational Interface
This issue is a little self-serving since the chatbot book is out. Sorry in advance. You can skip it, if you don't care. No hard feelings. The next issue will focus on John Galton, Timothy Leary, and the failed promise of computer libertarianism.
Way back in March of 2017, we did a podcast episode on the Microsoft Bot Framework. Shortly thereafter, I (Michael) started working on a book about how to build chatbots with the Bot Framework Node.JS SDK. 2 years, a dozen speaking engagements, two rewrites, and countless tweaks later, the book is officially finished. It was a long road, and I've learned that writing a book is easy, but finishing a book is hard. A lot has happened in the last two years, and certainly a lot is still happening in the conversational interface space, so I wanted to take this issue of the newsletter to not only announce the book, but to also details some of the exciting innovations that have been continuing in the chatbot space.
Something about chatbots just spoken to me. It wasn't a new technology, but it was a rising one, and I felt I could make my mark as an expert in this niche, but growing field. A lot of my earlier blog posts began to center on the Bot Framework, and eventually, I found myself awarded the Microsoft MVP status, and was able to make a trip out to Bellevue. It was here I was able to officially meet Gary Pretty and James Mann: Two high profile Bot Framework communicators from the community.
Just prior to the MVP Summit in Bellevue; however, I began writing the aforementioned book on the Bot Framework. I was probably 2/3rds of the way through it when Microsoft announced via a PGI call that the Bot Framework SDK v4 was coming out, and it was changing an awful lot. I cringed slightly, knowing that I was going to have to rewrite large portions of the book, and unsure if I had the capacity to do it. By the time Microsoft Build came around (where the SDK v4 was announced), I had decided to continue forward. This would be the first of two rewrites, as later changes between preview and GA also required some fine-tuning.
Throughout this process, I had about 7 speaking engagements about chatbots on the East coast region--from code camps to regional conferences like SyntaxCon. While starting to wrap up the book, I worked with an acquisitions editor at O'Reilly making changes to align it with O'Reilly's vision. The book was accepted, I made several more revisions during the contract formation, agreed to a bunch of dates, worked hard to get the chapters ready, signed the contract, and then watched as O'Reilly pulled the contract on the book two days before I was set to deliver the first two chapters and receive the first advance. The last minute rescission sucked, but not because of it getting pulled. I was set to donate the proceeds to autism research, so I was disappointed in that outcome (side note: my acquisitions editor was top-notch during this process, and continued to promote some of my other work even after the contract was pulled).
Despite that setback, I was receiving interest from several other publishers, including Packt. But I decided to reach out to Rob Conery of Big Machine to discuss some of the indie publishing he had been doing. I have become a big fan of indie publishing over the last few years, including email newsletters like Sentiers and small print magazines like Logic, Regeneration, and Offscreen. Some of the best technology books I've read over the past two years have been from self-publishing or indie publishers. Rob convinced me that I should have stuck with my initial instinct, and handled the process myself. I decided to go the indie route, mostly because I've been slowly creating a non-profit meant to empower human decision-making with technology. This particular non-profit is centered around technology support for initiatives in neurodiversity and climate change.
It was a long, hard road. Multiple revisions gave way to upgrading code which gave way to copy-editing, technical reviewers, and indexing. Somewhere along the way, I needed to learn LaTeX. At the end of the day, the book was finally finished, and sales for the book go to support research in autism and neurodiversity, which makes it a bit of a passion project for me, and makes up for the loss when the book was associated with O'Reilly.
If you've read this far, and you're interested in the book, reply to this email. The first 20 people who respond will get a free PDF copy of the book, and a thank you. I couldn't have done this, and Bill and I wouldn't be able to continue all of these passion projects without you. If you like the book, feel free to drop it an Amazon review.
Also, I'd liked to thank Bill for allowing me to hijack this issue to promote the book. He's often the unsung, behind-the-scenes guy with most of these projects--whether editing, audio, ideas, etc. --Michael Szul & Bill Ahern
The Bot Builder Community
When I was selected a Microsoft Valued Professional, it was actually for the Developer Technologies category--even though a lot of the work I was doing was with the Bot Framework. When I finally made it to Bellevue for the MVP Summit, I was able to meet a few guys in the AI category that were there specifically for the Bot Framework: Gary Pretty and James Mann. Several months later, Gary, James, and Arafat Tehsin put together the Bot Builder Community on GitHub, and invited me to collaborate. Gary has built out a really mature offering on the .NET side (including Alexa and Google Home adapters), and I'm slowly building out the Node.JS side (starting with middleware and dialogs for NLP). We've even received some collaboration with Microsoft employees. If you're looking to create chatbots, this is probably the community you want to be involved in--especially if you're more about the creation process. --MS
Things Tagged with "chatbots"
Bot Framework Tutorial Series
Bill and I have been trying to tackle all forms of media when it comes to creating informative content. It started with the Codepunk web site, and then continued with the podcast (which is primarily Bill doing all the hard work). We have this newsletter, of course, but we also started producing some tutorial videos. I've actually cut down on my speaking engagements a lot in order to focus more on this newsletter and the video tutorials. We started with tutorial videos on the Node.JS SDK v3, and then eventually upgraded to SDK v4. We even started to include videos on the MSBot tool, LUIS, Chatdown, and the QnA Maker.
Terreux Peach Sour Blonde Ale
The Breury's Terreux is a peach sour blonde ale in a 750ML bottle. Sours vary in strength when it comes to both ABV and sourness, and this one is no exception. This beer sits at about 7% alcohol and is one of the more sour beers I've tasted. The sour almost eliminates the taste of alcohol, but allows the peach to come through. I actually didn't finish this bottle on the first day, as it was late into the night, but I sampled what was left over the next day, and the sour was enhanced even more.
This is more for fans of sours and gose than casual drinkers, as the flavor profile might overpower some people's taste buds. --MS