The first version was great, but it didn't use the real ChatGPT. I made some updates and now it's better than ever.

Trying to decide if going serverless is for you? There are a few trade-offs you need to consider first.

You've undoubtedly heard about serverless and read about the benefits. But implementing serverless into your app doesn't have to be all or nothing.

I've been building APIs for years, but recently discovered the power of inferring data from user sessions for a better developer experience.

Learn why API specifications are essential to the long-term success of every application and what you're missing out on if you don't have one.

Static sites are great but if you want to schedule something in the future, they leave something to be desired.

The location of your serverless app matters more than you might think. You could add significant latency and cost if you don't take it into consideration.

You probably do a few things every day that could be automated. Get your time back by building quick serverless integrations to do them for you.

Developer experience is a thankless part of software. When it's good, it's good. When it's bad... everybody talks about it and nobody uses it.

I built a serverless app that asks ChatGPT to write workouts for me every day. I couldn't be happier with the results.