Avoid errors, or, how to make good programming

I do not like orange (Warning) or red (Error) components, so I try (whenever as possible) to avoid them by including some exception handling before.
I recently had a Warning for trying to perform a Join Curves in list with only one curve. I avoided the error with the definition attached (perform Join Curves only in lists with more than one curve).
Do you have any tips/advice on how to do this more elegantly, or if I should not even care?

I understand the sentiment, but I’d say ignore warnings like this one.

It is reassuring to hear it from the big guy. Thanks.

We’ll have to rethink our approach to messaging so that it will become possible to deal with warnings that are expected. But not for GH1 I don’t think.

In Rutten we trust.