Catch-22: Can't refactor because no tests. Can't test because need to refactor. The 1st problem is political, the 2nd technical.
-
-
Replying to @tixxit
@tixxit@puffnfresh Before refactoring seems like a great time to add tests. What’s the technical issue?2 replies 0 retweets 0 likes -
Replying to @sellout
@sellout@puffnfresh In order to test the code adequately, I need to refactor it.1 reply 0 retweets 0 likes -
Replying to @tixxit
@tixxit@puffnfresh But why? Refactoring doesn’t affect the external API, and tests should only use the external API.1 reply 0 retweets 0 likes -
Replying to @sellout
@sellout@puffnfresh Refactoring can definitely change an "external" API. I don't live with a bad API just because it existed a week ago :)1 reply 0 retweets 0 likes -
Replying to @tixxit
@tixxit Not saying you shouldn’t change external APIs, just that it isn’t refactoring. But I get@puffnfresh’s complicated dependencies.2 replies 0 retweets 0 likes
@sellout @puffnfresh I'm not writing functional tests or changing the actual external (customer facing) specification.
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.