Abstract: Feature flags are a DevOps pattern to push changes live to production “off”, and then turned on to different users. Feature flags allow the separation of deployment from rollout, enabling the ability to quickly throttle features for different users segments. In this talk, you’ll learn how you can use feature flags for opt-in early access, private beta, canary launches and dark releases. The benefit is to break down the walls between Developers, Operations, QA, Design, Marketing, and even Sales to give access at the right time. More effective releases allow teams to move faster, build trust, and deliver better products.
Edith Harbaugh is CEO & co-founder of LaunchDarkly. She has more than 15 years of experience in software engineering with both consumer and enterprise companies. She is cohost of “To Be Continuous”, a podcast on continuous delivery published by devops.com and a columnist for ReadWrite. She holds two patents in deployment. Edith earned a BS, Engineering from Harvey Mudd College. She enjoys trail running distances up to 100 miles.
Although not officially coined until 2009, DevOps ideals have been explicitly discussed since at least 2006. Recently, however, the term “DevOps” has gained increasing popularity across a variety of fields and industries. DevOps is not a development methodology or technology; DevOps is an ideology. It is a way to facilitate organizational prosperity and growth while increasing each individual employee’s happiness along the way. As DevOps has gained in prominence, a gap has been created between the original definition of DevOps and this new “enterprise-ready” buzzword.
For organizations beginning DevOps practices, this talk will provide a 10,000ft view of DevOps and how you can properly implement DevOps practices in your organization. For organizations that are currently practicing DevOps, this talk will cover common pitfalls, ways to sustain a happy culture, and new tips to foster organizational prosperity.
Seth is a software engineer and open source advocate at HashiCorp. Previously, Seth worked at Chef (Opscode), CustomInk, and a few Pittsburgh-based startups. He is a co-author of Learning Chef and is passionate about reducing inequality in technology and organizational culture. When he is not writing software or working on open source, Seth enjoys speaking at local user groups and conferences. He is a co-organizer for DevOps Days Pittsburgh and loves all things bacon. You can find him on the Internet.
In today’s technology organizations, we are all in agreement that “silos are bad”. One of the key components of the DevOps methodology is cross-functional communication and work style. In order to successfully have a high performing DevOps-driven technology organization, trust is key.
In this talk, I will guide you through the reasons that trust precludes apologies. Mistakes are okay. I will touch on the culture of blamelessness, what is needed for “transparency-driven development”, and how to change your way of thinking from being a “CYA Engineer” to a truly collaborative and high-performing “Trust Engineer”.
Matt Stratton is a senior solutions architect at Chef, where he demonstrates how Chef’s automation platform provides speed and flexibility to clients’ infrastructure. He is devoted to concepts like Continuous Delivery and Infrastructure as Code, and his license plate actually says “DevOps”. He is the creator and co-host of the popular “Arrested DevOps” podcast.
Matt has over 15 years experience in IT operations, ranging from large financial institutions such as JPMorganChase and internet firms, including Apartments.com. He has given presentations at ITSM focused events, ChefConf, DevOpsDays, Interop, and various local groups within the Chicagoland area.
He lives in Chicago with his three children, and has an unhealthy obsession with Doctor Who, Firefly, and Game of Thrones.
Git is a great SCM, and almost everyone is familiar with using it in that way. However, the features git offers, along with the indexing power, makes it quite handy to use for multiple types of data storage, including as a backend for visualization or data exploration.
Examples will be given in the talk for a few examples – including access tools – all of which are available on Github:
– Storing complicated data from REST APIs (diff, grep, log)
– Wiki/SCM with Git as a backend
– Graph data (such as movies) using tagging for cross-references
– Ancestry Graph (family tree)
Attendees will come away with inspiration and ideas about how to use Git to store, share and explore data without the overhead of a database.
Kirsten Hunter is an unapologetic hacker and passionate advocate for the development community. She currently works as an API Evangelist for Akamai, and is writing a book on Irresistible APIs (Scheduled publication: Summer 2016). Her technical interests range from graph databases to cloud services, and her experience supporting and evangelizing REST APIs has given her a unique perspective on developer success. In her copious free time she’s a gamer, fantasy reader, and all around rabble-rouser. Code samples, recipes, and philosophical musings can be found on her website at http://www.princesspolymath.com.
CI is a well-known and popular methodology, which is supposed to help software projects to stabilize their source code and make the entire development more predictable and surprise-free. Even though all this sounds very good in theory, the practice is different. in many companies I’ve been consulting with, the situation is very similar – continuous integration is causing troubles if being aggressively enforced. There is a very logical reason for that, which I will discuss at the session and will suggest a vendor-neutral solution.
Yegor Bugayenko is a CTO and co-founder of Teamed.io, a software development company with a unique approach to management of distributed teams; a regular blogger at www.yegor256.com; a proud holder of PMP and OCMEA certifications; a hands-on Java developer and a lead architect of a few popular open source projects, including jcabi.com, takes.org, rultor.com and qulice.com. Yegor lives in Palo Alto, CA and Kyiv, Ukraine.
Enterprises are looking to adopt DevOps Practices to improve delivery lead times, quality and efficiency. Many companies struggle with how to begin this process and relating this to the application of Lean and Agile principles. This talk describes a foundational model and roadmap, which is being successfully used by a Fortune 100 company on its journey from Agile to Continuous Delivery utilizing DevOps Practices. The model includes component of practices and culture to establish a roadmap for successful implementation of a DevOps Program.
Carmen DeArdo is the DevOps Technology Director at Nationwide Insurance and is responsible for driving Continuous Delivery utilizing DevOps, Lean and Agile techniques. This includes recommendations and implementation of technologies integrated across the development life cycle to accelerate delivery. Carmen was a speaker at Gene Kim’s 2014 and 2015 DevOps Enterprise Conferences and 2012-2015 IBM Innovate and InterConnect conferences on improving productivity, quality and visibility through the use of DevOps practices such as continuous planning, integration and continuous delivery.
Salt Lake City DevOps days is an open conference for discussing methods of improving the interaction between developers and operations teams. It the natural convergence of these two diametrically opposed groups as they become one functional agile team.
As we put together this event, we’re asking that you put together a proposal so that we can shape the future of DevOps in the Silicon Slopes.
You can participate as a speaker in three ways:
Propose a talk or panel for our morning conference: there is two days with six 45 minutes slots. We can have up to 200 people in the auditorium.
Propose an Ignite talk that will be presented during the Ignite sessions: Ignite sessions are 5 minutes slots with slides changing every 15 seconds (20 slides total) also presented to all attendees in one room.
Openspace session: even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during the openspace portion of the conference. Check the openspace format for more information
Some suggestions to get you thinking but not limited to:
How to make a proposal: Send an email to [email@example.com] with the following information
Proposal working title (can be changed later)
Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
Description or abstract
SLC DevOps Day’s Rules: