Pinned Tweet
The Road to Next is LIVE 🚀
5 months ago, I launched the early access. With feedback from hundreds of students, it's grown into a self-paced full-stack bootcamp.
Honestly, I should've just called it The Road to Full-Stack 😅
Whether you're into Next.js or just want to level up this is for you.
🎁 Giveaway
3 random people who like & share this post in the next 24 hours will get free access to the course!
Check it out in the replies 👇
5 months ago, I launched the early access. With feedback from hundreds of students, it's grown into a self-paced full-stack bootcamp.
Honestly, I should've just called it The Road to Full-Stack 😅
Whether you're into Next.js or just want to level up this is for you.
🎁 Giveaway
3 random people who like & share this post in the next 24 hours will get free access to the course!
Check it out in the replies 👇
15
46
160
27,153
Robin Wieruch retweeted
Love this post by @rwieruch about using libraries vs. building your own. It was always a trade-off, especially when it came to custom design, but agentic coding dramatically moved the crossover point toward the primitives: robinwieruch.de/agentic-coding…
7
8
92
9,971
One of my students: "I heard Next.js is slow." 🐌
Meanwhile, my team and I are shipping a freelance client's enterprise project: 10 Next.js apps, shared look-and-feel, one monorepo, each app deployed individually on AWS. It flies 🚀
Meanwhile, my team and I are shipping a freelance client's enterprise project: 10 Next.js apps, shared look-and-feel, one monorepo, each app deployed individually on AWS. It flies 🚀
32
8
309
39,917
FWIW 👉 Learn full-stack development, from UI to database, with a complete video course 👇
road-to-next.com
road-to-next.com
1
0
2
1,820
👀 React Insight
Most prop drilling problems aren't global state problems.
They're composition problems. Keep it simple.
Most prop drilling problems aren't global state problems.
They're composition problems. Keep it simple.
4
6
35
3,079
👀 JS/TS Monorepo Insight
We thought we could manage 10+ React applications in an enterprise setup across teams.
Dependency drift proved us wrong. Catalogs made it simple.
We thought we could manage 10+ React applications in an enterprise setup across teams.
Dependency drift proved us wrong. Catalogs made it simple.
32
40
666
71,222
FWIW 👉 Learn full-stack development, from UI to database, with a complete video course 👇
road-to-next.com
road-to-next.com
0
0
0
1,681
A thread about tools used in a Monorepo 👇🏽
🔥 Monorepos in JavaScript/TS
Monorepos are a way to manage multiple projects under a single repository, enabling code sharing across all the projects.
Here's the breakdown of tools and mechanics:
1️⃣ Workspaces
Workspaces (e.g. yarn workspaces) allow you to group multiple ) within a monorepo. Typically, you'll organize them into:
👉 Apps: Standalone applications that use shared packages.
👉 Packages: Shared code that apps and even other package can depend on.
2️⃣ Orchestration
Running commands across apps and packages can be challenging. Tools like Turborepo simplify this by orchestrating tasks, ensuring everything runs from a top-level.
3️⃣ (Optional) Polyrepo
Want the flexibility of multiple repositories but the benefits of a monorepo? You can set up a "polyrepo in disguise", allowing you to distribute your projects across GitHub/GitLab/Bitbucket/... while maintaining a unified local structure.
You can either use .gitignore or git submodules for it.
4️⃣ Decoupling with Versioning
Versioning in monorepos decouples apps from packages in their rigid local structure. It also allows one to release updates for packages without impacting all apps.
5️⃣ Automating Versioning
With tools like Changesets, you can manage versioning either locally or through your CI/CD pipelines. The latter improves automation.
6️⃣ Fallback Dependencies
Monorepos prioritize dependencies from local workspaces. If a dependency isn't found locally, it falls back to the registry (e.g. npm). This setup enables apps to depend on packages both inside and outside the monorepo.
Have questions or tips to share? Drop them below 👇 I did this whole setup for a freelance project of mine over the last 3 years.
0
1
9
3,076
Robin Wieruch retweeted
Started @rwieruch's Road to Next course.
Already obsessing over the details... can't help myself.
68ms staggered animations + ghost tooltips = buttons that feel alive ✨
This is going to be a fun journey 🚀
#RoadToNext #NextJS
Already obsessing over the details... can't help myself.
68ms staggered animations + ghost tooltips = buttons that feel alive ✨
This is going to be a fun journey 🚀
#RoadToNext #NextJS
0
1
7
1,302
Robin Wieruch retweeted
@rwieruch He is an excellent mentor, it feels like pair-programming. While he explains concepts clearly, preparing you for real-world challenges. It's a rare opportunity some only experience after joining big-tech.
0
1
2
1,414
Robin Wieruch retweeted
I finished @rwieruch's NextJS Basic and Pro courses. They provide so much value, with detailed, practical content that teaches in weeks what takes years to learn independently. What I love is that at the end you have the code and skills to go build a scalable SaaS product.
1
1
4
1,457
Robin Wieruch retweeted
I can’t tell you his excited I am. Look what got I just got in the mail. Going to study this front to back.
@rwieruch
@rwieruch
1
1
10
1,621
Robin Wieruch retweeted
I need to start the "The Road to Next" course by @rwieruch.
He was kind enough to give me access to it, and it's the only reason why I'm giving Next another chance.
If I'm not shipping after this course, I'll never do it.
He was kind enough to give me access to it, and it's the only reason why I'm giving Next another chance.
If I'm not shipping after this course, I'll never do it.
1
1
15
4,742
🤔 Curious how different AI models handle the same prompt?
With React.js and the AI SDK, you can stream responses from multiple models in parallel and compare their outputs side by side, in real time.
With React.js and the AI SDK, you can stream responses from multiple models in parallel and compare their outputs side by side, in real time.
1
0
14
1,768
Working with multiple AI models in JavaScript? 🤖
One of the best things about AI SDK is how easily it lets you switch between models like GPT-4 Turbo and Claude 3 without juggling different SDKs.
💡 Why it matters:
You can compare responses from different models with the same to add new models as they're released.
Great for finding the best model for specific use cases (speed, cost, domain etc.).
Instead of locking yourself into one provider, you stay flexible and future-proof. One clean interface, multiple powerful LLMs 🔥
One of the best things about AI SDK is how easily it lets you switch between models like GPT-4 Turbo and Claude 3 without juggling different SDKs.
💡 Why it matters:
You can compare responses from different models with the same to add new models as they're released.
Great for finding the best model for specific use cases (speed, cost, domain etc.).
Instead of locking yourself into one provider, you stay flexible and future-proof. One clean interface, multiple powerful LLMs 🔥
0
3
26
1,986
👀 Ever built a chat app with streaming AI responses in React… from scratch?
You probably ended up writing:
- State hooks for messages, loading, input
- A streaming fetch with manual decoding
- Logic for assembling incoming chunks into complete messages
❌ It's doable, but essy fast.
✅ Now enter an AI SDK like ai-sdk/react:
- Handles the stream
- Manages the state
Gives you a clean, simple hook: useChat().
🚀 Result? Less boilerplate, more time spent on what actually matters: building a great user experience.
Once you see the difference, it's hard to go back ✨
You probably ended up writing:
- State hooks for messages, loading, input
- A streaming fetch with manual decoding
- Logic for assembling incoming chunks into complete messages
❌ It's doable, but essy fast.
✅ Now enter an AI SDK like ai-sdk/react:
- Handles the stream
- Manages the state
Gives you a clean, simple hook: useChat().
🚀 Result? Less boilerplate, more time spent on what actually matters: building a great user experience.
Once you see the difference, it's hard to go back ✨
0
2
24
2,111
Hard facts about The Road to Next 👇
- 14,230 lines of real-world code we’ll write together
- Up to 6 operating terminals during development
- 30+ hours of self-paced video lessons
- ~5 minutes per video on average
- 100+ quizzes to reinforce your learning
- 60+ coding challenges to provide real-world practice
- 14,230 lines of real-world code we’ll write together
- Up to 6 operating terminals during development
- 30+ hours of self-paced video lessons
- ~5 minutes per video on average
- 100+ quizzes to reinforce your learning
- 60+ coding challenges to provide real-world practice
The Road to Next is LIVE 🚀
5 months ago, I launched the early access. With feedback from hundreds of students, it's grown into a self-paced full-stack bootcamp.
Honestly, I should've just called it The Road to Full-Stack 😅
Whether you're into Next.js or just want to level up this is for you.
🎁 Giveaway
3 random people who like & share this post in the next 24 hours will get free access to the course!
Check it out in the replies 👇
3
2
18
2,568
🚀 I love how easy it is to tailor the outcome of The Road to Next course.
You won't just learn full-stack development, you'll build your own starter kit application, ready to launch your next big idea!
You won't just learn full-stack development, you'll build your own starter kit application, ready to launch your next big idea!
0
0
7
1,124
💬 I asked my students what they think of Shadcn UI’s copy-paste approach to components. Here’s what they said:
🔹 “I love the flexibility. No more black-box components.”
🔹 “Feels lighter. You only install what you use.”
🔹 “So much easier to customize compared to MUI or ersonal projects, but updates might get tricky in teams.”
Most loved the control and simplicity, especially coming from more rigid UI libraries. The biggest concern? Long-term maintainability and manual updates.
Shadcn is making them rethink what a component library should be. 🔥
Curious how it’s working for others 👇
🔹 “I love the flexibility. No more black-box components.”
🔹 “Feels lighter. You only install what you use.”
🔹 “So much easier to customize compared to MUI or ersonal projects, but updates might get tricky in teams.”
Most loved the control and simplicity, especially coming from more rigid UI libraries. The biggest concern? Long-term maintainability and manual updates.
Shadcn is making them rethink what a component library should be. 🔥
Curious how it’s working for others 👇
1
2
29
2,767