I enjoyed the read and still have the Final Form stickers you gave me so long ago! If I was choosing a type system at that time, I would've gone with Flow too.

And good riddance ✌️

Same — I use em a bit too much 😂

Lastly on the tech side of things, I'm quite happy with how the tech stack has survived. It's full stack Next.js with tRPC and Prisma. Aside from being 1-2 major versions behind on some libraries, it's still working and stable with zero issues getting the app running again.

I also think that focusing on quality of event data, with potential for manual curation and content matches is really useful. For example with family friendly events, it's really important to know how well equipped the event facility is with things like baby changing tables.

So, I initially was thinking location, but that made less sense as I thought more about it. My neighborhood is small and for most events people travel to Manhattan anyway. I like the idea of focusing on categories as that's broader and would promote the service to more people.

Makes sense, I like the ticket idea.

Nice! I've already been doing some of this without knowing but I like having a consistent format for teams to follow. Would CI integration be useful to you or have you seen enough effectiveness without?

Also, it's all local to your project. Install it as a dev dependency, and run it via `npx tsnew`. The workflow is optimized for this to avoid having to wrap tsnew within your own custom script, but you still can if you really want to extend it that way.

Compared to other scaffolding tools, tsnew will allow you to write templates in `.ts` files, meaning that you have full control over your templates. Template literals are the default, but you can use any templating language.