Videos / Web Dev

Episode 3 of 16 · Web development, end to end

JavaScript architecture: how a codebase stays understandable

Chapters

1. The switch on the wall0:00
2. What a file exports0:16
3. One reason to change0:32
4. Deep, not wide0:47
5. Three things that leak1:05
6. The smallest surface that works1:22
7. Water runs downhill1:37
8. Folders navigate, imports bind1:53
9. Stable underneath2:09
10. What a cycle costs2:29
11. The half-evaluated module2:46
12. Two ways out of one3:04
13. The board and its photographs3:20
14. Stored or derived3:36
15. Never store what you derive3:53
16. Who may write4:10
17. The shape of a change4:28
18. The module-level variable4:46
19. The bicycle5:05
20. What inheritance costs5:21
21. Start with a function5:37
22. A closure for memory5:55
23. Plain objects at the seams6:14
24. A class still earns it6:33
25. Passport control6:50
26. Name your edges7:07
27. Parse, do not validate7:27
28. Types stop at the compiler7:46
29. Where errors become messages8:03
30. Trust the inside8:21
31. The second caller8:38
32. The setup block is a bill8:56
33. Count the mocks9:14
34. Pure core, thin shell9:31
35. Test through the surface9:47
36. The loop closes10:05
37. The whole thing10:24

JavaScript architecture: how a codebase stays understandable. Here is the one image for this chapter. A light switch on a wall. You see two positions, up and down. You do not see the wiring, the breaker, or the gauge of the cable. A module is

Mark as watchedSaved in this browser only.