> The existing API was served on the same domain so the new React website could've directly interacted with it without any problems. But no, this guy wanted to

> The existing API was served on the same domain so the new React website could've directly interacted with it without any problems. But no, this guy wanted to put "GraphQL" on his resume and so introduced an unnecessary extra component and potential point of failure that the company now has to support. There's a simple solution to this kind of problem: let the resume driven developer use his skills - fire him.