Culture
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.

‍

Vilas Veeraraghavan
Sr. Director of Engineering, DevEx, BILL

Related talks

Culture
June 8
Why is building observability platform (still) so hard?
Any organization seriously pursuing "you write it, you run it" in 2023 is probably considering platform engineering. Observability is a necessary part of that strategy, but building the right observability platform for an organization is (still) hard. Why?
sam boyer
Principal Engineer, Grafana Labs
sponsored
Culture
June 9
Unleash the power of technical empathy
Technical empathy provides a shift in mindset and culture that cultivates greater clarity of responsibility, increases the empowerment of both implementers and integrators, and ultimately helps build and maintain trust between software delivery teams.
Jeff Doolittle
Sr. Software Architect, Trimble
sponsored
Culture
June 9
Working with a QAOps approach: Enhancing quality and efficiency in platform engineering
In recent years, the approach to Quality Assurance (QA) in software development has evolved from a separate stage of the process to an integrated approach, known as QAOps. QAOps combines principles from DevOps and QA to ensure that quality is built into the software development lifecycle from the outset, and throughout the entire process.
Ludovico Besana
QA Engineer, Banca AideXa
sponsored
Culture
June 9
Empathy for the other
Language is important but outcomes are more important than labels, especially labels which try to draw crisp lines and have the potential to diminish collaboration. Othering is toxic. Let's look at some ways to appreciate and amplify the work of others.
Nathen Harvey
Developer Advocate, DORA & Google Cloud
sponsored