Not sure how the DevNation team managed to do this without talking to me, but it appears they custom tailored Monday's tracks specifically for me... oh, and probably for everyone else who is going that is interested in DevOps. :) Thanks DevNation; thrilled to be able to go!
If you haven't already taken a look at the line-up, now is the time to do it. Here is where I will be on Monday:
8:30-10:00 - Agile architecture and design with Neal Ford
It has been hard for me to find people talking about how to balance great design and architecture with the need for agility and speed. I am very interested in hearing more about the tactics Neal is suggesting for architecture and design specifically as it pertains to an agile framework. I can't wait to hear more about what other teams are doing in this space.
10:15-11:10 - How Netflix uses DevOps for reliability and developer velocity with Jeremy Edberg
Jeremy references moving Netflix data centers from monolith systems w/ centralized operations to the cloud. Since we are in a similar situation in Red Hat IT, I'm interested in hearing about that journey, and what the "dream DevOps" team looks like.
11:30-12:30 - How Facebook does open source at scale with James Pearce
In his abstract, James asked the question, "With hundreds of projects, thousands of engineers, and tens of thousands of participants, how does Facebook manage the open source portfolio itself, at scale?" I would love an answer!
1:30-2:30 - DevOps general session with Gene Kim
Whether he knows it or not, I began my official DevOps journey with Gene at a conference last June. His speech and and my subsequent reading of "The Phoenix Project" was the nudging I needed to align all the things I was disgruntled about to something that I could measurably change. I am excited to get to hear him talk again next week.
2:45-3:45 - Continuous delivery through continuous questioning with Joel Tosi
My perception may be wrong, but I view this as the "how do I convince my boss to let me use tools like Chef / Puppet" talk. Hopefully we will answer the question, "how do we know if we are doing the right thing?" My default answer is: If we aren't, we can adjust in two weeks.
