RT @GraphQL: Congrats to @martinbonnin and @Pascal_Senn for being elected into the GraphQL TSC!.

RT @GraphQL: This week's #graphqlstar is the one and only @Pascal_Senn 🎉 Pascal has been an important contributor to the composite schema W….

I think it's beautiful that competitors in an ecosystem can come together to build a standard that is free for everyone to use and find common ground. The composite schema specification unifies all the best parts of existing federation solutions! 🌐✨.

I really enjoyed working on the composite schema specification and am excited to push the boundaries of distributed GraphQL together with @theguilddev and @apollographql and all the others involved!.

#GraphQLConf has come to an end, and what a fantastic conference it was! It was wonderful to finally meet in person all the amazing people I've been working with over the past year.

I have worked with numerous database systems over the years, but I don't think I've ever had a better experience than working with @ClickHouseDB. It feels like for every problem I have, there is a solution directly built into the database. such a joy to work with!.

So,the next time you choose a technology for your projects,consider this:#GraphQL is not just about scalability, multi-modality, efficient data fetching et al. It unifies communication and makes your domain accessible to everyone. You dont have to be Facebook for it to make sense.

Now, if a new requirement comes in, lets say, adding an address to the User. This is enough information for the backend dev to know where to add a field (extend the User type with the address field) and for the frontend dev to know where to expect the data, User.address.

Using a unified domain model across the project ensures clarity and prevents misunderstandings. The used by the frontend developer in the <UserProfile/> component, aligns perfectly with the attribute defined in the PM's and stakeholders domain model.

developers, stakeholders and PMs often use different terms to describe the same thing. This is why we need to have a common language to communicate. To bridge this gap, we need a ubiquitous language, and this is precisely where @GraphQL with its schema excels.

In 1999 a NASA mission to Mars failed, because some engineers used imperial units while others used metric units. A good example of what happens when people do not talk about the same thing. This is also a common problem in software development.

RT @michael_staib: You want to get started with #graphql in .NET? I got you covered with my new course at @dometrain. .

I'm super excited about 🚀. I've always switched between Obsidian, @logseq, Notion, and various to-do apps. Recently, I settled on a custom solution in Obsidian, but this PR looks like it's exactly what I've been trying to build there!.

RT @michael_staib: We have been working with our friends form @apollographql and @TheGuildDev since last year on a new specification for di….

Having code coverage in PR reviews on @github would be a game-changer

RT @michael_staib: Let's checkout the new #graphql operation builder in #BananaCakePop 16.

RT @RafaelStaib:

So @openai just opensourced a three year old repo called grok. And yes, the issue board already looks exactly how you would expect it:

I know there are relay resolvers, but it's still not possible to mutate the local state easily with useMutation and a simple resolver.

I wish grats would just have an integration into #relay for client side extensions. client side state management would be so easy. (also, checkout grats by @captbaritone ) #graphql.