Your license to criticize the developer's role in this depends entirely on the requirements you provided him/her with for this project. Were they formalized and agreed upon? Were they clearly presented and sufficiently comprehensive? Sadly, I think all too often developers get the bad press when poor requirements gathering is, in fact, to blame. It is somewhat sad how meticulous one must be when presenting development guildelines, but not doing so will bite you in the end. So, my advice...if the requirements were clear, a stern rebuke is in order...if not, perhaps a process revamp.
in reply to OT - How to deal with coders who don't do what they should