DevOps is all about collaboration, but what does that mean at a growing company? Abstractions tend to wall us off from each other, but they also provide the opportunity to experiment (e.g., don't need to wait for ops to spin you a server up to try something out). As companies grow, communication overhead increases. As your organization grows, different techniques are needed to prevent everyone from getting bogged down.
It's hard to write documentation that anyone can get excited about. This is true for projects aimed at beginners, but it goes double for projects and writing aimed at intermediate/expert programmers. Find out how to write documentation that *everyone* would want to read and can understand.
How do you start young people out with STEM skills, and DevOps in particular? Make it useful, make it fun! I taught my nine year old nephew to take his Minecraft game to a whole new level by showing him how to administer a remote Minecraft server, a Docker container running on Digital Ocean.
In my talk, I will share my experiences on how to successfully grow and develop technical teams. My practices are designed to align employer's/employee's values and goals. I will provide specific and actionable steps that can be adjusted to fit your organizations' specific needs.
The intent of this talk is to define the place for business units at DevOps table to improve overall organization communication and tech team efficiency, including monitoring strategy, post-mortems, chatops and other DevOps-centric processes.
Diversity and inclusion have become hot topics in technology, but you may not know how to you can make a difference. However, this talk will help you understand that, no matter your background, you have privilege and can lend it to marginalized groups in tech.
"Serverless". It is already being called the buzzword of 2016. Steve is going to bring "serverless" back to reality by showing how Bustle has built a fully serverless application platform. Real production examples handling millions of API calls a day. You will leave knowing if the hype is justified.
Source code: Just put it in git, right? Scale? Github! 1000's of repos? No problem! Bitbucket Server! Now: Add PCI & SOX.. Audit. SSO. SSH key management. DR. Geo diversity. This starts where the vendor stop- workflows to keep work moving, security & audit to ensure code integrity.
How do you create the best devop you can be? When building a devop, we usually think about our technical skills but often forget aspects of our personal brand including relationship building, reputation, communication... all on top of the awesomeness you already can do. Let's talk about building the 'well rounded devop'. After we've built the devop of our dreams, how do you keep such awesome devops working in your company? Based on Jill's experience working with many engineers as well as perspectives from small (DigitalOcean), medium (Rackspace), and large (IBM) companies we'll discuss what it takes to become a sparkly devop unicorn.
How can we detect a bad deployment before it hits production? By automatically looking at the right architectural metrics in your CI/CD and stop a build before its too late. Lets hook up your test automation with app metrics and use them as quality gates to stop bad builds early!
Everyone is affected by being on call in different ways. A rotation that seems "equal" may not be "equitable," namely, it may place significantly more burden on some employees than others. I'll discuss how to make everyone comfortable, happy, and not burnt out
Mentoring and teaching are key to professional development. More organizations are adopting a "75% technical / 25% manager" role to enable career coaching and growth. Good, engaged, technical management can completely change the happiness of an entire organization.
Code review has always been used by developers, recently operations has started as well. How is it different when operators are reviewing code that has an operations impact? How can it be optimized? Our team has been reviewing ops code for years, and I'm here to share the lessons we learned.
I've found when working with many developers and operations folks that there is a real lack of understanding with regards to how TLS/SSL works. This talk was originally given internally at Braintree to help folks understand this important part of the stack.
Many conference attendees come year after year without giving presentations. The sense that there's a high bar for perfection is pervasive, and people are afraid of being "wrong." Everyone has a story to tell about a problem they've solved or issues they've tackled.
Are you sitting in front of a cluster right now? Surely you are typing at a laptop running a cluster just like the ones you have in production. And the process of moving your efforts from the laptop up to production, is it silky smooth? Maybe not. Let's talk about why.
When Docker burst on the scene in 2013, one promise that excited both developers and operations people alike was the idea that a dev would create a container on her laptop that could then be shipped right up to production. Three years later, most people have realized that it may not be that simple. In a world where we are building microservices and distributed systems, how can you ensure that the laptop you are typing at now is a step towards production-ready software and not a distraction from it? Let's get deep down and dirty into the art of constructing useful clusters on our primary development/operations control machines and the challenges we face in the process.
"I'm sure if I work hard, my contribution will one day be recognized and I'll get a raise." -- Everyone At Some Point In Our Careers. The world is unfair; this talk won't do much to fix that-- but it will give insight from a hiring manager on how to maneuver within the world we currently inhabit.