What can possibly Go wrong?

Developing software is a lot of fun, especially when we don’t have to deal with all the uncertainties of life. Hardware failures, software bugs, mischievous users (or users in general) providing bad input - there are a million things that can go wrong within our beautiful products. In this talk, we are exploring how to deal with those problems efficiently while keeping our code clean. The focus will be on Golang and Python; however, we will also touch on other languages (e.g. Java).

Transcript

1. What can possibly Go wrong? Kiril Vuchkov
2. A Perfect Day of Coding
3. What can go wrong? Runtime Developer Business
4. Now what?
5. Error handling, like logging, is always a secondary thought
6. Survive with the help of primitive tools
7. If a client cannot do anything to recover from the exception, make it an unchecked exception. https://docs.oracle.com/javase/tutorial/essential/exceptions/runtime.html
8. If foo() fails, what do you do?
9. Deal with every error
10. Ignore? Retry? Do something else? Propagate? Wrap?
11. Handle everything!
12. Change handling?
13. Pass it through Handle at the edge With context
14. Why … did it happen What … happened? Where … in the code did it happen? The 6 W’s Who … was affected? When … did it happen? How … to fix it?
15. Error values in Go aren’t special, they are just values like any other, and so you have the entire language at your disposal. Rob Pike @ Gophercon 2014
16. Checked No stack trace Opaque, but wrap Assert behavior
19. Conclusion ➔ Part of the code ➔ Part of the design ➔ Part of the domain
20. Code happily ever after...
21. Thank you
22. References • https://www.artima.com/intv/handcuffs.html • https://blog.golang.org/errors-are-values • https://dave.cheney.net/2016/04/27/dont-just-check-errors-handle-them-gracefully • https://martinfowler.com/eaaCatalog/specialCase.html • https://learning.oreilly.com/library/view/clean-code/9780136083238/chapter07.html#ch7 • https://youtu.be/TTM_b7EJg5E