4 ms·

If the requirements are unclear, then why are you writing code? Why aren't you having conversations with people to clear up those requirements?

• dtech 9y ago
  Because there is only so much talking is going to do, at some point you just need to build a prototype and see if it works and how it can be improved. If pre-planning, talking and requirements solved this problem we wouldn't see failed (software) projects and companies. As a matter of fact, extensive requirement gathering before prototyping and iterating is a good way to fail a project as at some point you're just adding new towers to your castle in the air.
  • s73ver 9y ago
    Yeah, but if you're prototyping, then that shouldn't be the actual code you use. You write a prototype to test your assumptions, have the people bang on it for a bit, then throw it away. You take the lessons you've learned from that, and now you have more of a "spec" than you did before. Thus, you can write your tests.