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

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

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

Congrats to @martinbonnin and @Pascal_Senn for being elected into the GraphQL TSC! graphql.org/blog/2025-02-0…

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!

@davidfowl @GKedzierski appsettings.json via swisslife-oss.github.io/Confix/

@GKedzierski How are you managing config?

The more I spend time in the devops space looking for what should be simple solutions to some problems I am appalled at the tooling state of the art. Absolutely developer hostile. It's clear why everyone tries to rebuild heroku.

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.

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.

@philliphaydon You dont need to be facebook for this to make sense.

@philliphaydon I think the biggest missconception about GraphQL is that it's just about multi modal, typesafe and optimized data fetching. It's not. It's a way expose your business model where the frontend dev, the backend dev, the PO and the stakeholder all talk the same (ubiquitous) language.

2024 and people still trying to justify GraphQL outside of Facebook.

@SimonCropp @philliphaydon @wdolek Aren't all of these problems caused because you essentially expose the database directly with github.com/SimonCropp/Gra… instead of exposing a business layer?

@philliphaydon @wdolek permissions, performance, debuggability context: i was a core contributor to graphql .net. and still maintain github.com/SimonCropp/Gra…, github.com/SimonCropp/Gra…, and github.com/SimonCropp/Gra…

bessey.dev/blog/2024/05/2… 🖕GraphQL Dumb solution looking for a problem to solve.