June 8

DevEx is NOT DevOps: Investing in developer enablement to reduce barriers to continuous delivery

This talk will clarify the difference between developer experience (DevEx) and DevOps practices, and clearly outline what a DevEx investment should look like in a modern enterprise. We will discuss three specific areas of DevEx investment relating to developer onboarding, day-to-day, and modernization.
Talk abstract

Most successful, high-performing software companies have adopted DevOps practices, tools and process improvements in a bid to deliver innovative ideas faster to market and build a variety of disruptive experiences within every industry vertical. However, adherence to DevOps philosophies cannot happen without a significant engineering investment to improve the efficiency of developers' daily activities. developer experience (DevEx) is the investment you make to enable solid DevOps practices, reduce developer burnout, and improve retention. The need for this investment is more pronounced as companies grow larger and the tech stack gets more diverse. 

DevEx teams strive to increase developer agility by providing training, tools, abstractions for creating/deploying services to the cloud using CI/CD pipelines, and a well-defined paved path to production that has sensible defaults for most workloads. In addition to tools, DevEx teams typically own and operate an internal developer portal. This serves as a single point of truth for documenting all tools and best practices as well as dashboards that aggregate metrics like deployment frequency, change failure rate etc (DORA metrics). 

This talk will discuss the specific engineering investments/efforts needed to provide developer enablement in three broad categories of experiences that form a part of a typical developer’s lifecycle at a company: Onboarding, day-to-day build/delivery, and modernization/refactoring.