Our result
simply states that the order in which unit tests and
production code are written may not be as important
as commonly thought so long as the process is iterative,
granular, and uniform. Therefore, the developers could
follow the approach they prefer while paying particular
attention to step size and keeping a steady rhythm.
This matches my experience working with Clojure REPL that provides fast feedback on running application. I can quickly check how the changed code works similarly to small test. Small iterations are more important than sequence when tests are written.
A test-first dynamic may
provide long-term advantages not addressed by or detected in our study.
This is important point. In my experience TDD codebases have better tests and more maintainable production code. TDD is a good process to learn how to write testable code.
No, in my opinion it does not matter. As long as you have testable code and systems.
Did you check the story? It’s the link to an empirical study, not just a question for its own sake.
Yeah I did. But that’s my opinion :)
This matches my experience working with Clojure REPL that provides fast feedback on running application. I can quickly check how the changed code works similarly to small test. Small iterations are more important than sequence when tests are written.
This is important point. In my experience TDD codebases have better tests and more maintainable production code. TDD is a good process to learn how to write testable code.