Break Things on Purpose Gremlin

Today Jason and Julie catch up and reflect on their favorite moments from Season 3, including unpopular opinions, chaos engineering, make or break moments in engineers’ careers, and more.

Today Jason chats with Mauricio Galdieri, a staff engineer at Pismo. Mauricio describes his journey to becoming a developer, and then talks about his role at Pismo. Jason and Mauricio talk about reliability and the reluctance of financial institutions to adopt new tech, and Mauricio delves into some of the work he’s done with Chaos Engineering. The conversation concludes with a discussion about maximizing success and new technologies Mauricio’s team has been utilizing at Pismo.

Today Jason chats with Aaron Clark, Director of Developer Advocacy at the Royal Bank of Canada. Aaron shares what it was like starting out as a developer at RBC and working in early cloud development, and then transitioning to his role as a developer advocate. Jason and Aaron talk about the value applying open source principles within organizations, or “innersource.” Their time ends with a discussion on continuing education and how to keep learning.

Today we chat with Cisco’s head of developer content, community, and events, Michael Chenetz. We discuss everything from KubeCon to kindness and Legos!

We’re joined by Dan Isla, VP of Product at itopia, to talk about everything from astronomical importance of reliability to time zones on Mars.

Natalie Conklin, tamer of chaos and Head of Engineering here at Gremlin, joins us to talk about embracing change, working alongside each other, and building more reliable systems. Natalie has a talk coming up at DevOpsDays Boise which she has titled “Embracing Change Fearlessly.” Her talk is oriented around enabling teams to take calculated risks and having the guts to take those risks. Natalie spent time working in India, which helped solidify her “fearlessly” philosophy. She provides examples of taking chances and how teams can orient around them together, the cultural changes that need to happen in chaos engineering, how to communicate across whole teams, dealing with “adolescent” engineers and more!