A critical scene in his JavaScript course involves him writing a large function, staring at the screen, and muttering, "This is ugly. This is not DRY (Don’t Repeat Yourself)." He then deletes 30 lines of code and replaces them with 10 lines of higher-order functions. For a beginner, this is terrifying. For an intermediate, it is enlightenment. You are watching a master reject his own work in real-time. This teaches the most elusive skill in software engineering: .
To the aspiring developer reading this: Do not watch the videos at 2x speed. Do not skip the coding challenges. Do not download the finished source code. Sit. Pause the video. Type the code. Break the code. Fix the code. If you invest 200 hours into his courses, you will save 2,000 hours of future debugging confusion. You will stop asking, "How do I do X in Framework Y?" and start asking, "What is the underlying principle governing this interaction?" watch jonas schmedtmann videos
The Blueprint of Mastery: Why Watching Jonas Schmedtmann’s Videos is a Non-Negotiable Rite of Passage for Developers A critical scene in his JavaScript course involves
This modeling of a calm, methodical, error-tolerant professional persona is perhaps the most valuable takeaway. Most developers quit not because they can't understand "this," but because they panic when the console turns red. Schmedtmann retrains your amygdala to see the red text as a clue, not a catastrophe. For an intermediate, it is enlightenment
Notice the production quality: the clear audio, the zooming into the code, the highlighting of the specific line, the typed notes in the corner. Notice his demeanor. When he makes a mistake (and he does, deliberately or accidentally), he doesn't cut the tape. He says, "Look, I made a typo. How do we debug this?" He normalizes error messages as a tool , not a threat.
Schmedtmann, conversely, is a master of . His hallmark is the "staggered reveal." He does not present a perfect, final product. He presents a bug. He asks, "Why is this happening?" He fixes the bug. He refactors the mess. He shows you the evolution of thought, not just the fossilized result. Watching him code is akin to watching an architect lay a foundation, test the soil, realize the wood is warped, adjust the blueprints, and then build the house. You are not learning a framework; you are learning problem-solving resilience .