humpty dumpty a story of api devops gone wrong (emily dowdle)

HUMPTY DUMPTY DEVOPS

HUMPTY DUMPTY | A Story Of DevOps Gone Wrong

Emily Dowdle // emilydowdle.com

Humpty DumptyA Story of DevOps

Gone Wrong


Here’s som example text



Emily Dowdleemilydowdle.com@editingemily





Humpty Dumpty sat on a wall, Humpty Dumpty had a great fall. All the king’s horses and all the king’s menCouldn’t put Humpty together again.

Humpty Dumpty




You see, Humpty is a deploy.





Humpty Dumpty sat on a wall, Humpty Dumpty had a great fall. All the king’s horses and all the king’s menCouldn’t put Humpty together again.

The Important Bit(In case you missed it.)





(It’s ops.)





But it doesn’t have to be that way.




Change is hard.And a little scary.




A long history of conflict.




ConflictWe have different priorities.





Fundamentally unfair.




And they deserveto feel like this.


OPERATIONS | Empower Your Developers


OperationsEmpower Your Devs




Trust Your Team




Bridge the Skills Gap




Read-Only Logs




Consistency




Source ControlSharing is caring.




On-Call RotationWake me up. I dare you.




Simple Deploys


DEVELOPERS | Don’t Be Assholes


Developers Don’t Be Assholes




Plan Together




Small Changes




Communicate




Yes, And…




Stay Open




Be Humble


FAILURE | Practice Failing Together


Embrace FailureIt happens. Seriously.




Leave Your Ego At The Door




Don’t Point Fingers

Make failure fabulous.




PostmortemsThey’re not optional.




1. What happened?2. What was impacted?3. When did it happen?4. Who was involved?5. How was it discovered?6. Why did it happen?7. What’s the solution?8. When will it be fixed?

Postmortem Questions






Making your job awesome is your job.





Emily Dowdleemilydowdle.com@editingemily

humpty dumpty a story of api devops gone wrong (emily dowdle)

Technology