O TYM PODKAŚCIE 🔗
We’ve consistently observed a common pattern: regardless of the architectural approach—from traditional enterprise to more hands-on, emergent methods—teams face similar obstacles when building effective systems. The core challenge remains how to build software that truly works and enables a smooth flow of delivery. To address this, we’ve started a new series, Stories on Facilitating Software Design and Architecture. In these sessions, we focus on real-world experiences from our community, sharing practical stories about the alternative approaches that have delivered results. It’s about moving beyond the theoretical and into the practical, shared wisdom of what actually works.
Częstotliwość aktualizacji:
biweekly
Średnia długość dźwięku:
26 minutes
Wywiady gościnne
Język angielski
Stany Zjednoczone
31 odcinków
od 2 września 2025
episodic
NAJNOWSZY ODCINEK 🔗
Every team has that retrospective complaint that never gets solved. Someone can’t take a proper holiday because there’s nobody to hand their work to. Someone else would gladly help but has no idea where to start. It gets a sticky note, maybe an action item, and then the next sprint arrives and noth…
WYSZUKAJ MINIONE ODCINKI
Wyszukaj minione odcinki Stories on Facilitating Software Architecture & Design.
POPRZEDNIE ODCINKI 🔗
We say we want teams to own their decisions. But what happens the moment you actually hand people the pen, and they discover how uncomfortable that is?
Two weeks into a new role, Yves Hanoulle, who calls himself a “creative collaboration agent” rather than an agile coach, was working with a group o…
We tend to assume that if the people who will live with an architecture standard help create it, adoption takes care of itself. Invite the teams, let them design the process, give everyone a voice, and the standards will be theirs.
Wouter Lagerweij tells the story of an organisation where that assu…
Most organisations have a community of practice that nobody actually wants to attend. It sits in the calendar every two weeks, a handful of people talk, and the rest stay silent. Suzanne Lagerweij has a simple explanation for why: people don't feel like they matter there. Why would anyone go the ex…
We spend a lot of design effort on how data gets into a system — the forms, the validation, the transactional database quietly recording everything in neat rows. We spend far less on how it comes back out. And when the person who needs a weekly report is a loss prevention officer rather than a soft…
Most facilitation advice starts the moment people walk into the room. Prepare your flip charts. Sort the chairs into some reasonable configuration. But Katie Clark brought two stories that are deliberately not about what happens during a workshop — they're about everything that happens before it, a…
We tend to trust diagrams. Four boxes, four arrows, four services — that feels like shared understanding. But when Vanessa Formicola started asking basic questions about a team's architecture, the boxes came apart in her hands.
What the team called four services turned out to be four deployments of…
Most decisions in software teams don't fail because people disagreed. They fail because people thought they agreed — and nobody found out for weeks. You leave the meeting feeling good about where things landed, and three weeks later you're having the same conversation, wondering how you got back to…
There is a version of career progression that looks like success from the outside and feels like erosion from the inside: you get more senior, you sit in more meetings, you write less software, and eventually someone asks whether you'd like to become an architect. Most people in that position have …
There's a pattern that turns up in almost every struggling team: the problem gets named as technical, the technical fix gets applied, and nothing improves. The complaints come back louder, and the only thing that really changes is who gets blamed next.
We recorded this one differently. At DDD Europ…
Zastrzeżenie: Podcast i grafika osadzone na tej stronie pochodzą z Virtual Domain-Driven Design, który jest własnością jego właściciela i nie jest powiązany ani wspierany przez Listen Notes, Inc.
WYSZUKIWARKA PODCASTÓW
Możesz skorzystać z naszej strony internetowej, aby wyszukiwać podcasty3,835,862i odcinki197,495,513według osób, miejsc lub tematów.
If I have seen further than others, it is by listening to podcasts and standing upon the shoulders of
giants.
‐ Isaac "Llamacorn" Newton
WYSZUKAJ MINIONE ODCINKI
Wyszukaj minione odcinki Stories on Facilitating Software Architecture & Design.
ZGŁOŚ PRAWA DO TEGO PODCASTU
Why to claim podcasts?
If you are a podcaster, the best way to manage your podcasts on Listen Notes is by claiming your Listen Notes
podcast pages.
It is a great, free way to engage the podcast community and increase the visibility of your podcasts.
After claiming your Listen Notes podcast pages, you will be able to:
✓
Manually refresh the RSS feed to sync up
✓
Get a verified badge (
✓
) alongside with your podcast name on Listen Notes
✓
Post ogłoszenia drobne for sponsorship,
guests, co-hosts,
cross-promotion...
✓
Respond to listener comments on Listen Notes
✓
Use speech-to-text techniques to transcribe your show and
edit transcripts
✓
Improve the presence of your podcasts, e.g., self-service
wywiad z podcasterem...
✓
If you share your Listen Notes page and at-mention @ListenNotes
on X (formerly Twitter),
nasze oficjalne konto na X (dawniej Twitter) will retweet to promote
your show to our followers.
Coming soon:
◯ Self-service promotion on Listen Notes
◯ Track your podcast stats on Listen
Notes, e.g., listens, page
views...
◯ Manage episodes
EDYTUJ
Dziękujemy za pomoc w aktualizowaniu podcastowej bazy danych.
