I did make a pretty strong point about Sticking to the Spec up there, perhaps over stressing that point. Obviously the spec can't think of everything, or it would have already developed the whole application. But non-trivial rewrite 50% of the code changes? I'm just not down with that. This is even more complicatd by the fact that another developer wrote about half his client side in vbscript and then quit. I'm more entertained than irritated, but it still gives me a headache.

lachoy mentions a problem of client ego thinking they know what's best. In my experience here (but I'm saving the brunt of this rant for later) that the client really just wants something wiz-bang and wants you to PSI::ESI exactly what that is out of them. Development cycles in Japan flip back and forth on the order of hours or days at most (at least at my company).

The developer runs into a problem (frequently), management can answer it about 1/2 the time and otherwise calls the client. Sometimes management will save up a bunch of questions and take them to a meeting to get it all out. Meetings with clients are every week or so. I have more to say, but I'll save it for another post towards June when I've completed my year here and I can be as complete as possible.


In reply to Re: Benefits of the Specification by Lexicon
in thread Benefits of the Specification by Lexicon

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":