in reply to
Ethics of Dealing with Evil
I do see some serious issues with this whole scenario. Why, if doing work for GRWBSC, would anyone choose to implement in anything other than GRWBSC tools? I realize that Perl may have been the *best* tool for the job, but any consultant worth his/her salt should know that it's not always about what's best, but what the client wants.
It seems that both you and your client have put yourselves in a bad situation. Your client should have been more proactive in gathering the requirements and having GRWBSC sign off on them. At any step in the process, if you had concerns, you should have let your client know.
Am I or my client ethically responsible for recoding the GRWBSC Web service at no extra charge to GRWBSC even though technology-specific requirements were never discussed?
IMO, your client is resposible for being 100% honest with their client and showing them some respect. Who cares if GRWBSC is considered evil by many...the fact is, they paid for a solution and had certain expectations that weren't met. A hack to get around it doesn't seem like the ethical thing to do.
Anyway...that's my 2 cents about the matter. I will say one more thing...if you feel comfortable with knowing what you know and not letting GRWBSC know, than don't worry about what any of us have to say. :-)