re: What programming best practice do you disagree with? VIEW POST

re: My point is that tests have a tendency to solidify existing code. If the code is changing before it's even released, this is time wasted. Write t...

Sorry but I have to disagree. A large point of TDD is to allow for this. You write a test that describes the functionality that you want, then write the implementation. After you can refactor, change, rewrite the implementation as much as you want and the test it still valid. If you need to change the functionality then this can be done be first updating the tests.

If you work in an agile environment as you suggested you should be creating small, potentially shippable products. So once you have implemented something, it shouldn't be changing too much especially before you release, as it will have been agreed before brought into sprint.

code of conduct - report abuse