Software engineers are usually divided into two groups, backend and frontend. Sometimes you will have people that are full-stack but for the most part, they are either one or the other. When I first started I would constantly build the API for this startup in a certain way, I would build it how I envisioned it should work based on the requirements. I would code away for a few days and at the end of it all, there would be the feature. It would be reviewed and put into staging where the frontend would then take the development branch and add the necessary frontend changes to complete the feature. Every single time, 5 minutes in there would be “Hey Errol, how do I get X data?”, I would respond with “well call this existing query”. This was never the right option. When you have a feature that requires a bit of information on the backend but it also requires some information that exists in another query it’s pretty easy to disregard that old data and only think of the new data. It makes sense, for as far as your concerned it’s already been completed, just call that other bit of data. Well not all the time, for example, if you had a Posts and you also needed to get the comments on that post. In GraphQL you would call something like this