No. Don't do that. You never know who did what or why they did it. There may be some good reasons for bad code. Even worse, there may be a personal relationship

No. Don't do that. You never know who did what or why they did it. There may be some good reasons for bad code. Even worse, there may be a personal relationship that you inadvertently shit all over by suggesting the client ditch their programmers. Don't shy away form pointing out bad code that gets in your way (and why they need to pay you to fix it), but don't make it personal - there is no up side.