I'm picky because, as a coder, I have to personally deal with different variations of what people think "prototype" means.
One client thinks prototype means "mock-up", another thinks it means "ready to go" after a round of QA.
Surely you can see how this might effect a project overall?
No doubt. That's why specifying project requirements and writing proposals is usually so important for both client and coder. Managing expectations is key.
Semantics: http://en.wikipedia.org/wiki/Prototype#Semantics