Things that can't be solved by any programming methodology

Below is a great quote from the thread What can't be solved by TDD? on StackOverflow. It is true to any programming methodology, technique or tool.

In my opinion this perfectly highlights what the real problems are in most software projects today (at least in my 10 years experience as a developer/contractor). But usually those are not the problems teams are trying to solve.

 

There are a number of things it can't solve:

1. Can't address poor or incomplete requirements.
2. Can't work as a silver bullet for unrealistic project deadlines.
3. Can't fix poor architecture choices.
4. Can't guarantee a robust development environment, it's only a technique.
5. Won't solve writers/coders block. You'll get stuck on what test to write next.
6. Doesn't fix a poor understanding of the problem domain. It will, however, show that the person doesn't know what to test to someone who is knowledgeable.
7. Won't show you the answer to what algorithm is the "best" to use.
8. Isn't a guarantee that you can push to production from development. It has to go to test unless you're willing to accept the possibility of bugs.

That's all I can think of. About the only way around the things that TDD doesn't address is to have a competent, team-oriented group who want to make good software rather than clocking in/out from 9 to 5.

follow me on twitter, I need some friends :-)