1/ I love Test-Driven Development. I'm not strictly test-first, but I approach it. But, I'm slowly starting to realize there is a complexity *cost* associated with TDD. It may select for testable code, but it also tends to make code that is too big for your head less painful.
-
Show this thread
-
2/ If that's a symptom of the system your building, it's a good thing. It guards against regressions and makes what you're doing obvious and legible. But, sometimes it may inhibit the search for... ...simpler.
1 reply 0 retweets 0 likesShow this thread -
3/ (This is a hot take that I'll almost certainly reject quickly.)
1 reply 0 retweets 1 likeShow this thread -
Replying to @generativist
After you’ve already broken your system into understandable sub-components, it becomes much harder to re-imagine how it would operate under a completely different paradigm.
1 reply 0 retweets 1 like
Replying to @RealtimeAI
Yea, it's a real cost. (Although admittedly, the untested assumptions cost is still higher...)
2:17 PM - 12 Jun 2019
0 replies
0 retweets
1 like
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.