Keeping Up with the Codeashians. Dealing with our fast paced industry.

Episode Summary

Executive Summary: The episode tackles developer anxiety about falling behind in a rapidly changing web industry and argues for a pragmatic approach: stay strong on fundamentals, learn just-in-time, and avoid chasing every new tool immediately. Wes and Scott stress that it’s normal to feel overwhelmed, that cutting-edge tech is often unstable, and that staying current can be integrated into work, side projects, and community learning rather than weekend grinding.

Main Topics: Coping with industry change and overwhelm: The hosts frame the core issue as a common fear among developers: the web changes so fast that it can feel impossible to keep up while balancing family, work, and life outside coding. Fundamentals over chasing every new tool: They argue that strong core JavaScript/web fundamentals make it easier to adapt to new frameworks and language features when needed. Avoiding the cutting edge too early: The episode recommends waiting for new libraries/frameworks to mature before adopting them in production, because early versions often have breaking changes and unclear best practices. Just-in-time learning strategy: Wes promotes learning technologies when a real project need arises, rather than trying to learn everything in advance. Finding time to learn on the job: They discuss practical ways to stay current during work hours through internal tools, side tasks, gradual adoption, and small experiments that benefit the team. Career and business reasons to stay current: Staying updated matters for job security, client expectations, promotions, and competitiveness, especially as newer teams and companies adopt modern tooling. Information sources and community learning: The hosts recommend podcasts, Twitter, newsletters, lunch-and-learns, and meetups as low-friction ways to track trends without feeling overwhelmed.

Key Arguments: Feeling behind is normal in this industry; almost everyone experiences it because the pace of change is so high. You do not need to know every framework or library; it is better to know your core language deeply and learn specific tools when they become relevant. The cutting edge is not always the best place to be in production because early tools often stabilize only after a period of dogfooding and iteration. Just-in-time learning allows developers to conserve energy and focus on life/work balance while still staying relevant. Learning on the job is realistic if developers can carve out even 30-60 minutes a day for small experiments or internal improvements. Modern skills matter for employability, client expectations, and staying competitive against newer developers and companies. Companies that invest in developer learning attract stronger talent and often move faster because their teams are better equipped to adopt useful new technology. Developers should use multiple lightweight channels—newsletters, podcasts, social media, meetups—to keep a pulse on the ecosystem without trying to consume everything.

Data Points: Professional experience mentioned by listener email: Close to 10 years professionally - Used as part of the listener’s concern about falling behind in web development. Time since Wes shifted career focus: A couple of years / about a year and a half ago - Referenced when discussing his move from agency/freelance work to courses and podcasts. React course re-recordings: 3rd time since late 2015 - Wes says he fully re-recorded React for Beginners again to stay current. Suggested time for staying current: 5% to 10% of the week - Scott suggests dedicating a small portion of work time to keeping up. Learning time example: Half an hour to an hour a day - Wes describes spending a small amount of time at work learning Angular through a side tool. Birthday mention: 30 - Scott jokes that he turned 22, then corrects himself to 30. Course sale window: 2 days and 11 hours left - Wes mentions the remaining time on the course sale at recording time. Podcast format: 8-part audio documentary - Scott recommends the podcast Containers.

Pivotal Quotes: "you are not like, this is not, you're not alone. This is not a unique problem." — Scott: Reassuring the listener that feeling overwhelmed by fast tech change is common in the industry. "it’s fine with not knowing how to do absolutely everything." — Wes: Core takeaway on accepting knowledge gaps and avoiding pressure to master every new tool. "the cutting edge is not necessarily a place that you want to be." — Wes: Explaining why early adoption can be risky and why waiting for maturity is often smarter.

Implications: Listeners should prioritize fundamentals, adopt new tools selectively, and use work-time learning strategies instead of burnout-driven weekend study. For the industry, the message favors sustainable growth, mature adoption, and healthier expectations for developers at every career stage.