Pascal Senn 🌶

Co-Founder and COO of @Chilli_Cream. GraphQL TSC. Usually yes, occasionally no.

[Pascal Senn 🌶 @Pascal_Senn]

https://t.co/Md1nkwlXSB

[Michael Staib @michael_staib]

AI agents can call APIs, but can they actually understand them?

@Pascal_Senn shows why #GraphQL is such a strong fit for agents when using semantic introspection for huge production schemas.

This one is worth watching 👇
https://t.co/DhSb9JsDnW

[Pascal Senn 🌶 @Pascal_Senn]

@michael_staib and me will be at GraphQL Day in Amsterdam on June 9th and 10th. We still have a few free tickets for you! Send me a DM if you are interested.

See you there!

Find out more: https://t.co/5Ym0h63PlL

[Pascal Senn 🌶 @Pascal_Senn]

@StatisticsFTW @cnakazawa yes - but thats a backend problem...
graphql and its patterns make a lot of sense on the client, but i'd argue you get even more benefits when you have a graphql backend. especially when client and backend talk the same language..

[Pascal Senn 🌶 @Pascal_Senn]

@cnakazawa sure - i meant more that the concept of fragments and composition is part of the graphql query language and this is leveraged by relay, apollo client, urql etc.

[Pascal Senn 🌶 @Pascal_Senn]

@cnakazawa i see - already sending this through to folks that never got to experience relay so they can finally know what i am talking about 😅
so you'd say - fate partially solves a problem on a client that graphql solves higher up in the stack?

[Pascal Senn 🌶 @Pascal_Senn]

@hrgooo @rickyfm hmm can you elaborate? isnt this pretty similar to a subscription and @appendNode and @deleteRecord ?

[Pascal Senn 🌶 @Pascal_Senn]

@cnakazawa So essentially: just because the backend does not provide a GraphQL interface? also, I've read through the docs and I like fate, dont get me wrong.

[Pascal Senn 🌶 @Pascal_Senn]

Wrapping up another great API Days. Looking forward to seeing everyone next week at GraphQL Conf in California - registration is still open and free to attend. https://t.co/UjQr4D0oP3

[Pascal Senn 🌶 @Pascal_Senn]

GraphQL wasn’t made for AI.

But it might be one of the best ways to talk to it.

https://t.co/4AXIHTfEcP

[Pascal Senn 🌶 @Pascal_Senn]

Clauding (verb) — Relentlessly hammering prompts into Claude with zero strategy and full confidence. You don’t understand the output. Claude doesn’t understand the input. But eventually, somehow, it works.​​​​​​​​​​​​​​​​
#Claude

[Pascal Senn 🌶 @Pascal_Senn]

Keynote Speaker:
“AI is revolutionizing healthcare research and will help us defeat cancer. At scale. Very soon.”

Meanwhile, Engineers (prompt to ChatGPT):
“Give me 5 better names for the variable _aggregatedContextualConfigurationOverrideValue.”

[GraphQL @GraphQL]

🔥 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 @GraphQL]

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

https://t.co/kSTHx4l9om

[GraphQL @GraphQL]

This week's #graphqlstar is the one and only @Pascal_Senn 🎉 Pascal has been an important contributor to the composite schema WG, website, and of course the spec! Thank you, Pascal!

[Pascal Senn 🌶 @Pascal_Senn]

@davidfowl @GKedzierski appsettings.json via https://t.co/41unRa4chk

[Pascal Senn 🌶 @Pascal_Senn]

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! 🌐✨

[Pascal Senn 🌶 @Pascal_Senn]

#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.

[Pascal Senn 🌶 @Pascal_Senn]

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!