In our 10th anniversary episode, we discuss why it is a good idea to throw error messages at other developers in case they are using a component in an unexpected way. This concept helps in embedding junior developers in a team and saves a ton of time and effort hunting down weird bugs. We explain how to implement this design pattern using it in expressions, processes and interfaces.

And somewhere, deep in this stream of thoughts, we find out that this kind of error handling sometimes must be optional. Sic!

Video “Naming is Hard: Let’s Do Better” by Kate Gregory.