↳ In-reply-to » I did a take home software engineering test for a company recently, unfortunately I was really sick (have finally recovered) at the time 😢 I was also at the same time interviewing for an SRE position (as well as Software Engineering).

Speaking of good error handling. Have you or your mates/colleagues thought much about good/best practices around this? Besides the fact that it’s a bit of an “art form” – So is good Unit Testing really and even designing good interfaces.

For example, how much context to provide? Should you always wrap the underlying error? Is it always useful to bubble errors up the stack? I’m not even sure myself, but one thing that does come to mind is to avoid repeating the same error as they bubble up the stack. I don’t know how to define this clearly though in a set of examples and best practices like Jessica Black has done so eloquently in her article (yet)