Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
@seanwalberg
Water Boy, my robotic coworker
Sean Walberg <sean@ertw.com>
Infrastructure guy
National Football League
@seanwalberg
@seanwalberg https://www.flickr.com/photos/lizbrooks/2502106228/
Conversations
happen in private
@seanwalberg
We repeat
work.
Repeatedly.
@seanwalberg
We are
constantly
context
switching
when
solving
problems
@seanwalberg
Enter Chat
A transparent,
distributed, shared CLI
for your
infrastructure.
@seanwalberg
What is chat?
@seanwalberg
Good chat services have APIs
• Post messages to a channel
• Receive messages, both direct and group
• Send ri...
@seanwalberg
Easily POSTable status messages
@seanwalberg
Context and conversation
Here we are, talking about code, and then we learn:
Now we’re talking about fixing c...
@seanwalberg
@seanwalberg
General usage
robot.respond /git er done/i, (msg) ->
msg.send "Will do #{msg.message.user.name}!”
robot.hear ...
@seanwalberg
Pre-canned and custom scripts
@seanwalberg
Making JIRA suck less
@seanwalberg
Automate third party services
@seanwalberg
Troubleshoot in public
@seanwalberg
Long and complicated commands?
@seanwalberg
You know what didn’t work?
robot.respond /deploy consulator/i, (msg) ->
robot.respond /deploy node (.*) to (....
@seanwalberg
What if I
make a bot
and nobody
uses it?
(or how do I
get people
to use it?)
https://www.flickr.com/photos/vr...
@seanwalberg
Like a mullet, it needs a mix
@seanwalberg
A good bot…
• Helps people do their work
• Is fun to use
• Is easy to change
• Contributes to your company cu...
@seanwalberg
@seanwalberg
Reduce context switches
@seanwalberg
Teach them to fish.
@seanwalberg
Let people express themselves
Giphy got annoying quickly. “image me” is banned. We prefer “meme me”.
In-jokes...
@seanwalberg
Make it easy to change
@seanwalberg
Encourage acknowledgements
@seanwalberg
Behaviour modification
@seanwalberg
Peer Pressure As A Service
@seanwalberg
It can be a gateway drug
@seanwalberg
If you want me to stop talking, you’d
better ask some questions.
sean@ertw.com
@seanwalberg
Upcoming SlideShare
Loading in …5
×

Water Boy, my robotic co-worker

323 views

Published on

Slides for the talk I gave at DevOpsDays Toronto on May 27, 2016. This talk is about the use of ChatOps at the NFL and the Hubot based robot we've been working on.

Published in: Internet
  • Be the first to comment

Water Boy, my robotic co-worker

  1. 1. @seanwalberg Water Boy, my robotic coworker Sean Walberg <sean@ertw.com> Infrastructure guy National Football League
  2. 2. @seanwalberg
  3. 3. @seanwalberg https://www.flickr.com/photos/lizbrooks/2502106228/ Conversations happen in private
  4. 4. @seanwalberg We repeat work. Repeatedly.
  5. 5. @seanwalberg We are constantly context switching when solving problems
  6. 6. @seanwalberg Enter Chat A transparent, distributed, shared CLI for your infrastructure.
  7. 7. @seanwalberg What is chat?
  8. 8. @seanwalberg Good chat services have APIs • Post messages to a channel • Receive messages, both direct and group • Send rich attachments (or open protocols)
  9. 9. @seanwalberg Easily POSTable status messages
  10. 10. @seanwalberg Context and conversation Here we are, talking about code, and then we learn: Now we’re talking about fixing code And now we all know it’s fixed
  11. 11. @seanwalberg
  12. 12. @seanwalberg General usage robot.respond /git er done/i, (msg) -> msg.send "Will do #{msg.message.user.name}!” robot.hear /demo on (.*) is at (.*)/i, (msg) -> # Access the message itself robot.router.post "/hubot/say", (req, res) -> # respond to POST from the outside httprequest = msg.http(…) # call out
  13. 13. @seanwalberg Pre-canned and custom scripts
  14. 14. @seanwalberg Making JIRA suck less
  15. 15. @seanwalberg Automate third party services
  16. 16. @seanwalberg Troubleshoot in public
  17. 17. @seanwalberg Long and complicated commands?
  18. 18. @seanwalberg You know what didn’t work? robot.respond /deploy consulator/i, (msg) -> robot.respond /deploy node (.*) to (.*)/i, (msg) -> Factoids Tracking team demos
  19. 19. @seanwalberg What if I make a bot and nobody uses it? (or how do I get people to use it?) https://www.flickr.com/photos/vr/2364953428/
  20. 20. @seanwalberg Like a mullet, it needs a mix
  21. 21. @seanwalberg A good bot… • Helps people do their work • Is fun to use • Is easy to change • Contributes to your company culture
  22. 22. @seanwalberg
  23. 23. @seanwalberg Reduce context switches
  24. 24. @seanwalberg Teach them to fish.
  25. 25. @seanwalberg Let people express themselves Giphy got annoying quickly. “image me” is banned. We prefer “meme me”. In-jokes are fun to add.
  26. 26. @seanwalberg Make it easy to change
  27. 27. @seanwalberg Encourage acknowledgements
  28. 28. @seanwalberg Behaviour modification
  29. 29. @seanwalberg Peer Pressure As A Service
  30. 30. @seanwalberg It can be a gateway drug
  31. 31. @seanwalberg If you want me to stop talking, you’d better ask some questions. sean@ertw.com @seanwalberg

×