GraphQL Meetup #12

Join waitlist?

21 on waitlist

Location image of event venue


🙌 Join us for the 12th GraphQL Berlin Meetup and fantastic speakers.

🍕🍹 As always there will be free food and drinks, so please feel free to come and chat with us about GraphQL!


⏰ Schedule

6:30 PM: Doors open
7:00 PM: Welcome & Announcements
7:10 PM: 🗣Life is hard and so is learning GraphQL (Carolyn Stransky)
7:40 PM: Break
8:00 PM: 🗣Typed Resolvers – PureScript GraphQL (Hendrik Niemann)
8:30 PM: Hang out & Chat about GraphQL

🗣 Talk 1: Life is hard and so is learning GraphQL (Carolyn Stransky, Frontend Developer @ Blacklane)

Learning a new technology can be daunting. For many of us, the way we try to make sense of a new technology is through their documentation and the examples we see online. The problem with GraphQL is that - because there’s no “vanilla” GraphQL - there’s no central hub for all of the information and tooling necessary to learn. While documentation is meant to serve as a tool for teaching, it’s underutilized and scattered throughout our community.

Consider this talk a voyage through the ups and downs of learning GraphQL. Along the way, we’ll touch on the major pain points faced by GraphQL beginners and how we can better enable our docs for learning and comprehension.

Carolyn Stransky is a frontend developer and former technical writer based in Berlin. She currently works at Blacklane and teaches at ReDI School of Digital Integration. You’ll usually find her looking at memes or taking selfies in the nearest restroom.

🗣 Talk 2: Typed Resolvers – PureScript GraphQL (Hendrik Niemann, Lead Software Engineer @ Kiron Open Higher Education)

Are you writing your server side GraphQL code in a strongly typed (compile to JS) language like TypeScript? If so you might have noticed that the most important parts of your code – the resolvers - require you to write annotations yourself. While writing annotations can catch some errors by requiring you to be explicit, mistakes can still be made and lead to runtime errors. What if the types could be generated or inferred from the GraphQL schema definition?

In the last years a lot of the efforts in the GraphQL community were targeted at getting started with GraphQL but recently there is a shift that tries to make writing GraphQL servers safer and more fun at scale. In this talk we will find out what the newest developments in the ecosystem have evolved to statically type GraphQL resolvers. And who knows, maybe we will find a pure programming language with a type system that advanced and safe that resolvers are simply typed out of the box.

Hendrik works on making the world a better place at Kiron Open Higher Education. He develops GraphQL APIs for over two years and has authored multiple opensource projects around GraphQL and static types.