Building a Better Web
June 11–12, 2018: Training
June 12–14, 2018: Tutorials & Conference
San Jose, CA
Alex Banks

Alex Banks
Software Engineer and Owner, Moon Highway

Website | @moontahoe

Alex Banks is a software engineer for Moon Highway, Lynda.com author, and JavaScript enthusiast. He started writing code at the age of eight years old on his first computer, a Tandy TRS-80. In 1995, Alex developed his first website and has been hooked ever since. Alex now lives in Tahoe City, California, and he provides classroom and online-based training regularly for Yahoo, eBay, PayPal, Stanford University, and other companies across the country. When Alex isn’t in a classroom, he spends his time developing applications, learning new technologies, and writing custom training curriculums with Moon Highway. He is also the author of O’Reilly’s Learning React and Learning GraphQL.

Sessions

9:00am - 5:00pm Monday, June 11 & Tuesday, June 12
Learning GraphQL, React, and Apollo
Location: 212 C
Alex Banks (Moon Highway), Eve Porcello (Moon Highway)
Average rating: *****
(5.00, 1 rating)
GraphQL, a query language for your APIs, can make data fetching simpler and more declarative. There’s a lot of hype around the technology, but how do you actually use GraphQL to make your life easier as a developer? Join Alex Banks and Eve Porcello to learn GraphQL from the ground up. You'll explore graph diagrams, GraphQL’s type system, tools like Apollo and Graphcool, and more. Read more.
3:35pm–4:15pm Thursday, June 14, 2018
Group games with GraphQL subscriptions
Web services and APIs
 Location: 210 B/F
Secondary topics:  Developer Experience Track: Tools, Platforms, and Techniques, Hands-on, Technical
Alex Banks (Moon Highway)
Average rating: ****.
(4.33, 3 ratings)
Instead of allowing our phones to make us oblivious to the world around us, what if we were able to use them to facilitate interactivity in the real world? Alex Banks details (and invites you to participate in) interactive challenges that use the power of GraphQL to create graphable relationships, covering the code that produces each activity and the data produced by the activity itself. Read more.