Mini Episode | Growing Engineers with Goldilocks Challenges

Being an Engineer · 3 Feb 2023 · 8m · Episode 5

What this episode covers

Aaron Moncur, founder of Pipeline Design & Engineering, explains the concept of "Goldilocks challenges" as a method for growing engineering teams. He uses analogies from Brazilian jiu-jitsu and teaching CAD to illustrate how tasks must be neither too easy nor too hard to foster growth. Moncur advises leaders to balance pushing engineers with psychological safety, ensuring they feel comfortable admitting when they are struggling.

Other shows on the same ground, closest first.

  • How Soft Skills Drive High-Impact Engineering Teams w/ Aaron Moncur

    Aaron Moncur, founder of Pipeline Design & Engineering, discusses how soft skills like communication and psychological safety drive high-performing engineering teams. He shares specific management strategies, such as 'managing by invitation' and removing bureaucratic barriers to accelerate engineering speed, including the strategic use of 3D printing. Moncur also highlights the evolving landscape of engineering education, promoting his platform The Wave and the PDX expo as alternatives to traditional degree requirements.

  • The Pragmatic Embedded Podcast · 43m

    2024 christmas special

    Hosts Jeff Gable and Luca Eden reflect on three years of The Pragmatic Embedded Podcast, highlighting guests like Miro Slavic, John Odo, and Luca Mustafa who pushed specific technical and process boundaries. They discuss the disconnect between senior engineers seeking agile change and managers resistant to the hard work required for true transformation. The conversation emphasizes that successful embedded development requires breaking the 'Iron Triangle' of fixed scope, time, and budget by prioritizing core functionality and asking difficult questions about deadlines.

  • The Manufacturing Executive · 38m

    Creating Manufacturing Environments Where Engineers Can Thrive w/ Josh Tarbutton

    Josh Tarbutton, Chairman and Chief Innovator of Bravo Team, discusses creating engineering cultures that foster innovation by balancing autonomy with trust. He explains how his background in the Army and academia shaped his leadership philosophy, emphasizing the need to support engineers with clear objectives and resources rather than micromanagement. Tarbutton highlights the critical disconnect between sales and engineering, advocating for early engineer involvement in scoping to prevent unrealistic expectations and burnout. He also warns against the long-term costs of under-investing in capital infrastructure and talent, arguing that fear-driven leadership stifles the creativity necessary for manufacturing competitiveness.

  • TRADEOFFS · 59m

    Building Teams That Scale And What Happens When They Don't | Peloton, Meta, Blaze Talent | Will Blaze

    Will Blaze, founder of Blaze Talent, discusses his experience scaling engineering teams at Peloton and Meta, and his current work with companies like CoreWeave, Andium, and Sandbar. He explains the trade-offs between hiring full-time employees versus contractors, emphasizing that contractors reduce risk for startups during volatile growth phases. Blaze also details the importance of structured interviews, the use of AI tools like Gem and BrightHire to augment recruiting efficiency, and the challenges of maintaining quality of hire in high-growth environments.

  • Embedded.fm · 1h 15m

    386: Not Managing Robots

    Ingo Muschenetz, VP of Architecture at Axway, discusses his transition from startups to enterprise management, emphasizing the importance of psychological safety, mentorship, and maintaining a 'shield' for engineering teams. He shares insights on managing remote teams during the pandemic, the challenges of monetizing open-source developer tools, and the value of listening to podcasts for context-switching and inspiration. Muschenetz also reflects on his career path, starting at Harvey Mudd College and founding Zamlon (which became Aptana), and offers advice on finding mentors and avoiding burnout.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by Being an Engineer. The episode itself belongs to its publisher.