Learning a new technology can be daunting. For many of us, the way we try to make sense of a new technology is through their documentation and the examples we see online. The problem with GraphQL is that - because there’s no “vanilla” GraphQL - there’s no central hub for all of the information and tooling necessary to learn. While documentation is meant to serve as a tool for teaching, it’s under-utilized and scattered throughout the community. Consider this talk a voyage through the ups and downs of learning GraphQL as a frontend developer. Along the way, we’ll touch on the major pain points faced by many GraphQL newcomers and how we can leverage our existing knowledge to expedite learning.
Enjoying these posts? Subscribe for more
Subscribe to be notified of new content and support Bytesized! You'll be a part of the community helping keep this site independent and ad-free.
Thanks! Check your email to confirm your subscription.