The Schedule

Let's learn great patterns you can use, and also the strengths and weaknesses of each, so you know which to reach for to provide your components the flexibility and power you need

I just released a complete rewrite of my website. This isn't your regular developer blog though. You can actually log in, record some audio for a podcast, choose a "team" to be a part of, connect with discord, and much more. I'm using some of the coolest modern tech around including React, Remix, Prisma, Postgres, Redis, Fly.io, tailwind, TypeScript, and more!

I want to take you on a tour of some of the highlights and talk about some of the problems I faced and decisions I had to make while building a brand new modern website in 2021.

For years, not being able to cache GraphQL was considered one of its main downsides compared to RESTful APIs. Not anymore. GraphCDN makes it possible to cache almost any GraphQL API at the edge, and not only that but our cache is even smarter than any RESTful cache could ever be. Let's dive deep into the inner workings of GraphCDN to figure out how exactly we make this happen.

Building on the web today often involves a number of choices and a lot of effort. This talk explores Tejas’ ideal tech stack that allows for a high level of predictability and velocity, even at massive scale.

In this workshop, we'll do a complete walk-through of building web applications from A-Z with Hasura. At the end of our time together, you'll have a production-ready GraphQL API with access controls, caching, subscriptions, and more.

Creating 3D experiences in the web can be something that sounds very daunting. I’m here to remove this idea from your mind and show you that the 3D world is for everyone. For that we will get a model from the 3D software Blender into the web packed with animations, accessibility controls and optimised for web use so join me in this journey as we make the web more awesome.

Will visual tooling improve the way we develop software? With the rise of no- and low-code tools, many more non-technical people are creating websites and apps than ever before. But what does this mean for us developers? In this talk, we will explore how we can use low-code dev tools to our advantage to make us more efficient, even as we're still writing full code. And chances are, you're already using low-code tools without even realizing it. Learn how visual development unlocks the potential for robustness, collaboration, and instrumentation, making our code do more than just be error-prone lines of text, but instead become powerful communication devices for the entire team.

"Oh, you found a bug? It's probably cache. " is the unfairest sentence on the web. Cache
is not the bug, not understanding cache is. Let's have a look on how it works and what we can
do to leverage User Experience to the next level with it. Let's flush cache from a bug to a feature together!

The history of the web can be divided into evolutionary development leaps. The age of inline scripts, the age of jQuery, the age of SPAs, the age of JAMStack...

We are now entering the next stage that has been carefully prepared in the past few years. Let me introduce you to the world of modern monorepo solutions and introduce you to the benefits you will reap by using them in every project size and setup. It's time you automate those boilerplate tasks and reduce the bottlenecks so you can focus on what truly matters.

Get ready for the next leap! Welcome to the age of monorepos!

The way we build Apps usually involves consuming a RESTful API that we communicate with over HTTP. We design contracts for those APIs to define the way they work and, to have a formal spec for them, the Swagger IDL was proposed back in 2011 to become the OpenAPI Spec in 2016.

At Vercel we love NodeJS and we built almost every service in our system on top of it. We felt the need of having a spec for our API but of course, we never wanted to write it manually. There is almost no support to auto-generate an OpenAPI Spec in the NodeJS ecosystem but since the wide adoption of static typing, it became possible to write a generator for this purpose.

In this talk, we will explore how Vercel API internals evolved since 2017, from a set of minimalistic multi repository services to a monorepo sitting on a tailored framework. We will see how we built a static analyser tool out of it that allowed us to infer a Spec from the implementation of our APIs and how we integrated it using Vercel in our workflow to get alerted on API changes.

When building an app, I often depend on a handful of building blocks to get the job done (like a database, API, authentication layer, and file storage).

Using these core components, I can build out most of the types of applications I would like to, or at least get most of the way there. So what did this look like in web3?

After working, researching, experimenting, and building things over the past 8 months or so I’d like to share what I’ve learned in this talk.