I agree somewhat. A year on a team that does TDD has taught me when and where it is a great tool. No tool is useful all the time and everywhere.
Productivity isn't just this sprint. It is the productivity of the next 10 years of maintaining code.
Testing is complex and it will take teams time to ramp up from "testing what they know how to test" to "testing where it is needed".
Enterprise rarely has top notch code quality. When the devs are a rotating cast of various experience testing TDD keeps the tests flowing. Testing keeps devs from quitting, users from bad experiences and, ultimately, costs down.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree somewhat. A year on a team that does TDD has taught me when and where it is a great tool. No tool is useful all the time and everywhere.
Productivity isn't just this sprint. It is the productivity of the next 10 years of maintaining code.
Testing is complex and it will take teams time to ramp up from "testing what they know how to test" to "testing where it is needed".
Enterprise rarely has top notch code quality. When the devs are a rotating cast of various experience testing TDD keeps the tests flowing. Testing keeps devs from quitting, users from bad experiences and, ultimately, costs down.