> 2. I think the boilerplate is good in making things explicit. I think Boilerplate is the lack of a more succinct way of expressing your intent. So, boilerpla

> 2. I think the boilerplate is good in making things explicit. I think Boilerplate is the lack of a more succinct way of expressing your intent. So, boilerplate is never good in making things explicit, it's just the (current) shortest way possible to accurately expose your intent. For example, in TypeScript, if I delve into making datastructures `algebra-ish`, I always have the boilerplate of defining a `tag` field in my objects, and lengthy switch-constructs to match on the tag field. It's not good in making things explicit, it's actually just the only way (at the moment).