1/ in my opinion, the goal of good boundaries and isolation is to let you be "sloppy in the small, rigorous in the large"
@isaac32767 I think the answer is tautologous from the rest of my statements. Function boundaries offer insufficient tools for rigor.
-
-
@isaac32767 it's easy to say "YAGNI rigor", but I think what happens in reality is that larger isolation boundaries take their place. -
@isaac32767 And I think that's fine. Sloppiness can be correlated with productivity in the small!
End of conversation
New conversation -
-
-
@wycats not sure you understood my question. It was not meant to be an argument to your previous statements. -
@isaac32767 I just meant that the rest of the statements basically define "rigor" implicitly. -
@isaac32767 Every language has some details that cannot be expressed in various signatures. That "sloppiness" ends up being ok in the small. -
@isaac32767 JS doesn't even have arity checking, for example, while Ruby does. Go has structural types only, etc. -
@isaac32767 The sloppiness in each of these systems is ok as long as the implicit assumptions don't leak. -
@isaac32767 Isolation boundaries try to use human tools to contain the sloppiness, which works well if the boundaries are relatively coarse.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.