Podcasts about ubiquitous language

Выбор имени не просто сложно, а ... очень сложно. И сегодня мы поделимся супер-пупер принципом выбора имен: NURGLESS.Спасибо всем кто нас слушает. Ждем Ваши комментарии.Бесплатный открытый курс "Rust для DotNet разработчиков": https://www.youtube.com/playlist?list=PLbxr_aGL4q3S2iE00WFPNTzKAARURZW1ZShownotes: 00:00:00 Вступление00:03:00 Почему нейминг - самое главное?00:10:00 NURGLESS Принцип00:12:25 Ubiquitous Language 00:34:50 Referenced names00:39:40 Google it00:45:00 Local terminology00:51:40 Environment terminology saturation 01:00:00 Surrounding context01:02:30 Something stupidСсылки:- https://x.com/codinghorror/status/506010907021828096?lang=en : Великая мудрость- https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/identifier-names : C# identifier naming rules and conventionsВидео: https://youtube.com/live/Laa__y7ccIQ Слушайте все выпуски: https://dotnetmore.mave.digitalYouTube: https://www.youtube.com/playlist?list=PLbxr_aGL4q3R6kfpa7Q8biS11T56cNMf5Обсуждайте:- Telegram: https://t.me/dotnetmore_chatСледите за новостями:– Twitter: https://twitter.com/dotnetmore– Telegram channel: https://t.me/dotnetmoreCopyright: https://creativecommons.org/licenses/by-sa/4.0/

"But if we have three different understandings or three different models of how this operates – that's the situation we want to avoid. We don't want to get to the problem and realize we don't have a common way of understanding or talking about the problem." Paul & Karen discuss the challenges of creating shared understanding – and the dangers of failing to do so.

Janis, Dominik und Jochen unterhalten sich über Microservices. Letztes hatten wir ja schon so ein bisschen darüber gesprochen und daraufhin hat sich Janis gemeldet und gefragt, ob wir da nicht mal eine komplette Sendung mit ihm drüber machen wollen. Wollten wir natürlich :).   Und hier noch die Antwort auf alle Fragen im Bereich Softwareentwicklung Shownotes Unsere E-Mail für Fragen, Anregungen & Kommentare: hallo@python-podcast.de News aus der Szene Okta breach PYPL PopularitY of Programming Language Meta donates $300,000 to the Python Software Foundation | Łukasz Langa - #Programming GitHub Issues Migration: status update Cython is 20! Neue Programmiersprachen: vlang | zig April: PyCon DE & PyData Berlin 2022 Juli: EuroPython September: DjangoCon EU 2022 Werbung Ailio sucht Mitarbeiter | Anfragen bitte an diese Mailadresse: business@ailio.de Microservices BoundedContext / Single source of truth Buch: Building Microservices, 2nd Edition Sam Newman on Information Hiding, Ubiquitous Language, UI Decomposition and Building Microservices Sam Newman: Monolith to Microservices (InfoQ Podcast) Folge 99 - Sam Newman - Monolith to Microservices ELK-Stack Apache Kafka Buch: Software Architecture with Python MonolithFirst Benchmark Caddy / Nginx / Uvicorn Benchmarking nginx vs caddy vs uvicorn for serving static files Uvicorn / uvloop Picks bpytop / glances Kafka Connect

Having a ubiquitous language within your organization means that when someone on the developer team refers to “the foo bar,” the people on the design team, the service team and all the other teams, know exactly what they mean. Although a general understanding of the term is the most important aspect of ubiquitous language, we'd recommend not using terms like “the foo bar,” and rather applying principles of domain driven design to your naming system so that your glossary actually makes sense in the real world! Join us today as we share our experiences of dealing with ubiquitous and non-ubiquitous language in our working environments, and the importance of bringing up this topic as early on in any job as possible. 

In this episode of the InfoQ podcast Charles Humble talks to Sam Newman, an independent consultant focusing on microservices, cloud and CD, about the 2nd edition of Newman's book Building Microservices, published by O'Reilly. They discuss information hiding; ideas from Domain Driven Design including aggregates, bounded contexts and ubiquitous language; UI decomposition; and team structure drawing on ideas from Team Topologies. Read a transcript of this interview: https://bit.ly/3lXqBxx Subscribe to our newsletters: - The InfoQ weekly newsletter: bit.ly/24x3IVq - The Software Architects' Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/ Upcoming Virtual Events - https://events.infoq.com/ InfoQ Live: https://live.infoq.com/ - October 19, 2021 QCon Plus online conference: https://plus.qconferences.com/ - November 1-12, 2021 Follow InfoQ: - Twitter: https://twitter.com/infoq - LinkedIn: https://www.linkedin.com/company/infoq/ - Facebook: https://www.facebook.com/InfoQdotcom/ - Instagram: @infoqdotcom - Youtube: https://www.youtube.com/infoq

