You want to get started with #graphql in .NET? I got you covered with my new course at @dometrain. https://t.co/4lRGKfarIn I can tell you this course is massive with over 7h of content. I cover not only the simple things but discuss advanced topics like schema design and schema

Great session at the #GraphQL AI user group tonight with a lively exchange between engineers from @Meta, @Netflix, @apollographql and @Chilli_Cream. We dug into progressive schema exploration, sub-schemas and AI-driven query generation. Exciting direction for the ecosystem.

My talk about Getting Started with MCP and Agentic UI went quite well today. I think I will put a small course about OpenAI`s Apps SDK and the new MCP Apps standard on youtube.

Really love this talk from Sabrina about one of the core components of modern #GraphQL clients called a local data consistency engine. If you want to understand the magic of relay, other GraphQL clients or build a new client. This talk is for you! https://t.co/mxsZXJNwmO

🔥 Modern enterprises don’t have to be disconnected islands. See how agentic platforms turn silos into collaboration and intelligence at #GraphQL Day Paris https://t.co/v7Yx1iEtyx Catch the talk: From Isolated Services to Agentic Platforms - @michael_staib & @pascal_senn #AI

🚨 GraphQL Day Paris Giveaway 🚨 In GraphQL, what's the difference between interfaces and unions? Answer this question and we’ll raffle a free ticket among the best answers: Go! 👇 https://t.co/VYvZeqpQy9 #GraphQL #GraphQLDatParis @APIdaysGlobal

GraphQL's simple execution algorithm can result in under- and over-fetching, and a choice between N+1 issues or huge promise/futures usage. We need something better. Holistic. Batched. Efficient. Join @Benjie's talk -- Grafast: A Declarative Solution to GraphQL's Execution Woes

GraphQL error handling sucks. There, I said it. Null checks everywhere, and ambiguity: error, or true null? We've all been there. In this talk, Benjie Gillam shows how to fix GraphQL's biggest mistake in 512 bytes. 👇 https://t.co/S5abbWpiIR

You're using GraphQL fragments wrong. They're not for reuse, they're for co-location. Here's what Meta learned refining this idea 👇🏼 https://t.co/rD1kz45DG5

You're using GraphQL fragments wrong. They're not for reuse, they're for co-location. Here's what Meta learned refining this idea 👇🏼 https://t.co/4F66D3LXJF

Great insights into how @netflix approaches #graphql schema evolution.

Very good talk on fragments in #graphql and what the mental model really is behind them. https://t.co/0v7VS7fLVz

The 3 worst GraphQL myths: ❌ Everything is POST ❌ All URLs are /graphql ❌ Anyone can query anything One solution destroys all three: Persisted Operations/Trusted documents

@GraphQL @rob_richard Thanks @rob_richard !!

A few weeks ago I launched my xUnit course. Many of you asked: “Can I buy it without a membership?” ✅ For the next 72 hours only — yes, you can. Get lifetime access here →

👏 From GraphQL Scalars to the conf app & website, from nullability & HTTP to composite schemas, @martinbonnin is everywhere — contributing, reviewing, and giving solid feedback. Thank you for all you do! 🚀 #GraphQLStar

🎉 Welcome to #GraphQLConf 2025! Tomorrow we kick off 3 incredible days in Amsterdam with the global #GraphQL community! Ready for 100+ sessions, amazing speakers, and endless learning opportunities? See you bright and early! 🚲 🎟️ https://t.co/13ppwSHVIQ

Limit/offset pagination is simple but expensive, and not resilient to changes in the underlying data. Cursor pagination is resilient and performant, but doesn't give you "jump to page"... @michael_staib gives us the best of both worlds with "relative cursors":

@stephenspalding @stephenspalding I btw have started to referring to it as the Stephen Sandwich problem :D

The sandwich problem in #graphql explained by @stephenspalding . I have to say one of my favorite talks :) https://t.co/kEKVse3rQa

Fun fact 🤣 the first thing a #graphql server does is to defragementize the #GraphQL operation.