Cat Swetel gave a brilliant Technologist's Introduction to Epistemic Injustice explaining "epistemic injustice"—what we know, how we know, and who gets to decide and influence our reality. There are two kinds of epistemic injustice: Testimonial injustice; When someone is ignored, or not believed, because of their sex, sexuality, gender presentation, race, or, broadly, because of their identity. Hermeneutical injustice; injustice related to how people interpret their lives. Join us in this session where Cat will do a short introduction on the topic, and after, we will talk about how this impact domain crunching. For instance, if we don't include software developers in requirements engineering, what is the impact? What if the software teams only allowed to build user stories and aren't part of the narrative for their building? And what about the exchange of narratives across the ecosystem, i.e. across domains. Do we have the hermeneutic resources to describe emergent behaviour across the system?

[Fireside chat] How Epistemic injustice impacts Domain Crunching with Cat Swetel

Do Software architects have a bad name? Why? What are your expectations, what anti-patterns you experience? What are you thankful for from your architects? Should you have a software architect in the team, or between the teams? Changing the world starts with thinking and sharing the reasons. This podcast is the recording of our open discussion with the community.

[Open Discussion] Do we need software architects?

"Just Enough Software Architecture" author and Google Software Engineer George Fairbanks joins us for a round and educates us on technical debt and how it's a natural part of the software development process. He also gives practical advice on dealing with technical debt and the philosophies that have changed along with the evolution of software architecture.

Defining technical debt with George Fairbanks

In this episode, the founder of the Institute of Digital Transformation Charles Araujo aims to address some misconceptions most companies have when it comes to digital transformation and argues why 2020 wasn't the transformational year we all thought it was. He also talks about the importance of "intellectual curiosity" and  why we should stop adhering to the "tech company fallacy."

Misconceptions on digital transformation with Charles Araujo

&nbsp;    The term “sociotechnical” seems to have gotten a bit or renaissance lately, which is a great thing given all the positive impact it has had on many organisations and their workers around the world over the years. It also seems to have gotten some traction outside the academic circles this time after being developed and pushed from there mostly using action research since its humble beginning in the post-war British coal mines. It is an entry into systems thinking for many, with its idea about joint optimisation of both the technical and social aspects of an organisation. A common example is setting up the team topology to match the service architecture in an attempt to cater for negative effects of Conway’s law. This is all well and good, but if we think about it, viewing the modern organisation as a sociotechnical system is a bit of a tautology; all organisations have social and technical elements that people deal with on a daily basis. As with systems thinking, the value of sociotechnical system design is more about perspective and understanding rather than any specific outcome. There is so much more to sociotechnical design than DevOps and team setup that we need in order to cope in our increasingly complex and hazardous “digital coal mines.”

Open Sociotechnical Systems Thinking with Trond Hjorteland

In the last week of this year, we are closing another full year of virtual Domain-driven design meetups with the last meetup. So grab your drinks (tea, lemonade or anything you want!) and come join with your DDD questions to this lean coffee! We all post topics we want to discuss and together we will get into dialogues, so bring us your knowledge and DDD questions and see you then! Miro https://miro.com/app/board/uXjVOY0dIIk=/

Domain-Drinking Dialogues 2nd edition - 2021 Lean coffee

Our models should be driven by the domain, but not constrained by what domain experts tell us. After all, the domain language is messy, organic, ambiguous, social, incomplete, and if it has any intentional design to it at all, it's not designed to be turned into software. Modelling is more than capturing requirements, it's the opportunity to create novel concepts. This talk will use real-world stories to invite you to discuss.

Design & Reality with Mathias Verraes

There is a quote made famous by Ruth Malan from Grady Booch: "Architecture represents the significant design decisions that shape a system." And shaping a system takes time, and seeing the impact of these significant design decisions can take years after the changes have been done. And most of us are usually not there to reak the benefit, or worse, feel its pain. So in collaboration with D-EDGE we will have a panel of people that did experience and will discuss how architecture decisions shaped the system years after the change. &nbsp; &nbsp;

[Panel] Long term impact of architectural design decision

oday most software products are highly networked and distributed solutions used by 1000s if not -10000s of people spread across the globe. To produce an experience that is intuitive and delivers a quality service worldwide, multi-culturally, and 24/7 across all time zones, you need a multi-disciplinary and diverse set of individuals i.e. a tailored team. Join us in this panel with: Dawn Ahukanna Jessica Kerr Ruth Malan Rebecca Wirfs-Brock Mathias Verraes Trond Hjorteland

Effective team collaboration and why we need it for modern product experiences?

Does your team suffer from:  Inconsistent views of your systems? Producing incohesive solutions? Ineffective architecture practices and tools?  Introducing Bytesize Architecture Sessions! Bytesize Sessions are a workshop format that enables collaborative and iterative knowledge sharing. This talk will enable you to run Bytesize Sessions resulting in the following benefits:  Improved systems thinking. Enriching collaboration within the team. Understanding architecture practices and tools in a safe environment. A feedback loop controlled by the team produces better documentation across sessions. Revealing the Bermuda Triangles!  About Andrea Magnorsky Andrea is a professional software developer with over 20 years of experience. These days she is a consultant / contractor focusing on strongly typed functional languages and software architecture . Andrea founded Kats Conf, Global GameCraft and many other communities. She also co-founded BatCat Games, a PC and Console game development company in Ireland. &nbsp;

Sharing your (Systems) knowledge with Bytesize Architecture Sessions with Andrea

Coding Over Cocktails is created by TORO Cloud, a company that offers a low-code, API centric platform for application development & integration.

This podcast series will tackle issues faced by enterprises as they manage the process of digital transformation, application integration, low-code application development, data management, and business process automation.

Watch out for exciting and engaging content from guests who will touch on topics such as APIs as the center and foundation of applications, integrations, and business processes.

New tracks tagged #Software Architecture