Andrew McGivery
@andrewmcgivery
Followers
1K
Following
9
Media
409
Statuses
8K
Solutions Architect @apollographql
Canada
Joined March 2009
well deserved shoutout to @mcpjams 🤟 great for testing even if you are paying for chatgpt
2
1
3
great session by @andrewmcgivery walking through @apollographql 's framework for ChatGPT Apps their approach will appeal especially to frontend devs who want to focus on frontend concerns and use familiar graphql apis
2
3
4
OpenAI's new Apps SDK is changing how we think about embedding third-party apps into ChatGPT. Join us tomorrow to talk about what emerging protocols we’re seeing and experimenting with for agent development. https://t.co/gQvz5QQrFI
#MCP #ChatGPT #AgenticDev #AI #A2A #GraphQL
1
2
3
Curious about building Apps for LLMs? Join me and @andrewmcgivery tomorrow at 1pm et to learn more about what future these apps unlock and the DX we are working on here at @apollographql to make building these a delightful experience as the space evolves.
1
3
4
In one week join me and @andrewmcgivery as we explore Open AI apps SDK We will cover what the apps landscape looks like right now and why you might want to build an app for an LLM. You will also see a live demo of the Apps SDK with @apollographql MCP Server and Apollo Client.
1
2
10
"By 2027, more than 60% of enterprises will use #GraphQL in production, up from less than 30% in 2024” per @Gartner_inc. Find out why! https://t.co/agtaEaF8vV
#ApolloFederation #Platformengineering #APIOps #APIs
1
3
15
Have you heard? #graphqlsummit is back this fall! NYC 🍎🗽 October 8-10, 2024. Mark your calendars, submit your proposal to speak, and stay tuned for more updates ➡️ https://t.co/QiOJF3JOZ0 You won't want to miss this! 🌟 #GraphQL #GraphQLFederation #APIPlatform
3
7
10
🚀 Why Netflix Platform Engineering Chose Federated GraphQL Explore Netflix's extensive API journey and the adoption of GraphQL in an insightful fireside discussion with Bruce Wang, Director of Product Platform Systems at Netflix during the GraphQL Summit 2023. 🚀
0
5
12
Node.js, (cloudflare) workerd, (aws) llrt, (oven) bun, it's exciting, but I wonder what would've happened if they all focussed on the same thing; making node.js better.
I'm excited to see LLRT finally open for everyone to try!! I've said it before, and I'll say it again: Lambda must either build a runtime optimized for their online scaling model, or they need support some type of multi-concurrency. https://t.co/6ejnUuozwN
28
15
214
Funny seeing @Uber_Support gaslighting it’s customers in replies when hundreds (thousands?) of tweets are being thrown at them that @UberEats is down. Maybe acknowledge the outage and get your team on it instead of copy/paste “please DM us with details”. 🤷♂️
0
1
2
Watch the full talk from @dan_boerner! https://t.co/UzRneGmPo6
0
0
0
✅ Bring a declarative layer and a control plane to the middle, enabling us to apply declarative governance in this crucial layer
1
0
1
✅ Increasing and magnify investments by connecting and composing independent APIs together
1
0
0
✅ Provide an insulating contract between presentation and application layers that is flexible enough to manage the constant change while stable enough to prevent breaking changes
1
0
0
The end goal: ✅ Enable rapid self service for presentation clients by replacing one-off handwritten BFF apis with declarative queries
1
0
0
It is common to hear GraphQL and REST pitted against each other as competing technologies. While this may be true in some cases, most organizations who have adopted GraphQL utilize both for different purposes and at various layers of the stack.
1
0
0
🤔 GraphQL versus REST 🤔 ❌ This is the wrong question! ❌ GraphQL is for ✨ The Middle ✨. https://t.co/UzRneGmPo6 🧵… more in thread…
1
0
1
imagine a figma-like infinite workspace in visual studio code. prototype built using react and @code's api extension.
138
179
2K
my favorite chrome bug, from 2009: Head in place of close button
38
2K
20K