Keeping your component's side effects (like data fetching, subscriptions, or logging) close to where they are triggered, avoiding the pitfalls of prop drilling.
These are some patterns I've found helpful for using GraphQL in a pragmatic fashion to reduce headach...