-
Cultural post mortems: an approach to learning and recovering when your people systems fail
Winna Bridgewater will share how they planned and executed recovery work. Our aim is to inspire you to consider a systems approach when something with your team goes wrong, and we’ll provide a template for what we think worked well.
-
Riding the rollercoaster of emotions
Gabriel Michels covers key topics such as understanding and managing emotions, reflecting on them, developing emotional intelligence, and being in control of our thoughts.
-
How to effectively “Spike” a complex technical project
Aditya Bansal explains what a spike is, how to successfully spike a project, and lessons learned from leading several technically complex projects across 3 different companies, and various different teams.
-
Unleashing the artist within: Mentoring strategies in software engineering
Rodney Cobb explores the concept of artistry in software engineering, discussing the benefits of unleashing creativity and innovation in our projects.
-
Platform engineering is all about product
Gal Bashan wants to make sure you leave this talk with an understanding of platform engineering and how it relates to DevOps; what makes an IDP and a platform team successful; and finally, practices you can use to build a successful platform, and pitfalls to avoid.
-
Exit plans and how to talk about them
David Kiger covers why the answer to that question is important, how to set up the culture to enable the conversation, how to actually have the conversations once the foundation is laid, and the benefits that both employees and the company get out of it.
-
How we support making architectural decisions
Olena Sovyn takes a deep dive from the principles based on which this group operates to the specific how-to that made its work beneficial for the company and shares what we've learned from this whole experience so far.
-
How to drive pace in your team ??♀️
Alicia Collymore delivers actionable advice that'll help you to improve your teams' delivery and pace without a data-first approach.
-
“I’m happy where I am” – Supporting team members that aren’t seeking progression
Ryan MacGillivray talks about how realistically not everyone can or wants to be a Lead Engineer/Engineering Manager/Staff Engineer and nor should we be pushing people into roles they either have no interest in or have done before and not enjoyed.
-
Where we’re going wrong with developer productivity
Cat Hicks proposes a different, science-backed approach to productivity using research evidence from a study with 1200+ developers: developer thriving.