-->
Subscribe to access the entire course.
🌶️ tip: unsubscribe at any time.
Ah, that's a great question!
Frontend at Scale is a bi-weekly newsletter (as in, once every two weeks) that is all about software design and architecture for frontend engineers.
Subscribing to the newsletter is the best way to support my work and encourage me to keep making free resources like this one.
I probably don't need to say this, but I would never ever spam you—and you can unsubscribe with a single click at any time.
Already subscribed? Don't worry, you won't get double-subscribed. Nobody deserves to read my terrible jokes twice.
Module 4: Implementing
[00:03] Hey friends, Welcome to the implementation module of the course where we’re finally going to get our hands dirty and write some code. Now, we’re not going to implement the entire thing because full stack is a pretty big application, and that will take a really long time. So we’re going to see just enough code so you can see how all of the concepts that we talked about over the last few videos, how they translate into code,
[00:26] We’re going to start by grabbing the modules that we defined in the previous section and we’re going to implement them in the code base, and then we’re going to start breaking down those modules into components. We’re also going to see a very simple component hierarchy so we can keep those components organized in the code base as well.
[00:44] And we’re going to see how we can implement the entities of our system in models or types or just different code constructs in the code base. To wrap things up, we’re going to talk about how we can implement some constraints and guardrails so that we can protect the architecture as the codebase grows over time and as more people will contribute to it.
[01:04] I’m very excited about this module. This is probably my favorite module in the course, so I hope you’re excited as well and I’ll see you in the next video.