iiinova — where your digital self keeps evolving

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!

2130

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.

190

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.

150

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.

160

leerob @leerob.com · 15/06/2025

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)

91020

ICYMI he has them in a playlist, in order you should watch www.youtube.com/playlist?lis...

0110

leerob @leerob.com · 15/06/2025

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”

150

leerob @leerob.com · 14/06/2025

Quite a few do, and I also agree that you don’t need to use it. Client react is okay too.

leerob @leerob.com · 14/06/2025

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 🤔

1100

leerob @leerob.com · 13/06/2025

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

leerob @leerob.com · 13/06/2025

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.

leerob @leerob.com · 10/06/2025

We can't 😭 It's a GitHub limitation

050

leerob @leerob.com · 31/05/2025

Glad to hear it! Yeah the new stateless protocol is much better.

020

leerob @leerob.com · 31/05/2025

Yeah but the story is even easier. You can run compute, either before or after the cache. That’s p much it

leerob @leerob.com · 28/05/2025

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

leerob @leerob.com · 26/05/2025

`dynamic` can be the entire route. Make your `page.tsx` file render the `<Route>` component and use `dynamic`.

leerob @leerob.com · 19/05/2025

Can you share what issues you saw so we can fix?

120

leerob @leerob.com · 14/05/2025

What docs are you referring to? I don't believe we show this anywhere

020

leerob @leerob.com · 12/05/2025

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)

020

leerob @leerob.com · 11/05/2025

You can also have v0 generate vanilla HTML if you don’t want React stuff. Also can ask it for Svelte.

220

leerob @leerob.com · 10/05/2025

Andrew has made some massive improvements to prefetching, including fetching segments. It's under an experimental flag `clientSegmentCache`. x.com/acdlite/stat...

x.com

160

leerob @leerob.com · 08/05/2025

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.

leerob @leerob.com · 08/05/2025

Myth: RSC requires dynamic rendering You've covered it already in previous posts, but linking back to your longer explanations would be nice.

leerob @leerob.com · 08/05/2025

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.

2110

It's running on the same Vercel infrastructure as everyone else. It's a pretty simple site, although we do have some overly heavy SVGs on the homepage I'd like to replace.

I got in touch with the TikTok creator. They took down the video. Unfortunately they got scammed by a job posting on Indeed claiming to be from Vercel.

This was false. The TikTok poster took down the video. They unfortunately got scammed by a got posting on Indeed claiming to be Vercel.

It's not. Appears to be some kind of skit.

100

I'm doing an AMA on /r/vercel, come hang out and ask questions! www.reddit.com/r/vercel/com...

0260

That's like saying solar companies invented LED lights to leave lights on longer. The whole point is to use fewer resources. The default behavior of Next.js is to prerender. And with PPR we're trying to prerender to static as much as possible. You're only using compute when it's necessary.

140

Yes, Vercel employs me. Yes, I want Next.js to be great when self-hosting or not on Vercel. Will I recommend Vercel first if someone asks me? Also yes, or I wouldn't work here if I didn't believe in the product.

150

That's not necessarily true. Yes, you can have unconscious bias, but part of my job is confronting bias and being pretty open about it.

This argument gets confusing to me because Vercel also supports SPAs who want the PR previews as well. From a Vercel perspective, we want to support *all* frameworks and types of apps.

There's a bunch exploring RSC: • parcel: parceljs.org/recipes/rsc • waku: waku.gg • redwood: redwoodjs.com/blog/rsc-now... • mfng: github.com/unstubbable/... • kotekan: github.com/bndkt/kotekan • tangle: github.com/lubieowoce/t... • twofold: github.com/twofold-rsc/...

490

If you figure out a good way to get this through, please let me know. I've tried and it hasn't really landed, probably cause everyone assumes my bias.

3100

This isn't the same thing, though. - Agree we want to (and will continue to) invest in React - We also invest in other frameworks and libraries - RSC is not tied to Vercel, so it's not vertically integrated

Been there, absolute nightmare material 😱

Yeah I think something like this is closer, maybe too verbose

120

To clarify, are you advocating for not showing inline "use server" usage, or just this specific example?

IMO "use cache" is similar to all of the upcoming Next.js changes (dynamicIO, PPR). If we could have known from the start, we'd short circuit there. But the only way to arrive at these APIs is to put something out there, watch and listen, and iterate. Unsatisfying but seems to be true.

1120

leerob @leerob.com · 27/04/2025

If you're using AI models, how are you making sure it uses the right version of a given library? llms.txt? MCP? Context7? RAG? Web search? Another acronym? Seems like there's a million ways.

390

I hear you, but this would be a pretty big breaking change, so likely not something we would do soon. Longer term, I'd like to move away from dotenv entirely, personally.