I agree. His boss is very much to blame for this. He is awful, basically siding with the client against the team he is meant to protect. It is very important t

I agree. His boss is very much to blame for this. He is awful, basically siding with the client against the team he is meant to protect. It is very important to separate the domain of responsibility: What to do -> the client How to do it -> the developer Sure, there can be interactions both ways between the dev/architect and the client but you must be ready to defend your borders (i.e. the implementation) very fiercely with difficult clients. The dev didn't do it and got no respect back. I can't blame the poor dev too hardly though. Life really sucks when you have to work against your boss and the client.