Being wrong is often seen as the worst thing that can happen™, especially when you architect, build, and run business-critical applications and services. But the increased velocity of modern software development, plus the increased need for systems to be resilient, reliable, and right has increased the pressure on teams, and in particular architects, exponentially. Never before have you had such an opportunity, or the power, to be wrong. You need to get better at being wrong.
Russ Miles discusses the tools and techniques he uses to turn inevitably being wrong into being successful at being wrong. Being wrong can be turned to your advantage, and Russ shares stories of how this has happened and also the challenges to look out for.
The myth of always being right when you architect, build, and operate software is over. You’re going to be wrong most of the time. Time to get better at being wrong and learn how to turn accidents such as outages into opportunities.
YOU MAY ALSO LIKE:
- Keynote: Learning To Be Successful at “Being Wrong”™ In The Cloud (SkillsCast recorded in September 2019)
- Designing Microservices: Responsibilities, APIs and Collaborations with Chris Richardson (Online Workshop on 23rd - 26th August 2022)
- Evolution and Improvement of Software Architectures with Markus Harrer (Online Workshop on 23rd - 25th November 2022)
- iSAQB Software Architecture Gathering — Digital 2022 (Online Conference on 14th - 17th November 2022)
- Software Architecture in a DevOps World (SkillsCast recorded in February 2022)
- F# Gives You Superpowers (SkillsCast recorded in October 2021)
How To Be (Successful At Being) Wrong
Russ Miles is CEO and co-founder of Reliably, where he and his team build products and services that help developers build and run reliable systems. Russ is co-founder of the free and open source Chaos Toolkit project, and is also an international consultant, trainer, speaker, and author. His most recent book, "Learning Chaos Engineering" by O'Reilly Media explores how to build trust and confidence in modern, complex systems by applying chaos engineering to surface evidence of system weaknesses before they affect your users.