This document discusses the concept of DevOps and systems integration. It provides definitions of DevOps that focus on culture, process, technology, training and soft skills. It emphasizes the importance of defining DevOps philosophies through rational thought and discussion rather than by chance. Senior engineers are distinguished less by technical skills and more by traits like being open to change, treating others with respect, and accepting criticism of their work graciously.

1. Let’s Not Do OpsDev
Chase Pettet
chase.mp@gmail.com
https://github.com/chasemp
http://sta.sh/0tp1fu5nh79

2. Not a technical talk.
By the end you will be like, duh.

3. Those who fell before us.

4. Systems Integration Engineering

6. “Did you guys know windows can do
firewalling? We need to switch our firewalls
over to Windows.”
-- Sr. Systems Integration Engineer
No really, this happened.

7. Project Managers?

9. US

10. DevOps

11. The state of things...

13. So why are we here then?
These are not new problems
Ours are not new solutions

15. Technical Buy-in
we are maturing as a trade…
On Being A Senior Engineer
TLDR; Most of what separates ‘senior’
engineers from junior engineers is not
technical.

16. The Ten Commandments of Egoless Programming
1.
Understand and accept that you will make mistakes.
2.
You are not your code.
3.
No matter how much “karate” you know, someone else will always know more.
4.
Don’t rewrite code without consultation.
5.
Treat people who know less than you with respect, deference, and patience.
6.
The only constant in the world is change. Be open to it and accept it with a smile.
7.
The only true authority stems from knowledge, not from position.
8.
Fight for what you believe, but gracefully accept defeat.
9.
Don’t be “the coder in the corner.”
10.
Critique code instead of people – be kind to the coder, not to the code.
The Psychology of Computer Programming, 1971

17. So is devops?...
* Culture
* Process
* Technology
* Training
* Touchy-feely goodness
* Softskills
* None of the Above?
* All of the Above?

18. Devops definitions are important?

19. The Factory of DevOps Definitions

20. On the importance of defining ourselves...

21. Your only choice is whether you define your philosophy by a conscious,
rational, disciplined process of thought and scrupulously logical
deliberation — or let your subconscious accumulate a junk heap of
unwarranted conclusions, false generalizations, undefined contradictions,
undigested slogans, unidentified wishes, doubts and fears, thrown together
by chance, but integrated by your subconscious into a kind of mongrel
philosophy and fused into a single, solid weight: self-doubt, like a ball
and chain in the place where your mind's wings should have grown.
Ayn Rand
West Point Graduating Class
March 6, 1974

22. The Torvald TLDR;...

24. We need to be our own advocates.

25. Devops: consciously writing and running code.

26. https://gist.github.com/jallspaw/2140086
Devops: consciously writing and running code.

28. Before devops: write code, run code.
After devops: write code, run code.

29. References
allspaw noops response
Ayn Rand - Philosophy Who Needs It
whose line is it anyway - helping hands
allspaw senior engineers
The Psychology Of Computer Programming