Hasty Treat - Making Yourself Uncomfortable To Grow

Episode Summary

Executive Summary: The episode argues that developers grow by intentionally getting uncomfortable: learning new standards, tools, and workflows instead of clinging to familiar ones. Through examples like CSS preprocessors, Flexbox/Grid, jQuery, front-end frameworks, public speaking, and hands-on projects, Wes and Scott frame discomfort as the trigger for better efficiency, broader skills, and long-term career resilience.

Main Topics: Discomfort as a growth strategy: The core thesis is that avoiding discomfort keeps developers stuck in old patterns, while leaning into it builds competence and adaptability. Learning new standards and tools: They contrast legacy practices like floats and jQuery with newer standards such as Flexbox, Grid, and modern JavaScript, arguing that standard tools should be adopted when they become mainstream. Efficiency vs. comfort: The hosts discuss how comfort creates short-term speed, but often hides inefficiencies and outdated approaches that reduce long-term effectiveness. When to adopt new technologies: They explore how to judge whether a tool or framework is worth learning, using examples like CSS preprocessors and front-end frameworks reaching critical mass. Practical ways to learn unfamiliar things: They recommend a mix of research and direct building: reading docs, watching videos, then quickly moving to hands-on experimentation. Applying discomfort beyond coding: The discussion broadens to public speaking, breakdancing, cooking, photography, savings, and cold showers as examples of deliberate discomfort leading to growth.

Key Arguments: Staying in familiar workflows can make developers feel efficient, but that comfort often masks worse code, slower learning, and lost opportunities. When a new approach becomes a standard (e.g., Flexbox/Grid instead of floats), it should be learned because standards are durable and not just passing trends. Adopting tools at critical mass matters; if every interview or peer discussion expects knowledge of something, ignoring it becomes a career risk. Developers should not confuse feeling smart with actually improving; true growth comes from confronting what they do not know. Learning is most effective when a person combines upfront research with real implementation, because understanding deepens only after trying and failing in practice. Making yourself uncomfortable on purpose can improve not just coding skills but broader life skills like confidence, creativity, and resilience.

Data Points: Recording date: May 21 - The hosts note the episode was recorded in May, even though they joke about June weather in the intro. Snowfall: 3 or 4 inches - Wes describes unexpected wet snow that fell overnight, damaging trees and bushes. Meeting size: 12 people - Scott mentions being afraid to do public speaking at a meetup of about a dozen people. Progression count: 7 times - They jokingly suggest that after mentioning a topic repeatedly on the podcast, listeners should finally learn it (example given: Intersection Observer). Timeline: 6 months - Wes uses learning a new keyboard layout as an example of a temporary slowdown that could yield long-term efficiency. Peer consumption: 15 YouTube videos - Wes says he watched around 15 videos while learning sourdough and bacon before finally doing it himself.

Pivotal Quotes: "You want to feel dumb. You want to feel like you're growing." — Scott: The closing takeaway: growth requires embracing the discomfort of not knowing. "Feeling smart is not necessarily the same thing as being smart." — Scott: He warns against confusing confidence and familiarity with actual skill development. "The real learning will come when you actually put it into play." — Wes: Wes explains that watching videos and researching are useful, but hands-on practice is what creates real understanding.

Implications: Listeners are encouraged to audit their habits, drop ego-driven resistance to new standards, and deliberately seek discomfort. For developers, this means better skills, more modern code, and stronger long-term employability.