Paul Barbu Gheorge on Geographically Distributed Tems

The Pragmatic Embedded Podcast · 7 Aug 2024 · 49m

What this episode covers

Paul Barbu Gheorge, Head of Software at Wenglor, discusses the challenges of managing geographically distributed teams across Germany, Romania, Serbia, and Russia while developing machine vision cameras. He explains how the company structures its software and hardware development to handle multiple product lines, highlighting the latency and communication barriers inherent in this setup. Gheorge details specific strategies for improving alignment, such as establishing a clear hardware abstraction layer and shifting API design responsibility to the software consumer to better reflect use cases. The conversation also covers the importance of detailed interface specifications, such as sequence diagrams, to prevent integration issues during implementation.

Other shows on the same ground, closest first.

  • Being an Engineer · 48m

    S1E41 How To Communicate Between Development Groups | Lisa Somogyi

    Lisa Somogyi, Director of Business Development at Cooper Perkins, discusses her career trajectory from designing building mechanical systems to working on robotic automation at companies like ME Engineers and Picaro. She details specific projects, including high-precision sample positioning at Oak Ridge National Labs using Staubli robots and the development of mobility aids by Real Mobility. Somogyi emphasizes the importance of cross-functional communication, explaining how implementing Agile methodologies and tools like Arena and SolidWorks helped align hardware and software teams at Picaro, while highlighting the challenges of managing vendor lead times and overseas manufacturing tolerances.

  • Embedded.fm · 56m

    347: Be Careful About the Bits

    Elecia White and Christopher White discuss API design strategies for embedded systems, emphasizing the use of abstraction layers and the POSIX model (open, close, read, write) to manage hardware interactions. They address a listener's question about organizing firmware modules, suggesting block diagrams to define hardware, control flow, and layered interfaces. The hosts also tackle a career dilemma involving a startup engineer who feels demoted after being acquired by Big Tech and assigned to work with a senior 'gray-beard' engineer, advising on how to navigate team dynamics and imposter syndrome.

  • Being an Engineer · 46m

    S1E22 Being a GENUINE engineer/leader | Rob Newsom

    Rob Newsom, VP of Product Development at Cubex, discusses his journey from early software development on PDP and Apple II systems to leading cross-functional hardware and software teams. He explains how Scrum methodology can be adapted for hardware development by accounting for long lead times, such as mold creation, and emphasizes the importance of having experienced team members to predict these constraints. Newsom also shares strategies for managing remote teams, highlighting the success of using local liaisons to bridge cultural and time-zone gaps, and outlines his leadership philosophy centered on authenticity, self-awareness, and genuine interest in team members' lives.

  • Being an Engineer · 59m

    Michael Kubba | Working for Apple, Tesla, and Google

    Michael Kubba, COO at Fellow, discusses his career leading hardware teams at Apple, Tesla, and Google. He details the intense design and manufacturing challenges of the Apple TV remote, the vertical integration and mission-driven culture at Tesla, and the product definition struggles of Google Glass at Google X. Kubba emphasizes the importance of rapid prototyping, clear product development phases, and becoming a temporary expert in cross-functional areas to succeed in hardware engineering.

  • TRADEOFFS · 48m

    T-24-004 : Tom George - Hardware Startup Engineer to Google Product Lead

    Tom George, now a Product Team Lead at Google leading the Pebble initiative, recounts his journey from early hardware startups like Maritime Broadband and QuadLogic to his current role in Sustainable Cities. He details the engineering trade-offs of building satellite communication systems for cargo ships, including the failure of using commercial stepper motors in marine environments, and the organizational challenges of separating R&D from sustaining engineering at QuadLogic. George explains his decision to halt production at Sidewalk Labs when the Pebble sensor was not ready for scale, and his subsequent pivot at Google away from hardware manufacturing toward policy and urban planning solutions.

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