Upgrade to Pro — share decks privately, control downloads, hide ads and more …

let_bots_pick_up_the_slack.pdf

 let_bots_pick_up_the_slack.pdf

Cool stuff happening in Colima, Mexico.

Victor De la Rocha

July 12, 2018
Tweet

Other Decks in How-to & DIY

Transcript

  1. What are bots? (An Introduction) Bots are non‑human users of

    a messaging service (e.g. Slack , Facebook , Telegram , etc.) which interact with human users or third‑party services (e.g. Google Sheets , weather apps, etc.) in an automated way.
  2. Why would I want to use a bot? bots free

    humans from low‑skill, repetitive, undesirable tasks bots are fast, reliable, and less error‑prone than humans conversations (as interactions) provide an intuitive UX for humans
  3. Bot basics: tools Missions ‑ third party service (no coding

    required) Hubot ‑ code‑based, and you're on your own Botkit ‑ code‑based, but with lots of help! code‑based hosted plug‑and‑play Missions X X Hubot X Botkit X X
  4. Bot basics: tools (continued) Missions third‑party service (no code) Hubot

    code‑based solution needs to be hosted somewhere else Botkit code‑based solution well‑documented lots of integrations (right from the beginning), i.e. "quick starts" needs to be hosted somewhere else easy integration with Glitch
  5. Bot basics: hosting Heroku Pros: robust version control easy to

    work with locally, deploy remotely Cons: might go to sleep (free version) integration issues between environments with Slack API need dedicated IP pointing to your local environment (using ngrok , localtunnel , etc.)
  6. Bot basics: hosting (continued) Glitch ‑ code in the cloud!

    Pros: easy to get up and running easy to pair program remotely Cons: lack of robust version control (it does weird things)