This document appears to be a series of tweets by Bridget Kromhout discussing operations in the era of serverless computing and containers. Some of the main topics discussed include the challenges of operating complex technical systems and the human factors involved, how architectural considerations and communication structures impact operations, the importance of observability and monitoring systems, and establishing a culture of collaboration in DevOps.

1. @bridgetkromhout
Ops in the time of
serverless containerized webscale

2. @bridgetkromhout
lives:
Minneapolis,
Minnesota
works:
Pivotal
podcasts:
Arrested
DevOps
organizes:
devopsdays
Bridget Kromhout

3. @bridgetkromhout
traded oncall… …for more travel (similar effect on sleep)

4. @bridgetkromhout
Massively scalable fault-tolerant
distributed systems require a
significant engineering effort to build
and operate; complex socio-technical
systems are even more challenging.
Computers are easy;
people are hard

5. @bridgetkromhout
Not the goal: resumé-driven development

6. @bridgetkromhout
The goal: shorter time from
idea to value
Image credit: leadliasionImage credit: thebigword

7. @bridgetkromhout
How do we
get to
the goal?

8. @bridgetkromhout
serverless
(in the brave new cloudy-with-a-chance-of-containers world)

9. @bridgetkromhout
serverless
(in the brave new cloudy-with-a-chance-of-containers world)

10. @bridgetkromhout
— Simon Wardley

11. @bridgetkromhout
“Nothing’s the same anymore.”
Jeffrey Sinclair
Babylon 5

12. @bridgetkromhout
"The past is never dead. It's not even past.”
William Faulkner

13. @bridgetkromhout

14. @bridgetkromhout
architectural considerations

15. @bridgetkromhout
Image credit: James Ernest

16. @bridgetkromhout
Image credit: xkcd

17. @bridgetkromhout Image credit: Wikipedia
“Any organization that designs a system…
will produce a design
whose structure is a copy of
the organization's
communication
structure.”
Mel Conway

18. @bridgetkromhout Image credit: 00abstrahiert99 on Flickr
…but #opslife

19. @bridgetkromhout

20. @bridgetkromhout

21. @bridgetkromhout
Who owns your availability? The answer may surprise you!
Image credit: Wikipedia

22. @bridgetkromhout
observability: answering questions we didn’t know to ask

23. @bridgetkromhout
communication &
disconnects

24. @bridgetkromhout
understand your environment

25. @bridgetkromhout
monitoring: the old way

26. @bridgetkromhout
Monitoring
monitoring: the new way

27. @bridgetkromhout
Attack
Kitten
growls
about
Day 2

28. @bridgetkromhout
Attack Kitten Cat Reality Check

29. @bridgetkromhout

30. @bridgetkromhout
tools: necessary but not sufficient

31. @bridgetkromhout
The Wall of Confusion

32. @bridgetkromhout
The Wall of Confusion
yolo nope

33. @bridgetkromhout

34. @bridgetkromhout

35. @bridgetkromhout
hard problems & human factors

36. @bridgetkromhout
hard problems & human factors

37. @bridgetkromhout

38. @bridgetkromhout

39. @bridgetkromhout
“In a world that celebrates pioneers—
be the settlers instead.”
— Laura Bell (@lady_nerd)

40. @bridgetkromhout
devops: a culture of collaboration

41. @bridgetkromhout
We are uncovering better ways of developing
software, by doing it and helping others do it