462: Spontaneously High Performing

Embedded.fm · 19 Oct 2023 · 1h 15m · Episode 462

What this episode covers

Marian Petre, Emeritus Professor at the Open University and co-author of 'Software Design Decoded', discusses her research on how software developers become experts. She explains that high-performing teams and experts treat errors as opportunities for insight rather than failures, and emphasizes the importance of 'pair debugging' and sketching to externalize thought. Petre also addresses the gap between academic research and industry practice, highlighting the value of 'invisible work' and the need for engineering leaders to advocate for a learning culture over rigid KPIs.

Mentioned

Companies
Mozilla, HP Labs
Also
Software Design Decoded: 66 Ways Experts Think, Strange Loop, Joy of Coding, Never Work in Theory, UML, Scratch, Python, BASIC, AWK, Greg Wilson, Andre van der Hoek, Mary Shaw, Irum Rauf, Martha Hause, John, Wokwi, Godbolt, VSCode

Other shows on the same ground, closest first.

  • Being an Engineer · 49m

    S7E1 A Joyful Approach to Product Development | Lisa Ho & Andrew Muyanja (Menlo Innovations)

    Lisa Ho and Andrew Muyanja of Menlo Innovations explain their 'Menlo way' of software development, emphasizing high-tech anthropology, paired work, and story cards to ensure products meet user needs and stay on budget. They discuss how pairing reduces risk and builds quality, while story cards allow for granular planning and rapid feedback loops. The guests highlight that their culture of joy, transparency, and 'kindergarten skills' fosters collaboration and minimizes fear, leading to robust, user-centric outcomes.

  • Oxide and Friends · 1h 06m

    What's a bug? What's a debugger?

    Bryan Cantrill and Adam Leventhal of Oxide Computer Company discuss the philosophy and mechanics of debugging, arguing that the term 'debugger' is regrettable and that tools should focus on observability and understanding system behavior rather than just fixing reproducible errors. They critique traditional in-situ breakpoint debugging for its fragility ('killing the patient') and advocate for post-mortem analysis, memory forensics, and tools like DTrace and Hubris. The conversation highlights how modern practices like CI/CD and languages like Rust have shifted the debugging landscape, making traditional debuggers less relevant for simple errors but more critical for complex, distributed system pathologies.

  • Being an Engineer · 1h 06m

    S5E22 James Trevelyan | What Research Tells Us Is The Most Important Quality of Engineers

    Professor James Trevelyan, an engineer and author specializing in robotics and automation, explains that effective collaboration, not just technical skill, is the most critical quality for engineers. He argues that academic environments often discourage collaboration, leading to poor project outcomes, and highlights how cultural factors in countries like Pakistan create barriers to effective teamwork. Trevelyan emphasizes that listening skills and simple, low-cost experimentation are key to accelerating development and creating value, citing his work on low-cost air conditioners as a practical example.

  • Being an Engineer · 1h 02m

    S2E46 How To Build A Workplace People Love | Rich Sheridan

    Rich Sheridan, CEO and Chief Storyteller at Menlo Innovations, explains how he founded the custom software company to end human suffering in technology by returning joy to the workplace. He details Menlo's specific operational practices, including mandatory pairing, open office layouts without walls or desks, and the role of 'high-tech anthropologists' who observe users to ensure the team solves the actual problem rather than a perceived one. Sheridan contrasts this joy-based culture with fear-based management, arguing that transparency and collaboration eliminate the emergencies and rework that plague traditional engineering environments.

  • Let's Combinate · 14m

    249 - The Best Audit Advice Nobody Told Me

    Subhi Saadeh, a quality professional and certified lead auditor specializing in drug-device combination products, shares five key lessons learned from transitioning from the auditee to the auditor side. He emphasizes that audits should evaluate the health and adequacy of a system rather than targeting individuals, and that auditors must look for systemic patterns rather than isolated errors. Saadeh also stresses the importance of setting realistic scopes, recognizing auditing as a distinct skill set separate from technical expertise, and lowering anxiety to gather better evidence.

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.