kylegill

Wasn't familiar with that python doc, but I love it! Bookmarked.

I agree, it's also (ironically) sometimes hard to disambiguate the differences between Next.js/Vercel/modern versions of React. I like the latter two! The former has just given me some whiplash.

I find the ending particularly funny, we have a small team where we're often building things in-house that we should probably just buy, or rely on manual processes for.

The fumbling with "oops, there's some test data in here" and the issues with the service worker hit a little close to home from some of our demos I've been a part of.

I've had good and bad managers, and the best ones were always ones that were good at doing something. Even if it was something less related to what I did on the day to day it's nicest when someone levels me up vs mostly being the communication glue between me and the rest of the company.

> Vercel is easy to use and comes with batteries

On our team, we deploy our web app through Vercel primarily because of this (maybe there is some hype factor bias in there too?..). Everything else we rely on runs on AWS. We don't necessarily need Vercel for any of the edge computing or serverless environments, but the experience of building, previewing, and deploying our app is FAR superior to AWS's Amplify offering because it just works.

Trialing Amplify for a few weeks led to a world of hurt, leftover build artifacts in our accounts, failed builds left and right, unreliable preview environments, etc.

I'd still consider myself a bozo (3 years out of school), but may I offer a humble thanks for your shoulders that many of the rest of us stand on!