Скачать или смотреть Stop doing this as a Next.js developer!

00:00 Make a plan; become an architect.
01:22 Recursion, lazy loading, client vs server... etc.
03:04 Understanding the underlying data
05:09 Option 1: Client and Server component
10:12 Option 2: Client-parent state container component
15:30 The problem with option 1

In this video we make a commitment to better plan our architecture before we dive into coding. Specifically, as Next.js developers, where do we want to fetch our data? On the server? On the client? What are the trade-offs?

Once we have considered our different options, consult other people in the team and execute that design plan. This has two benefits: it saves us time as we sacrifice initial speed for future clarity and we simplify the underlying code by choosing the architecture that has the best balance of pros and cons.