Learning Should Feel Less Like a Panic Response
Jason Lengstorf, creator of "Learn with Jason" and CodeTV, has spent more than 20 years in the industry. His message to developers is straightforward: the constant scramble to master every new tool out of fear of falling behind is counterproductive.
It feels like we're scrambling to learn whatever thing we're worried is gonna cost us our job if we don't learn it really fast. A huge motivation for me is to try to remind everybody that this stuff can be fun. And having fun isn't not working.
That anxiety is familiar across the developer community, showing up in Slack channels and conference conversations. Lengstorf argues that curiosity, not desperation, leads to better outcomes. When developers enjoy the learning process, they are more likely to retain information, finish projects, and share their knowledge with others.
What AI Actually Amplifies
Lengstorf frames AI tools as a force multiplier for existing skills, not a substitute for them. He compares the situation to home repair: "A can of caulk and a plunger can get you part of the way there, but at some point, you need to hire a plumber."
During a live build on CodeTV, Lengstorf and Jack Harrington used an MCP (Model Context Protocol) server to generate code automatically. The output looked flawless until a bug surfaced—a single missing component name in a config file. Harrington, who understood the underlying system, fixed it instantly. Lengstorf, despite his decades of experience, would have needed to reverse-engineer the AI-generated codebase to find the same issue.
If you're a skilled developer, this is gonna make you unbelievably fast. If you are not a skilled developer, it's gonna give you a lot of tools to learn very quickly. If you have no interest in learning, it is going to get you into a big bad mess really, really fast.
The implications are clear: MCP emerging as a shared standard also suggests the ecosystem is converging on common protocols, unlike the pattern of incompatible, proprietary frameworks that crop up and disappear quickly.
The Fragile Backbone of Modern Development
A significant overhead of modern development depends on a worryingly small number of people. Lengstorf points out the disconnect between how much we rely on these projects and how little awareness exists about their maintainers:
- SQLite, which powers most local databases globally, is maintained by four people.
- The global timezone database is managed by two people.
- Colin McDonald maintains Zod, the TypeScript schema validation library underpinning countless AI and framework integrations.
Lengstorf sponsors Zod on GitHub because he calls it "load bearing" for his work. He encourages developers to inspect their own package.json files to find the dependencies maintained by individuals they have never heard of. Supporting these maintainers financially is not just a nicety; it's a matter of industry stability.
Predicting the Next Web Shift
The JavaScript ecosystem is in a holding pattern. Lengstorf sees a "weird spot" where the conversation is less about new ideas and more about debating past ones. Meanwhile, CSS sees advances with new browser capabilities arriving regularly.
I have a hunch that we are in a bit of a temporary lull that's gonna lead to something really interesting.
The next significant change may relate to user interface fundamentals. If AI tools make conversational interaction more practical, the need for complex information architecture—like navigation buttons and nested dropdowns—may diminish. That does not mean everything will be a chat interface, but it may require new component-based architectures that can integrate with autonomous agents operating sites.
For indie developers, the convergence of on-device AI models, standard protocols like MCP, and existing web technology creates a unique opportunity—similar to how edge functions democratized enterprise-level capabilities for individual developers.
Preparing for the Future by Enjoying the Present
The developers who thrive are unlikely to be those who treat technology as a checklist of things to fear. Those who learn for the enjoyment of it and who engage with the open source community will have the curiosity and resilience to adapt to the next wave.



