"Over-engineering. I have a tendency to "throw in" functionality I "know" I'm "going to need". Making one red test green (along with the list of future tests) helps me implement just enough. I need to find a new way to stay focused."
So creating a test for a function that sum of numbers that gets 1 and 1 and returning a hardcoded 2 is "just enough" and " a great way to stay focused ", funny
I kind of agree with the other points, not so much about the "API design" stuff, while it's true it facilitates, the end word is with the main API user.
Well, I'm glad it's dead, now I don't have to spend time mocking all other parts of my program.
"Over-engineering. I have a tendency to "throw in" functionality I "know" I'm "going to need". Making one red test green (along with the list of future tests) helps me implement just enough. I need to find a new way to stay focused."
So creating a test for a function that sum of numbers that gets 1 and 1 and returning a hardcoded 2 is "just enough" and " a great way to stay focused ", funny
I kind of agree with the other points, not so much about the "API design" stuff, while it's true it facilitates, the end word is with the main API user.
Well, I'm glad it's dead, now I don't have to spend time mocking all other parts of my program.