there is no coding principle that more violently combines good-when-used-how-it's-meant with horrible-when-overgeneralized than "explicit is better than implicit" if you're defining a constant DEFAULT_FOR_WHATEVER then every call to some method has to pass that, just fuck you
-
-
why would "strategy obliqueizer" be of use in scenario like "a coding practice is used in an obnoxious and dysfunctional way that impedes code readability and refactoring"? Like, at best it would increase the diversity of fuckup patterns, not reduce fuckupitude.
-
the phenomenon being identified is that your early mistakes seem increasingly justified because you build on them, so the use of oblique strategies is getting you outside of your model that's built on them so that, inshallah, you notice that they're fucked
- 2 more replies
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.