> A software developer should develop for a specification Really? And where does this specification come from? Presumably from a bunch of analysts? Who then wr

> A software developer should develop for a specification Really? And where does this specification come from? Presumably from a bunch of analysts? Who then write a big fat document? Which is then handed over to developers, who then groan because it is incomplete, unclear, unusable, or unrealistic? This sounds an awful lot like the waterfall of yore which turned out not to be all that great. > he or she should not be there to entertain clients in a game of creating a product The client tends to pay people with the hopes of getting a working product. It should absolutely be the developer's job to ensure that they get it. Even if that means -- shudder at the thought -- talking to them.