Architecture is Designing Knowledge Flow -- Explore DDD
In the tech industry, we are most interested in knowledge stock: What do you know? What information can you apply easily? Whiteboard tests, for example, assess a candidate's stock of knowledge.
In the tech industry, we are most interested in knowledge stock: What do you know? What information can you apply easily? Whiteboard tests, for example, assess a candidate's stock of knowledge.
Architecture, in the systems age, is not (just) Kubernetes. It is is designing relationships between parts (people and tech parts) then adapting those relationship patterns as circumstances change.
In my lifetime, we have experienced the equivalent of 20,000 years of change. Nonlinear change. In many respects, we are the architects of change, yet we seem to do the same things again and again, expecting different results.
Systems thinking practices that will help you make impactful changes -- despite the emerging complexity of modern systems.
In the tech industry, we are most interested in knowledge stock: What do you know? This focus is holding many individuals, teams and organizations back. As relational complexity increases, individual knowledge stock is insufficient. What we need is knowledge flow.
In this workshop, you鈥檒l understand how interrelated and interdependent parts (in people and software) act together to create patterns Through hands-on exercises and a real-world scenario, you'll You鈥檒l learn to create conceptual models to guide impactful decisions.