This is the second part of my talk with my colleague Bert Laverman. We continued our talk with Domain-Driven Design. We discussed how Bert found out about the concept, and we delved deeper into some aspects of the DDD-centric systems, such as Ubiquitous Language and Bounded Context.  Bert also highlighted the benefits of using agile development methodology when designing a system that requires lots of detailed planning and decision making and getting it all done in a timely manner.  We discussed why software architecture is so important, and lastly but very importantly we talked about Axon Server Standard Edition and Enterprise Edition. He also explained the benefits of using Docker and Kubernetes when setting up and using Axon Server.  You can reach Bert on Twitter @BertLaverman and on LinkedIn. Connect with me on Twitter @SaraTorrey and on LinkedIn. For more information about us visit axoniq.io

In qualsiasi progetto l'avere un linguaggio comune dovrebbe essere di primaria importanza. Nel Domain Driven Design questa cosa è chiamata Ubiquitous Language, e nella puntata di oggi ve ne parlo[Martin Fowler - UbiquitousLanguage](https://martinfowler.com/bliki/UbiquitousLanguage.html )[Martin Fowler - DomainDrivenDesign](https://martinfowler.com/bliki/DomainDrivenDesign.html )[Developing the ubiquitous language](https://thedomaindrivendesign.io/developing-the-ubiquitous-language/ )[D.D.D in TypeScript: Model, Ubiquitous Language e Value Object](https://www.intre.it/2020/04/07/domain-driven-desing-applicazione-typescript )[L’importanza di essere Ubiquitous](https://medium.com/@albx87/limportanza-di-essere-ubiquitous-890f09468cd7 )[CodeGen 2021 - 13 febbraio](https://codegen2021.azurewebsites.net )[Blazor Conf 2021 - 18 marzo](https://www.eventbrite.it/e/blazor-conf-2021-tickets-132619732189 )

To close off this season and conclude our deep dive into system and application architecture, today’s episode is a special panel discussion on a topic that has provoked a mix of answers that range from the controversial to the philosophical — “What does domain-driven design mean to you?” For the final word on this subject, we welcome back software developers Chris Keathley, Japa Swadia, Mark Windholtz, and Miki Rezentes. Our first hot take comes from Miki, who shares her thoughts about how domain-driven design developed because the tech industry undervalues communication. Following this, Mark and Japa discuss how domain-driven design gives developers a context for what they create while informing how you code using Elixir. We then touch on whether domain-driven design makes it easier or more difficult to change your code and how communication is valued within a business context. We explore key domain-driven design concepts, including the role of bounded contexts, and how this design ethos can help you appeal to stakeholders such as product managers. After Miki highlights the reasons why communication should be seen as a vital tech skill, each guest provides their final thoughts on domain-driven design. Tune in for this season’s insightful finale and find out which of today’s guests is the winner of “Whose Design Is It Anyway?” Key Points From This Episode: Introducing guests Chris Keathley, Japa Swadia, Mark Windholtz, and Miki Rezentes. Hear what domain-driven design means for each guest. Miki shares her hot take that domain-driven design is “nothing new under the sun.” Why the essence of domain-driven design is about listening. How domain-driven design can inform your Elixir architecture. Mapping your system and developing names for your bounded contexts. Domain-driven design trade-offs and how it can lead to a loss of productivity. The idea that domain-driven design has developed because the tech industry undervalues communication. Why communication should be valued — bad communication costs money. How tech companies are generally aligned with the goals of domain-driven design. Why Mark is so delighted to be working with Elixir and domain-driven design. The link between domain-driven design and developing better products. Exploring how bounded contexts allow teams to create solutions to unique problems. Seeing communication as a tech skill that should be learned early in your career. Our guests share their final thoughts on domain-driven design. Links Mentioned in Today’s Episode: SmartLogic — https://smartlogic.io/ Chris Keathley on Twitter — @ChrisKeathley/ Chris Keathley — https://keathley.io/ Japa Swadia on Twitter — https://twitter.com/japa2292 Japa Swadia on LinkedIn — https://www.linkedin.com/in/japaswadia/ Mark Windholtz on Twitter — https://twitter.com/windholtz Mark Windholtz on LinkedIn — https://www.linkedin.com/in/mwindholtz/ Miki Rezentes on Twitter — https://twitter.com/mikirez Miki Rezentes on LinkedIn — https://www.linkedin.com/in/miki-rezentes-823ba02a/ Podium — https://www.podium.com/ Elixir Outlaws — https://elixiroutlaws.com/ Agile DNA — http://www.agiledna.com Frame.io — https://frame.io/ Bleacher Report — https://bleacherreport.com/ Domain-Driven Design: Tackling Complexity in the Heart of Software on Amazon— https://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215 Domain Language — https://www.domainlanguage.com/ The Seven Laws of Learning: Why Great Leaders Are Also Great Teachers on Amazon — https://www.amazon.com/Seven-Laws-Learning-Leaders-Teachers/dp/1599559277 Patterns, Principles, and Practices of Domain-Driven Design on Amazon — https://www.amazon.com/Patterns-Principles-Practices-Domain-Driven-Design/dp/1118714709 ‘Ubiquitous Language’ — https://martinfowler.com/bliki/UbiquitousLanguage.html ‘Value Object’ — https://martinfowler.com/bliki/ValueObject.html Domain-Driven Design Europe — https://dddeurope.com/2021/ Domain-Driven Design Europe on YouTube — https://www.youtube.com/channel/UC3PGn-hQdbtRiqxZK9XBGqQ A Philosophy of Software Design on Amazon — https://www.amazon.com/Philosophy-Software-Design-John-Ousterhout/dp/1732102201 Eric Evans Training Videos — https://elearn.domainlanguage.com/ Designing Elixir Systems with OTP — https://www.amazon.com/Designing-Elixir-Systems-OTP-Self-healing/dp/1680506617/ Whose Line Is It Anyway? — https://www.imdb.com/title/tt0163507/ Drew Carey — https://www.imdb.com/name/nm0004804/ Special Guests: Chris Keathley, Japa Swadia, and Miki Rezentes.

