[archgoon]

Advice does not need to be correct to be valuable. Simply getting a perspective on a problem, and a proposed strategy, can improve your ability to reason about your problem domain. If advice is wrong, and you choose not to follow it, then you know that people will ask about it later and you will be prepared to explain why you thought it was wrong; which is a better situation then saying to potential investors "Gee, never thought about that option."

That is to say that advice, right or wrong, gives you information about the problem space and perspectives on it; which can be valuable if you evaluate said advice critically.

As an example "You should always unit test your code" may not be applicable, but being able to say something like "This code is almost 100% dealing with External systems so a pure unit test would not be the appropriate way to test this code" is a better answer than "What's unit testing?" (Yes, I'm sure someone is going to quibble with this example :) )