General client question - If you run across a seriously bad script in an account, do you inform the client and advise them against further use of that dev/company? For example: New script was written in SS1.0 with a loop that does a record load to get information off an item and they have hard-coded URL values embedded in the script.

Sounds horrible. Personally I would advise of the issue and possibly suggest a better approach but it lies in the hands of the previous dev and that company to sort it out.

I have to agree with @karlenigma - but I do have to say it depends on your relationship with the client. Don’t like to “badmouth” others that have developed scripts in someone’s environment, but at the same time you should be comfortable enough to inform them that this seems egregious, and that you may suggest (or may have taken) another approach to solving that particular issue.

Thank you. I agree with these statements as well. I wanted to make sure I wasn't out of bounds. I want what is best for the customer.

I would even advise the customer when I found code that is not scalable at all and any subsequent change would require a lot of time and effort(meaning they are basically losing money everytime they need to change or update that script because of the poor design)…

If you see my name on the script, then no, please god no.

Also, a single script may not accurately reflect on the author's company as a whole - and not even on that original author any longer if they have continued to learn and grow their dev skillz.