How GitHub Does Devops - Speaker Deck

Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

Reference: https://searchengineland.com/bidding-competition-really-worth-258398

Slide 3

Slide 3 text

Reference: http://www.dailystar.co.uk/tech/news/591737/Nokia-3310-launch-phone-relaunched-month-battery-new-design-MWC-2017

Slide 4

Slide 4 text

How GitHub Does DevOps Brent Beer @brntbeer Solutions Engineer

Slide 5

Slide 5 text

What is DevOps?

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

HTTP://WWW.EWEEK.COM/ENTERPRISE-APPS/SLIDESHOWS/DEVOPS-5-SIGNS-ENTERPRISES-NEED-TO-UNITE-THE-DEV-AND-OPS-CAMPS.HTML

Slide 8

Slide 8 text

REFERENCE: HTTPS://AWS.AMAZON.COM/DEVOPS/WHAT-IS-DEVOPS/ “DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. This speed enables organizations to better serve their customers and compete more effectively in the market.”

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

Organize

Slide 11

Slide 11 text

Tools

Slide 12

Slide 12 text

Tools Reference: https://hbr.org/2015/01/why-a-messy-workspace-undermines-your-persistence

Slide 13

Slide 13 text

Tools Reference: https://en.wikipedia.org/wiki/The_Paradox_of_Choice

Slide 14

Slide 14 text

Tools Reference: https://www.gardenbuildingsdirect.co.uk/blog/garden-shed-garage-organising-ideas/

Slide 15

Slide 15 text

People

Slide 16

Slide 16 text

People

Slide 17

Slide 17 text

People Reference: https://www.youtube.com/watch?v=KndSVsY5HWM

Slide 18

Slide 18 text

People Reference: https://www.youtube.com/watch?v=KndSVsY5HWM

Slide 19

Slide 19 text

People

Slide 20

Slide 20 text

Step 1 • Grab some tools your developers are using today. Lay them out on the table and remove some if need be, but keep some even if they completely overlap (CI tools may be an easy one to think about). • Additionally, group some people together, but let them stay ﬂuid. People may move to new tools or new tools will move to people.

Slide 21

Slide 21 text

Communicate

Slide 22

Slide 22 text

Reference: https://devops.com/devops-culture-mind-matter/ “Even if an org is full-on DevOps, there is still the requirement of cross-team communications to make sure everyone understands what is going on. […] Increase communication, not chatter.” - Don Macvittie, DevOps.com

Slide 23

Slide 23 text

Reference: http://itribesolutions.com/email_appending.php

Slide 24

Slide 24 text

Reference: https://slackhq.com/email-meet-slack-slack-email-1d5b36a68e79

Slide 25

Slide 25 text

Reference: http://www.blackberryos.com/content/verizon-z10-owners-heres-why-you-cant-download-whatsapp-blackberry-world-yet-5651/

Slide 26

Slide 26 text

Reference: https://www.createful.com/2017/beware-slack-trap/

Slide 27

Slide 27 text

Reference: https://www.forbes.com/sites/theodorecasey/2017/09/08/new-slack-clone-highlights-a-generational-divide-in-chat/#6aad4cfe7600 “Slack is easy for me because I grew up with AOL Instant Messenger and chat rooms. I can make sense of it. It must be even easier for kids who grew up with texting.” - Theo Miller, Forbes Contributor

Slide 28

Slide 28 text

Asynchronous best practices • Only use private messages when you absolutely have to, e.g. for privacy, legal, HR, or other reasons that make a discussion sensitive. • NEVER EVER do this: “@ username can i ask you a question?” Just ask the question. • When you respond to someone’s question in chat, unless it’s 30 seconds after they asked, @ them by username • Expect chat to be asynchronous, people will respond to you when they are able. • Don’t stare at your chat client all day, it’s easy to fool yourself into thinking replying to chats is the same as being productive. Reference: https://medium.com/@danielhengeveld/best-slacktices-e0cdfc050dd2

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

Step 2 • Choose to communicate more asynchronously. Be more open and let your coworkers bond and share ideas as often as possible. If they struggle with the new forms of communication, be patient and have empathy. Help them out.

Slide 35

Slide 35 text

Develop

Slide 36

Slide 36 text

Workflow Prerequisites • You’re using Git • You know your tools you planned on step 1 are involved • You want to do code review (automated and/or peer) • You want to deploy and iterate as fast as possible

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

Tools Reference: https://www.gardenbuildingsdirect.co.uk/blog/garden-shed-garage-organising-ideas/

Slide 42

Slide 42 text

Step 3 • If you pick a platform for combining all your tools, people, and working with good communication that doesn’t allow you to stay ﬂexible and make these changes, you will never reach your full potential.

Slide 43

Slide 43 text

Next steps We just talked about a lot of things.

Slide 44

Slide 44 text

Take a deep breath

Slide 45

Slide 45 text

Recap • Step 1: Bundle your tools together to give your people choice. People also need to know how to move teams or move tools to their team • Step 2: Choose a communications platform that is open and promotes good asynchronous communication. This tool should also integrate well with some other tools from step 1. • Step 3: Pick a platform that allows you to implement steps 1 and 2 ﬂawlessly, and allows you to grow as well. • (Bonus) Step 4: When the moment is right, revisit steps 1-3. Iterate and improve