Most of Rauch's original Next.js codebase has been deleted
Guillermo Rauch · How Vercel found extreme product-market fit by focusing on simplification | Guillermo Rauch (CEO) · Nov 2, 2023 · at 20:21
Guillermo Rauch discusses the evolution of Next.js from his initial prototype to an enterprise framework rewritten by engineering teams over time.
0:00 / 0:02exact quote · 3.0s
▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark
“Most of my original Next.js code is deleted now.”
quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →
More from Guillermo Rauch
Future websites will be dynamically generated just-in-time for individual users
“The thing that we want to accomplish with the web is that we want to make it truly an AI driven web where when you go to a website, you get a copy of that page that is just for you generated just in time. And it knows it has all this context about what you wan…”
Adaptive AI systems will eliminate the need for major software re-platforms
“So using AI to continuously modernize, you can think of systems of the future that are self-tuning and adaptive. We no longer have to catch the latest trend or optimization By doing major re-platforms.”
Human software engineers will write very little code in 20 years
“If I had a bet, since you gave me the 20 year out, I would say yes. I think very little code, if any, will be written by engineers.”
Developer experience at all costs is counterproductive for businesses and developers
“The framework that I use today is developer experience at all costs doesn't work. It it's bad for the vendor startup enterprise. It's bad for the developer because the end date is like the good old adage of the customer is king. We all get paid. You, me, like …”
Pure developer experience frameworks failed because user performance never solved itself
“There was a lot of optimism that certain things that were really good developer experiences, For whatever magical reason, let's call it Moore's law or just hopium. They were like, okay, the user part will figure itself out. You know, fast forward a few years, …”
Complex infrastructure software does not have to sacrifice developer experience
“Oh, if there is this really complicated message broker queue orchestrator workflow system. Yeah. It's really hard to use and it must be hard to use because it's solving really hard problems. That's actually not the case. Like you can do both. And that's where …”