Thanks to Krisztina we will have Matteo Collina as a special guest on our next panel. Matteo is a long time Nodejs contributor and TSC member. Open-source software is a success story, and undoubtedly one, we can learn from. In OSS the clocks tick differently, but it is software built for users, to solve problems - both relatively unknowns factors at the beginning. So what can DDD developers for businesses learn from that experience: how to handle these uncertainties, how is the Ubiquitous Language developed in the Open source world? How do you do design in OSS? And many more questions!

W tym odcinku razem z Łukaszem Szydło rozmawiamy o różnych odmianach języka wszechobecnego, jaki może pojawić się w rozmowach pomiędzy uczestnikami projektu.

In dieser Folge des innoQ Podcasts spricht Lucas Dohmen mit Michael Plöd über Domain-Driven Design. Was ist Domain-Driven Design? Wie passt es zusammen mit anderen Ansätzen wie Agile, DevOps oder Microservices? Was ist die Ubiquitous Language und welche Rolle spielt sie in DDD? Was ist das Strategic Design und was bedeuten die Begriffe Bounded Context und Context Map? Und was ist das Technical Design und welche Begriffe begegnen einem dort?

00:16 – Welcome to “Chinchilla Chat: Where It’s All Chinchillas…All The Time…” …we mean, “Greater Than Code!” 03:10 – Matt’s Origin Story in Software Development 09:04 – The Business of Consulting 16:24 – Empathy in Consulting 20:07 – Rigorous Communication and Shared Language; Microservices Ludwig Wittgenstein (https://en.wikipedia.org/wiki/Ludwig_Wittgenstein) Sapir-Whorf Hypothesis (Sapir-Whorf Hypothesis) Metaphors We Live By (https://www.amazon.com/gp/product/0226468011/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&tag=therubyrep-20&camp=1789&creative=9325&linkCode=as2&creativeASIN=0226468011&linkId=eb1e64309e20b18e5700df50e48890ae) 39:05 – Ubiquitous Language (https://www.amazon.com/gp/product/0226468011/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&tag=therubyrep-20&camp=1789&creative=9325&linkCode=as2&creativeASIN=0226468011&linkId=eb1e64309e20b18e5700df50e48890ae) Surfaces and Essences: Analogy as the Fuel and Fire of Thinking by Douglas Hofstadter (https://www.amazon.com/gp/product/0465018475/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&tag=therubyrep-20&camp=1789&creative=9325&linkCode=as2&creativeASIN=0465018475&linkId=acbb83bfae39114efe5369b300142f68) Coraline Ada Ehmke: Metaphors Are Similes. Similes Are Like Metaphors. (https://www.youtube.com/watch?v=czvgHSYKkNU) Wittgenstein’s Ladder (https://en.wikipedia.org/wiki/Wittgenstein%27s_ladder) Performance of Genetic Algorithms For Data Classification by Matthew Stine (http://thesis.honors.olemiss.edu/230/1/mstine-senior-thesis.pdf) Reflections: Matt: Ludwig Wittgenstein and language games. Coraline: The shortcomings of pattern-matching. Astrid: Using evolution as a model. Rein: The Beginning of Infinity: Explanations That Transform the World Janelle: Language as a mechanism of control. Sam: Building a bridge of understanding with progressively less incorrect metaphors. This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode). To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks! Special Guest: Matt Stine.

Author: Konstantin Kudryashov Read By: Alfred Nutile Original Source: http://stakeholderwhisperer.com/posts/2014/10/introducing-modelling-by-example "For the last year I have been experimenting with the new approach to a Behaviour-Driven Development, which could be summarised as "Ubiquitous Language is a thing again". The core premise of this approach is that if you take Ubiquitous Language seriously and push for it in your scenarios, you open the door to doing a Domain-Driven Design while you're doing Behaviour-Driven Development's red-green-refactor cycle. By embedding Ubiquitous Language in your scenarios, your scenarios naturally become your domain model, which you can use to develop the most important part of your application - a core domain."

Kerry and Rinat start the discussion with a Context Map that has several Bounded Contexts. They use their conversation to refine the Context Map and carve out the initial key words of the Core Domain’s Ubiquitous Language. Download (mp3): Episode 21 – Linguistic Cartographers – (65 minutes) Subscribe via RSS | Subscribe for free in […]