what if DRY is wrong, even in the "single source of truth" sense? So many of our tools for program correctness are, essentially, about overlapping and redundant "sources of truth" -- type definitions, tests, contracts all verify your code's "truth" by duplicating some part of ithttps://twitter.com/rtfeldman/status/1092885754265489408 …
-
-
Bugs are a much worse problem than duplication. DRY can be done, but you need to be careful about the consumers of the API. No semver here and every caller shares the same version of the code. So no guarantees that a change won't cause problems unless you test well.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That's a good argument for being clear about contract boundaries of functional units.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.