Does anyone have some non-trivial examples of `useFormState()` usage? Liiike: - client-side validation - optimistic updates - form lib (like react-hook-form) integration? - nested form values - how to structure the return to display errors, previous form data submit etc

RT @buildsghost: Before you go out and do a bunch of TypeScript magic to avoid JSX nesting, remember you can also just do something like th…

I think I might've been unnecessarily anxious about this. Any call to `cookies()` - which all private stuff depends on - automatically opts nextjs out of the caching

Yo @microsoft, if you ain't paying @AndaristRake for all his work on @typescript yet, you should start yesterday

Did you know that you can use @trpcio as the data layer in @nextjs to get a lightweight & secure layer with auth-checked code & runtime validated input/outputs? You don't even need to use trpc routers, client, or the react libs We should probably make a blog post about dis 👀

New toy available! Esp excited about: - Object.groupBy - Preserved Narrowing in Closures Following Last Assignments - NoInfer devblogs.microsoft.com/types…

New life improvement in @trpcio 😱 Enabled:false 😎 skipToken When implementing this, I realized how much work @TkDodo @jullerino @alexdotjs @tannerlinsley and others are putting so we have good DX. We should appreciate them more!

remember vision pro?

One of my mistakes when building products used to be adding dependencies too early. Don't add a cache store until your database starts slowing down and you've tried optimizing it with indexes. Even then, start with a basic in-memory cache before adding Redis or Memcached. Don't add a full-text search engine until you've pushed your database as much as you can with whatever full-text search features it has. Don't add a message queue until your background jobs are starting to struggle with the load. Even then, start with a simple in-process queue, or see if you can use your database as a queue. Only then should you consider adding RabbitMQ, Kafka, or whatever. Every new dependency comes with a cost, one more thing to maintain, and one more thing that can go wrong. These are the things you should avoid as long as you can.

Did some fixes on a socket.io Objective-C client 13 years ago

"While building a feature, we performed a database migration command locally, but it incorrectly pointed to the production environment instead, which dropped all tables in production." I'm surprised this sort of incedent doesn't happen more frequently tbh I've had prod access to dbs in most places I've worked and even knowing I sit on the credentials make me paranoid

"Thou shalt mock nothing [except third party services] in tests" - @alexdotjs Do you agree?

Integration tests > Unit tests 🤗