In this episode of the Ruby Rogues podcast Dave Kimura, Eric Berry, and Charles Max Wood discuss chatbots with Jamie Wright. Jamie will be speaking at Ruby Dev Summit in October.
Jamie is a professional nerd and independent contractor. He's been coding for 20 years mostly in Ruby. He's starting to get into Elixir.
Then Slack came out and he created Tatsu.
You can schedule it and it'll ask automated questions.
He's working on having it integrate with github, Harvest, Google Calendar, etc.
If there's a blocker, you should be able to create private conversations with the people who are blocked and add that to the standup.
When you sign up it adds a video link into your slack. Eric thinks this is pretty clever.
In Slack, the default action people should take when a bot is installed should be to DM the person who installed it.
Writing bots is "fun as hell."
Chatbots suck. We have the opportunity to improve an entire piece of the industry.
Many bots are command based bots. You say something and it responds.
Conversational UI's are really hard because they don't have any context or shared understanding of the world.
Every large company is working on one.
There are also lots of natural language processing services that you can use as well.
Before you start, you need to know your use case.
Where will your users be? What services do you want to provide?
At work? Probably slack.
Among friends? Facebook
Node has botkit. It's the most popular chatbot platform in the world.
Start with botkit, use the examples, then come back to Ruby.
Dave brings up building a chatbot for Slack that connected to VersionOne.
Data retrieval bots are another great place to start.
From there, you start answering the question of where things go.
Tatsu has been around for about 2 years and has existed pre-Slack.
Eric uses a Slackbot to get information about users who cancel or decline messages.
Chuck has done automatic posting to Slack with Zapier.
Chuck also mentions serverless with AWS Lambda.
Chatbots are a lot like webapps. They're text in, text out and process things in very similar ways.
Dave also brings up SMS bots as well with Twilio.
Jamie has thought about creating a web based standup bot for when Slack is down. Slack is a single point of failure for your bot if that's where it lives.
Slack gives you a lot of UI elements that you don't get in SMS.
From an end-user perspective, no. But Jamie does wish they'd revisit threading replies and separating conversations in the same channel.
It only took a handful of developers to build Slack.
You can call an api endpoint on Slack that gives you a websocket endpoint.
The events API sends webhook events to your server. It's easier to program against, but it can be slower. It may also be restricted on certain API's
Based on a Peepcode video with Aaron Patterson. You got a score based on your activity in Github.
Jamie recorded videos for a talk at Codemash.
It never actually became a thing, but it was a fun idea.
Jamie got into Ruby by going to a Ruby Koans talk by Jim Weirich.
This is what we put into the chat room after the Dr. Who reference...