DEV Community

Discussion on: Is testability a reason to change your design?

Collapse
 
codemouse92 profile image
Jason C. McDonald

Funny thing is, you'd think all this would be obvious...but our industry has a strange habit of adopting methodologies for their own sake, instead of because how they can benefit our project.

Auxiliary point, "TDD" drives me a little crazy, because it is a particular methodology of programming that doesn't work for all projects. I've worked on a few where TDD would have been more of an obstacle than an asset. We still do testing in those projects, but it isn't "TDD" per-se. In short, Testing != TDD. :)

Thread Thread
 
n_develop profile image
Lars Richter

Auxiliary point, "TDD" drives me a little crazy, because it is a particular methodology of programming that doesn't work for all projects.

It's very important to stress that. I don't think there are a lot of practices and methodologies that work for every project. Every project is different. They use different languages, frameworks and libraries. There are really big and very small projects. From a few hundred lines of code, to millions.

I said it before and I will say it again: Use the right tool (or framework or methodology) for the right job. Don't be dogmatic.