24: I'm a Total Fraud

Embedded.fm · 23 Oct 2013 · 53m

What this episode covers

Elecia White and producer Christopher White discuss a listener's question about how to measure competence as an embedded software engineer, referencing the RBM Consulting embedded C test and Brain Bench exams. They argue that rote knowledge tests are less valuable than evaluating a candidate's project history, ability to ship code, and generalist skills. The conversation shifts to the prevalence of imposter syndrome in engineering, with White sharing her personal strategy of maintaining a '10-slide deck' of achievements to counter feelings of fraudulence. They conclude that the best way to improve is through hands-on projects and teaching, rather than passive reading.

Mentioned

Companies
RBM Consulting
Products
Arduino
Also
Brain Bench, Stanford

Other shows on the same ground, closest first.

  • Making It · 1h 05m

    Episode 320: I’m an idiot, help me…

    Jimmy Diresta, Bob Clagett, and David Picciuto discuss their experiences with imposter syndrome, sharing personal anecdotes about feeling inadequate when tackling new skills like building a travel trailer, operating a backhoe, or working with complex machinery like a Bridgeport mill. They explore how the fear of being perceived as a fraud affects their confidence in both professional settings and personal projects, such as car restoration and woodworking. The hosts conclude that owning one's lack of knowledge and adopting a 'forever learner' mindset helps mitigate these feelings and encourages others to ask for help without shame.

  • The Amp Hour · 1h 42m

    Work on it for 10 years...

    Eliseo White and Chris White of Embedded.fm join Chris Gammell of Contextual Electronics to discuss skill improvement, the importance of deliberate practice, and the challenges of learning electronics and programming. They debate the best ways to teach engineering fundamentals, the limitations of prototyping platforms like MicroPython and Arduino, and the transition from hobbyist projects to manufacturable products. The conversation also covers their personal interests, including 3D printing, VR, and solar energy, while highlighting the gap between building a prototype and shipping a reliable product.

  • The Amp Hour · 1h 44m

    Pedantic or Andrantic

    Chris Gammell, a developer advocate at Hologram and founder of Contextual Electronics, joins Elecia and Chris White of Embedded.fm to discuss hardware prototyping, learning strategies, and industry tools. The conversation covers the challenges of cellular IoT connectivity, the utility of the HackRF software-defined radio, and debugging techniques using the J-Trace Pro. They also explore pedagogical concepts like the Dreyfus model for learning programming and hardware, emphasizing the importance of iteration and mental health in engineering careers.

  • The Pragmatic Embedded Podcast · 39m

    Christmas Special

    Hosts Jeff Gable and Luca share war stories from their careers in embedded systems, highlighting the pain of manual testing in helicopter avionics, the chaos of managing requirements with Word and Excel in Dropbox for medical devices, and the technical debt of massive #ifdef blocks in legacy machine tool software. They discuss the industry's slow adoption of modern software practices like version control and CI/CD, contrasting embedded development with web development standards. The episode concludes with book recommendations including 'The Phoenix Project' and 'Team Topologies', and reflections on the future of IoT security and agile adoption in hardware.

  • The Pragmatic Embedded Podcast · 38m

    The Matthew Test with Matthew Eshleman - Part 1

    Matthew Eshleman, a principal embedded software engineer and consultant formerly at Toshiba, joins Jeff Gable and Luca to discuss his 'Matthew Test,' a 15-step checklist for evaluating embedded software teams. Modeled after Joel Spolsky's Joel Test, the episode covers foundational practices such as using source control (specifically Git), automating build and release processes, and implementing continuous integration. Eshleman argues that unlike web development, embedded engineering requires 'reasonably complete specifications' and early risk management due to the high cost and long lifecycle of hardware changes.

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