Tim Hingston retweeted
We're looking to interview developers to understand the challenges around adopting and using #GraphQL. Participants will receive a $125 gift card.
If you’re interested, please take the quick survey here: tinyurl.com/2ts7byuf
Tim Hingston retweeted
Today, we're happy to announce our $130 million Series D, valuing Apollo at over $1.5 billion.
Many thanks to the Apollo community and team for helping us achieve this incredible milestone! 🚀
Tim Hingston retweeted
Meet Apollo Sandbox, your new favorite tool for local #GraphQL development. Sandbox is our new open GraphQL IDE with one-click query building, intelligent field and path search, integrated #schema docs, and more. We can’t wait to see what you’ll build! bit.ly/2RX8Tzn
Landed a new article on our @apollographql blog this week, enjoy!
Using GraphQL Fragments for safer, cleaner, and faster code apollographql.com/blog/graph…
😍
⚡ There's a new way to do local GraphQL development.
We’re thrilled to announce Dev Graphs: a way to get all of Explorer's productivity-boosting features in your local development environment 🎉.
This powerful GraphQL IDE is free to use. Forever.
apollographql.com/blog/apoll…
Seeing this scene, and totally ignoring how and why this is happening, I do slightly feel like I'm missing out...
Tim Hingston retweeted
Donald Trump’s attempts to stop votes from being counted are the actions of a desperate man trying to cling to power just a little longer.
It's undemocratic. It's pathetic.
And it won't work.
Thanks to everyone who came by the session today! Great to hear so much interest in GraphQL at GIDS 2020!
This Post is from an account that no longer exists. Learn more
Tim Hingston retweeted
🎉 We're excited to announce "GraphQL at Enterprise Scale", a completely free ebook written by Apollo Engineers.
Learn how to scale GraphQL in the Enterprise with Federation and Apollo Studio.
apollographql.com/blog/annou…
Looking forward to presenting some strategies for building data-driven apps at #gids @developersummit in October! Lots of learnings to be shared from working at @apollographql with SPAs, components, #reactjs and #GraphQL
#GIDS has metamorphosed into a virtual experience in 2020, streaming Live to #developer isodesks, July-Dec 2020. 7 multi-stream conferences, 100+ international speakers, 200+ breakout sessions, 25+ lively workshops, Virtual Expo, Live Demos. Don't miss it: developersummit.com
Tim Hingston retweeted
"GraphQL is mature, and it's approachable." — @debergalis on the growth and proliferation of GraphQL in the last year #graphqlsummit
Tim Hingston retweeted
We're excited to announce our $22 million round of growth funding, led by @a16z and @MatrixPartners. 🚀 Big thanks to the amazing Apollo community, we couldn't have done it without you!
blog.apollographql.com/apoll…
Tim Hingston retweeted
We're excited to announce the 2019 edition of GraphQL Summit will take place in San Francisco on October 29-31! 🎉
Register before 2/24 and receive 60% off your ticket:
graphql-summit-2019.eventbri…
Tim Hingston retweeted
Very proud to launch our new Apollo GraphQL Platform today, an out-of-the-box way to do GraphQL right. #graphqlsummit #GraphQL blog.apollographql.com/intro…
Tim Hingston retweeted
Holy Moly! @martijnwalraven just blew my mind with Apollo Gateway 😱 one graph with distributed execution.... Seriously incredible. @apollographql never ceases to amaze with every feature they announce.
Definitely check out his 'Schema Composition' talk at #graphqlsummit
Loved this talk from #code18 by Lindsay @auxesis - lots of great advice on how to work better as a distributed team.
Here's slides from my whirlwind #Code18 talk on bootstrapping, growing, and adapting distributed teams speakerdeck.com/auxesis/mana…
Tim Hingston retweeted
Awesome analogy by @Mandy_Kerr between using `any` for everything in TypeScript and using `<div/>`s for everything in HTML.
You lose the benefit/meaning of the tool/language.
@webdirections #code18
👏
Tim Hingston retweeted
Watching @Mandy_Kerr draw a line between using the `any` type in a type system and using `div` in html — both are generic and lack meaning #code18















