The Platform Engineering Pitfall You Aren’t Looking For (Yet)

In the past few years, developer experience has become one of the biggest concerns at the C-level. Gartner found it’s the top value factor for adopting IDPs, performance engineering, CI/CD, and more core aspects of platform engineering. In 2021, McKinsey said it should be “the cornerstone of talent strategy” – and still, it’s a sticking point for a lot of software orgs. Turnover, burnout, skill gaps – symptoms abound that can often be contributed to bad DevX.Justin Reock is Field CTO at Gradle, makers of Gradle Enterprise and Gradle Build Tool. He’s focused on the developer experience at an intersectional level – where right-brain creativity, left-brain productivity, and ‘joyful activity’ combine to make development better for the people who do it. In conversation with David Sandilands, Senior Solutions Architect at Puppet, Justin shares his perspective on where platform engineering is headed and how the future of platform engineering – up, down, or flat – depends on using tools to engineer the developer experience.Speakers:David Sandilands, Senior Solutions Architect at Puppet by PerforceJustin Roeck, Field CTO at GradleHighlights:Justin’s career to date and starting a year of living out of an RVWhy the future of platform engineering depends on a developer experience focusInstructions for organizations to adopt real practices, not just hypeThe personalities needed to make stuff like platform engineering actually workLinks:Download Puppet’s 2023 State of Platform Engineering ReportOrganizational Physics by Lex SisneyFind your nearest devopsdays eventJustin Reock on TwitterJustin Reock on LinkedInDavid Sandilands on LinkedInDavid Sandilands on TwitterRead the episode transcriptFind Us Online:puppet.comApple PodcastsTwitterLinkedIn