A common topic at conferences and on social media last year has been “How do we structure (architectural) decision-making?” Let’s begin 2023 exploring this question together! On January 2, 2022, at 6:00 PM GMT, join the online virtual Decision Making Open Space. In this four-hour unconference, you can be both a participant and a speaker in this open-space format. Everyone joining can suggest session topics; the attendees set the agenda they want to explore. This means this conference will go wherever the attendees want it to go. You’ll be sent a link to the event space prior to the event if you RSVP yes and get accepted on Meetup. We will be using Spatial chat and miro to facilitate this! The event will be free of charge, but space is limited. We do accept donations to help us pay for Spatial chat. You can donate any number you want or pay for 1 Spatial chat day pass on our open collective page (see the link below). We are happy with any donations! The more donations we get, the higher the attendee limit. Any money left over will be donated to a cause promoting software design to nontraditional communities! See you in 2023! If you have any questions, you can contact us at email@example.com. Link to miro: https://miro.com/app/board/uXjVPEdHYFg=
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!
Residuality theory is a revolutionary new theory of software design that aims to make it easier to design software systems for complex business environments. Residuality theory models software systems as interconnected residues - an alternative to component and process modeling that uses applied complexity science to make managing uncertainty a fundamental part of the design process.
16 years ago, my teammates and I built software for big internet properties. Now, we build information systems - data platforms, decoupled frontends, event streams, lots of interdependent software and services with many types of consumers. In the world of “digital transformation”, software is becoming systems. Unfortunately, we don't think in systems. Systems are nonlinear. They reorganize our mental models and communication structures. Yes, we need skills in cloud-native architectures, Kafka, Kubernetes, GoLang, Terraforming, etc. But those are not the key to our success. We also need to transform how we think together. Otherwise, we will build the same old things with fancy new tools. Let's explore essential nonlinear skills and practices for IT professionals, skills we might not think of as “IT”. What are the practices that help us navigate from software to systems?
Today 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, Nivia Henry, Jessica Kerr, Ruth Malan, Rebecca Wirfs-Brock, Mathias Verraes, Trond Hjorteland
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. About D-EDGE Have you ever booked a hotel online? Then you've probably used D-EDGE without knowing it. Every day, we help more than 17,000 hotels worldwide to develop their online visibility and sales through a range of SaaS and digital marketing solutions. Amongst the 480 D-EDGERS, the R&D team is made up of a hundred or so enthusiasts who are reinventing hotel booking for both the traveller and the hotelier. As a subsidiary of the Accor group, D-EDGE simplifies the life of independent hotels and hotel chains alike. https://www.meetup.com/D-EDGE-tech/ https://miro.com/app/board/uXjVOA5fBQU=/?invite_link_id=308762229734
Writing a book about a modeling method (in our case: Domain Storytelling) necessarily makes you reflect on your own modeling practices. We had to frame things that we intuitively did in workshops. And we had to put our own approach into relation to other modeling methods. In this Meetup, we would like to talk about two concepts that came from these thoughts and discuss with you if they are applicable to collaborative modeling in general: Scope: Before a workshop, we try to figure out which kind of model is needed to make the workshop successful. This led to the concept of “scope”: Which point in time should we model? At which level of granularity should we model? Should we model the pure business process or how the software-supported process works? Scenario-based modeling: Several modeling methods that are popular with DDD practitioners are based on scenarios – meaning that one model shows only one case. Scenarios help a lot to learn and to deal with complexity. But they also raise the questions of which scenarios are relevant and how to keep an overview over many scenarios.
'It is not the domain experts knowledge that goes in production, it is the assumption of the developers that goes into production' This famous quote from Alberto Brandolini is unfortunately true but it also points to the right direction: we need to bring the domain knowledge into our software. This time one of our organisers Krisztina will show you how this can be done in the day to day business, she will share her experience including the list of techniques needed to succeed in having real Domain-driven development. This won't be a slide show, challenges, questions are welcome!
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.
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!