Discover tRPC's potential in building end-to-end type safe RPC APIs in this insightful blog post. Perfect for developers seeking innovative solutions for server-client separation in webapp development.

A painful lesson from production that brought several engineers almost to tears: *Please* add PATCH endpoints to your public APIs.

A way to embed tweets in static sites with full pre-renders and live updates using just 9kB of client-side JavaScript, 2 HTTP requests, and full reader privacy ✌️

The quickest way to simplify a complex function with lots of logic is to turn it into data. A lesson from production

A fun problem for RESTful APIs: Did you get 404 because your URL is wrong or because the resource wasn't found?

RESTful APIs are like Agile – everyone does it differently and if it isn't working, it's your fault for doing it wrong. 🤨

Common problem in engineering teams: Stepping on each other's toes. JAMStack can help.

In this episode of CodeWithSwiz, we tried NextJS's support for /api routes – code running on the backend. In a word – Wow

"He's a frontend guy, is this even a fair question to ask?" The head of engineering was worried about our systems design question …

Let's have a look at hyow GraphQL makes queries so much easier and more pleasant than REST

We live in exciting times my friend. It's never been this easy to build a webapp and make your first $1,000/month.

What if I told you modern tools let you build and launch a small webapp in 30 minutes? Complete with SSL, a .com domain, a database, a documented API, CDN hosting, fast static initial loads, and a hydrated SPA? That's the challenge I posed at Silicon Valley Code Camp this weekend. The audience didn't believe me, so it was time to perform some magic. 🧙

You've probably seen web notifications before. YouTube shows them when it goes to a new song, Facebook pings them when a new message comes in, scammy websites ask for permissions and you say no. The usual. You can fire those notifications from anywhere inside your JavaScript.

Both superagent and fetch() enable you to talk to a server. The first produces clean code that gets nesty if you need many things. The second produces clean code that is Promis-y and sometimes cumbersome. The difference between superagent and fetch() isn't that one sends your headers as-given and the other lowercases their names. The difference is that superagent sends a cookie and fetch() doesn't!