He’s cooking
24.01.2026 15:16
👍 3
🔁 0
💬 0
📌 0
He’s cooking
It does compile now.
Thank you 🖤
I want to help developers become an order of magnitude more productive, and help more people contribute to building software.
This is going to take a *lot* of education and retraining. So expect more videos soon, and if you have ideas for what I should teach, let me know!
This is why some experienced devs are having a great time with AI. They can ask for a pattern like "add an exponential backoff" instead of “make it more robust to errors” which may or may not work.
3. We need to help developers become even more competent. AI may end up writing most of your code, but you have to review, understand, and maintain that software.
2. We need to teach experienced developers how AI can automate the tedious parts of coding, or save them time reading docs and fixing bugs.
I'm joining Cursor to teach the future of coding!
There are millions of developers learning how to use AI and they need pragmatic advice:
1. We need to teach new developers strong foundations, so they know what to learn, and how to solve issues when debugging.
(1/5)
ICYMI he has them in a playlist, in order you should watch
www.youtube.com/playlist?lis...
Thank you - I appreciate the correction because it’s not the first time I’ve had to debunk “Vercel pays a bunch of DevRels to push Next”
Quite a few do, and I also agree that you don’t need to use it. Client react is okay too.
DevRel is me and Delba for Next. For docs, we just hired a new person Joseph.
The DevRel team has never been larger than 5 people over the years 🤔
1. Browsers handle title/metdata outside of <head> just fine
2. We haven't seen any SEO impact (this is the same pattern sites like Amazon use, it's not novel)
3. It's not Vercel specific (this is standard `next start` behavior)
4. This was a community requested feature
The post is FUD. I don't have the energy to write up a long response on why yet, but it's simply not accurate.
We can't 😭 It's a GitHub limitation
Glad to hear it! Yeah the new stateless protocol is much better.
Yeah but the story is even easier. You can run compute, either before or after the cache. That’s p much it
Writing has been on the wall for a while, just finally starting to slowly roll out example updates, followed by actually deprecating the product soon (and change management)
We moved forward with Fluid compute instead
`dynamic` can be the entire route. Make your `page.tsx` file render the `<Route>` component and use `dynamic`.
Can you share what issues you saw so we can fix?
What docs are you referring to? I don't believe we show this anywhere
Vercel for the backend is Vercel 😁
Can deploy APIs, connect to databases/queues with first-party integrations, built-in logging/observability.
And can also bring & use your backend frameworks (e.g. Express, Hono, etc)
You can also have v0 generate vanilla HTML if you don’t want React stuff. Also can ask it for Svelte.
Andrew has made some massive improvements to prefetching, including fetching segments. It's under an experimental flag `clientSegmentCache`.
x.com/acdlite/stat...
Myth: you can fetch data with "use server"
Taking your RPC explanation further, could talk about how you can think of it like a POST, and the broader umbrella of Server Functions as maybe where you could have a GET.
Myth: RSC requires dynamic rendering
You've covered it already in previous posts, but linking back to your longer explanations would be nice.
Myth: RSC doesn't work with CSS-in-JS
It would probably be helpful to talk about runtime CSS-in-JS versus zero runtime variants.
