Isabel Garrido Cardenas - What could possibly go wrong?

Learn from a personal story of failure and discover the importance of testing, understanding context, and deploying quickly while avoiding common pitfalls in software development.

Key takeaways
  • The speaker shares a personal story about a failure in one of their applications, Sauer and I, which was a file reader that received information from containers and their destinations.
  • The failure was caused by trying to evolve the system too quickly and not testing it properly, leading to many issues, including incorrect numbers and a complete disaster.
  • The speaker highlights the importance of understanding the context, being able to deploy fast and automatically, and being able to see the health of the system.
  • They also emphasize the need to ask questions and not take things for granted, and to learn from mistakes.
  • The team worked on observability and added more events to improve the system, but it was a complex solution and also had some drawbacks.
  • The speaker notes that there is no silver bullet and that every solution has its pros and cons.
  • They also mention that they didn’t have much experience working with the legacy tech they were using.
  • The speaker discusses the importance of testing and highlights the need to have a solid plan and a good understanding of the feature being developed.
  • The team added more tests and used an internal event bus to help understand what was going on inside the system.
  • The speaker concludes that as software engineers, it’s important to ask questions and not take things for granted, and to learn from mistakes.