Avantages
Nothing that I can think of. Basically, you are risking it to fate, you are liked your stay or you will be harassed subject to the emotional imbalances of this manager.
Inconvénients
Watch out for these 1) Are you given a task without proper KT or background documentation. 2) Are you blamed for discrepancies that result from improper KT 3) If you address your concern that this is not true are you demeaned. 4) Does the product manager talk to you in a condescending tone even when you know more than him. 5) Are you expected to ask around for information and run between pillar and post with no outcome. 6) If you come up with a wireframe are you expected to refer to a loosely coupled database with multiple data points within the same column headers. 7) So basically if you sound agitated or express your concern. Are you taken on a recorded call and put on the spot for every character and word in the document instead of the manager giving you KT on the architecture and the previously implemented logic. 8) If you try to speak up you are probably not going to benefit from it because it will be a one sided affair where you will be constantly targetted and reminded of all mistakes that happened in the past including the current one because of the arrogance of the product manager. 9) Are you being told that UAC and the initial state is not a part of a user story. 10) Basically you should be asking for help escalate matters to HR before this piece of art puts words in your mouth and stages a narrative against you. 11) Do not talk about it to others as they talk about it behind your back. 12) This is genuine advice and many others before me have faced the same situation also people from the implementation team and dev team believe so. 13) It is ok to loose interest after such a mishap. Be open about it to the HR. Don't expect anything in return