1.
northfieldit.com@SeanWalbergJoin us this week on slack.prdcdeliver.com
Water Boy, my robotic coworker
Sean Walberg <sean@ertw.com>
Infrastructure guy
Northfield IT

2.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg

3.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
https://www.flickr.com/photos/lizbrooks/2502106228/
Conversations happen in private and
in different places

4.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
We repeat
work.
Repeatedly.

5.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
We are
constantly
context
switching
when
solving
problems

6.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Enter Chat
A transparent,
distributed, shared CLI
for your organization.

7.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
What is chat?

8.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Enter ChatOps

9.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
I’m not kidding!
 It’s familiar
 It’s asynchronous
 It’s also synchronous!
 It can run on anything
 It’s auditable
 It’s searchable
 It’s fun!

10.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Our work happens in the open!

11.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Training docs? We have history!

12.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Documents are a future lie
Our chat history is always current.
It updates as we discuss our environment.
Chat really is a “living document”.

13.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
The two sides of ChatOps

14.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Good chat services have APIs
 Post messages to a channel
 Receive messages, both direct and group
 Send rich attachments
(or open protocols)

15.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Easily POSTable status messages

16.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Context and conversation
Here we are, doing our work, then…
Now we know who has it, and can discuss if need be.
And now we all know it’s fixed

17.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Push information, when it matters

18.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg

19.
northfieldit.comJoin us this week on slack.prdcdeliver.com @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

20.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Pre-canned and custom scripts

21.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Making JIRA suck less

22.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Automate third party services

23.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Troubleshoot in public

24.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Long and complicated commands?

25.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
You know what didn’t work?
robot.respond /deploy consulator/i, (msg) ->
robot.respond /deploy node (.*) to (.*)/i, (msg) ->
Factoids
Tracking team demos

26.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
What if I make
a bot and
nobody uses
it?
(or how do I
get people to
use my bot?)
https://www.flickr.com/photos/vr/2364953428/

27.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Like a mullet, it needs a mix

28.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
A good bot…
 Helps people do their work
 Is fun to use
 Is easy to change
 Contributes to your company culture

29.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg

30.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Reduce context switches

31.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Teach them to fish.

32.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Let people express themselves
Giphy got annoying quickly. “image me” is banned. We prefer “meme me” and emoji.
In-jokes are fun to add.

33.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Make it easy to change

34.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Encourage acknowledgements

35.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Behaviour modification

36.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Peer Pressure As A Service

37.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
It can be a gateway drug

38.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Where to start?
 Start with your team.
 The product doesn’t matter.
 Be careful of “too much fun”
 Let it expand organically

39.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
Let’s collaborate over chat! Right now!
 Prairie Tech Slack – http://slack.prdcdeliver.com
 Talk with attendees and speakers (#our-robotic-
coworker)
 After the conference this becomes a regional tech
discussion – learn about meetups, jobs, get help
 Invite your cow-orkers and friends

40.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
https://github.com/WpgTech/gilfoyle
https://github.com/WpgTech/erlich

41.
northfieldit.comJoin us this week on slack.prdcdeliver.com @SeanWalberg
sean.walberg@northfieldit.com
@seanwalberg
If you like ChatOps and automation, I’d like
to work with you. Come to the Northfield
booth, we’d love to learn more about you.