이 에피소드에 관해
In this episode, we talked with J.B. Rainsberger about how we can improve interactions and communication within an engineering organization, how to diagnose issues, and which models can help make sense of them. We also discussed why it shouldn't be your responsibility to fix a large-scale organization, but how you can still make sustainable improvements.
영어
미국
전사 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
이 팟캐스트의 다른 에피소드
In this episode, we discussed how architecture can work in a fast-moving, agile world with Ted Neward, who provides insights into how he defines architecture and the role of an architect. We talked about our experiences in different organizations and the importance of patterns and abstractions in c…
In this episode, we take a deeper look at the term code review, exploring it beyond its typical context—the pull request. Joining us is Dr. Michaela Greiler, a software engineer, researcher, and consultant.
Dr. Greiler is renowned for her work in the field, including her significant study conducte…
In our first episode, we discussed the Inverse Conway Maneuver with Nick Tune, who is well known for his contributions in the domain-driven design community. We talked about our experiences on applying this approach in real-world projects. Along this we touched upon a couple of related socio-techni…
In this episode, we had an insightful conversation with Adam Tornhill, co-founder of CodeScene, a leading code analysis and visualization tool. We explored the role of AI in software engineering, focusing on its potential to refactor code, but also how AI can in general help us to tackle the persis…
면책 조항: 이 페이지에 포함된 팟캐스트와 작품은 David Leitner and Thomas Pokorny에서 가져온 것입니다. 이 팟캐스트는 소유자의 재산이며 Listen Notes, Inc.와 제휴하거나 보증하지 않습니다.
