Benjie

One of the things we’re excited about this year is creating a Golden Path for GraphQL, here is @graphile.org’s @benjie.dev and Meta’s @keweiqu.bsky.social introducing the initiative

V5's database queries are much simpler and more performant than in V4 (which was already faster than traditional execution methods!) thanks to offloading work from Postgres to the Grafast planning engine in Node. I'm so happy that what started out as a theory is now having such measurable impact!

I've been using postgraphile for years at work, including latest V5 RCs and it's just a pure gem, very fast and extremely flexible, plus it works perfectly with rescript-relay! Kudos @benjie.dev for the great work!

It would be hard to understate how large of a feat of engineering this was. PostGraphile is such a powerful tool and it's great to see such a great foundation for the future in v5 Kudos to @benjie.dev, Jem, and all who contributed to Postgraphile

GraphQL error handling driving you nuts? @benjie.dev shows a cleaner path by explaining how nulls, errors and schema design should really work together. Read it here: benjie.dev/graphql/errors #GraphQL #APIs

Yesterday was the #GraphQL primary working group and I made a presentation about @benjie.dev capabilities proposal. Slides (cute kittens included!) below. docs.google.com/presentation...

Great post from Jovi here! Remember: Trusted Documents: if you can, you should!

Missed out on GraphQLConf? The Guild have written up some of the highlights and key takeaways! Spec release, input unions, correct fragment usage, errors and nullability, federation interoperability, and more - check it out: the-guild.dev/graphql/hive...

Our team is at #GraphQLConf today, if you’re here come and say hi! It was a blast to celebrate the GraphQL Stars on stage and launch the Ambassador Program

We've just launched the GraphQL Ambassadors Program at #GraphQLConf & we're celebrating our first cohort! GraphQL Ambassadors are community leaders who help others, share their expertise, and contribute knowledge back to the community. Meet the cohort & learn more: graphql.org/blog/2025-0...

GraphQL 2? @keweiqu.bsky.social @mbonnin.net @benjie.dev and Curtis holding court on how the language could change #GraphQLConf

Yo dawg! I heard you like #GraphQL so I put the #GraphQLConf2025 data in a #GraphQL API so you can browse all the #GraphQL things using #GraphQL graphqlconf.app

I use LLMs heavily, and they're _terrible_ at code. Really really bad. Using them as autocomplete is okay-ish, but ask them to generate something serious or review something you wrote and they're wrong way more often than they're right. I advise you treat them as the most junior of junior devs.

In exciting news, I will be on stage for the first time since 2018 at GraphQL Conf, but it wont be too nerve wracking as I'll have @benjie.dev with me. We've got a huge community update to present! graphql.org/conf/2025/sc...

EUROPEAN GRAPHQL-ers: help prove demand for events outside of San Francisco! 2025's GraphQLConf is in Amsterdam; attend, sponsor, share — everything increases the chance of a future return to 🇪🇺! ⏰ Early Bird ends in 4 days: get your ticket now! ⏰ The schedule is 🔥 graphql.org/conf/2025/sc...

graphql.org/conf/2025/

Just 10 days left to save $300 off your ticket to GraphQLConf '25 in **AMSTERDAM** 8-10th September. The talk line-up looks fantastic! Looking forward to seeing you there!

I don’t see many teams using GraphQL fragments, and I think they’re missing out. Fragments let you co-locate your components data requirements with your components. I wrote a quick post showing how this works to make maintaining your apps simpler. Check it out: brookehatton.com/blog/enginee...

London GraphQL next week! New venue: American Express just across the road (literally!) from Victoria Station. Two great talks and a little recap of some of the things being worked on at the GraphQL working groups! Register so we know how much 🍕to get 😋 guild.host/events/londo...

GraphiQL v5.0 was just released; it integrates Monaco editor (so you get coloured matching braces, multiple cursors, and all the stuff you're probably already familiar with in VSCode - press F1!) and also enables comments in the variables editor. Check it out! github.com/graphql/grap...

📣 The #GraphQLConf 2025 schedule is live! 🔥 Join us in Amsterdam 8-10 Sept. for deep dives and exclusive #GraphQL talks. Amazing sessions lined up! ➡️ graphql.org/conf/2025/

Just adding more ends to the metaphorical candle...

> Yours is fine as-is if you prefer the repetition for clarity. ChatGPT with the sass! 😁 It really doesn't like that I never take its suggestions verbatim and prefer to make my own edits to my text.

I submitted two talks for this year. One for Graffle and one for a new project I recently started at @the-guild.dev. More to share about the latter in the coming weeks :))

Okay so yeah I missed the CFP deadline for GraphQLConf... but worry not - they extended it until Saturday and I submitted today! You should submit too. There's only 48 more hours for you to do it, GET IT DONE! It won't be extended again. BTW: speakers get free attendance! graphql.org/conf/2025/

It's really worth checking out the GraphQL JS documentation, a lot of effort has been put into renewing and expanding them. Especially these new guides for GraphQL Errors and resolvers are absolutely top-notch! www.graphql-js.org/docs/

Spent 2 hours writing, 4 hours editing, and 2 days spiraling about whether anyone would care. finally hit publish anyway. ashley.dev/posts/fear-o...

Nulls for daaaaaaays! (Well actually no, the point of the work is to get rid of unnecessary nulls… youtu.be/gYnVaZz-19A)

Me: Siri, time five minutes. Siri: 6 hours, 39 minutes and 11 seconds; counting down. WTAF?!

graphql-sock v1.0.0 CLI & library now available on npm; converts a schema with semantic nullability (eg via `@semanticNonNull` directives) to traditional syntax for compatibility with existing tooling (eg codegen). Pairs great with graphql-toe — throw on read from an errored field. Blog post soon!

Jeff really is an unsung hero behind the scenes of making GraphQL awesome — his calm, balanced and insightful presence brings so much to all the working groups and committees he attends. Thanks for all you do, Jeff!

Love our conference vids? Ready to shine? Speak at GraphQLConf 2025! Submit your talk by May 4 and join us in Amsterdam this Fall: graphql.org/conf/2025/#...

Nullable-by-default made GraphQL resilient, but led to a lot of client-side null-checks. Alex has stalwartly championed solving this latter issue since the early days of Client-Controlled Nullability, keeping us engaged through all our discussions to our latest “Semantic Nullability.” Thanks Alex!

Just discovered the git pager `delta`, you should check it out: github.com/dandavison/d... The docs are really good; whilst working through them (which only took a few minutes) I added a number of other enhancements to my setup. Thanks @dandavison.bsky.social! (Hoping I tagged the right person!)

I sent a PR to the postgres-array npm module that improves array parsing performance 2.5-5x and it was just merged, so if you use postgres arrays in Node: you’re welcome 😉😁 github.com/bendrucker/p...

Quick (unscientific) Poll: What would you like to see during GraphQLConf 2025's UnConference Day? 1️⃣ Workshops 2️⃣ Lightening Talks 3️⃣ Small group / focus group discussions 4️⃣ More Breakout Sessions 5️⃣ Something else - let us know in the comments!