Test harness LoC / Unit Tests LoC Before: 0 / 1292 After: 324 / 400https://twitter.com/generativist/status/1263117672683720706 …
-
Show this thread
-
This borders on yak shaving except all that complexity reduction means my tests are consistent now, and in my experience, that's going to trim a few days of frustration off me in avoided WTFs.
1 reply 0 retweets 2 likesShow this thread -
Although, a good amount of this code exists because a library I'm using is ill-documented and I want to make sure my assumptions are correct now and in the future...
2 replies 0 retweets 2 likesShow this thread -
Replying to @generativist
This kind of stuff is hard to teach (at least for me). If you are not sure how some other code works, make a strict/strong assumption and make sure that you abort/fail immediately if that assumption is ever violated. I can say it, but students won't really absorb it.
1 reply 0 retweets 1 like
Yea. The code I just wrote is basically assumptions_about_XXXX_test.go with lots of func XWorksLikeYGivenConditionZ(*) from a mixture of code reading and just guessing.
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.