Rub Some Ops on it

Ignite Talk for DevOpsDays MSP:

Building software is hard. Building maintainable quality software is incredibly hard. You know what else is hard? Running software. Operations has learned quite a bit from the development side of the house, a solid Ops person understands the basic principles of software development. But the reverse should also be true for developers. Coming from the perspective of someone who's done both, operations gives you an interesting view on how to run and ship software. Operations forces you to become an expert in recovering from failure. How to debug a problem when the only data you have are symptoms of that problem. It's a constant loop of continuous improvements to prevent the same problem from happening again. It's risk assessment, if something is a high risk how can you reduce that risk and still accomplish the desired goal? Operations requires understanding the impact of a change to your system, it could be the difference in shipping the nastiest hidden regression your software has ever seen versus shipping the new hotness feature that becomes it's number one selling point. But the most important thing developers can learn from operations is that everyone has the same goal, to ship and run maintainable quality software for your customers.

Transcript

1. Rub some Ops on it! Andy Fleener Software Engineer
2. Level up your Ops skills Debugging code? - Rub some Ops on it! ! Worried about something risky? - Rub some Ops on it! ! Production is down? - Rub some Ops on it!
3. Debugging
4. Step 1. Understand it Debugging
5. Step 1. Understand it Debugging Step 2. Reproduce it
6. Step 1. Understand it Debugging Step 2. Reproduce it Step 3. Fix it!
7. Risk Management
8. How risky is the change? What’s the worst that could happen? !
9. How risky is the change? What’s the worst that could happen? ! What happened to all my data‽‽!!11one
10. Can you reduce the risk? Let’s wrap this in a feature flag
11. Code smaller Seriously do less!
12. Code smaller Seriously do less! ! Release smaller changes more frequently
13. Failure
14. Internal failure The burning ring of SOA
15. Can this app function if the authentication service is down? Expecting internal failure
16. External failure I didn’t get my password reset email!
17. Expecting external failure Redundancy FTW!
18. Continuous Improvement
19. Thanks! @andyfleener codinginthecrease.com