Nick is a strategic technical leader at Navico and the co-author of two books: "Designing Autonomous Team and Services" (O’Reilly) and "Patterns, Principles, and Practices of Domain-Driven Design" (Wrox).
Co-presented with Gien Verschatse
Coffee or tea? One sugar or two? Should we use Event Sourcing or does CRUD seem good to you?
Our brains are designed for making quick decisions, but quick does not always mean good… We make thousands of decisions each day but never stop to wonder: how did we come to this conclusion? Were there more choices than we realised? Did we focus on the right thing? Did we pick the right option? Are there other methods we can use to reach a better outcome?
If we improved our decision making by just 1%, overall we would achieve a massive improvement in every area of our lives, from happiness with our family to success at work. Everybody should learn decision making heuristics, yet nobody does. Let's fix that.
We're going to take a close look at a variety of key decision-making heuristics including "problem restatement", "devil's advocate", and "the wizard". Through provocative exercises, we're going to uncover the heuristics we currently use and we're going to teach ourselves when to apply certain decision making heuristics to improve our chances of getting the results we want.
A loosely coupled software architecture and an organizational structure to match is one of the biggest predictors of continuous delivery performance. To optimize end-to-end value creation and delivery, technical leaders must adopt a sociotechnical mindset.
When teams are designed without consideration of the software architecture, dependencies will arise in code that inhibit teams from delivering high value at speed. Organizational dysfunctions will multiply as productivity and motivation drop dramatically across the entire company. But by adopting a sociotechnical mindset, teams and software systems can be aligned to minimize dependencies and maximize product innovation speed.
The sociotechnical mindset is the synthesis of multiple perspectives, including social dynamics, domain-driven design, business models, and software architecture. Nick Tunee teaches you how to apply these principles and patterns through real examples based on years of practical experience across a wide range of organizations, including the UK government, Salesforce, and more.
Technical Debt Detective
Inventor of EventStorming
UX person in love with DDD
Author of Idea Flow
Data Horticulturist. Code Tinkerer.
Development Manager and Architect
Domain Driven Developer
Ask Me About Dojos
Developer, Crafty Person, and Eater of Legacy Spaghetti
Author of “Domain-Driven Design”
Event-driven Model Enthusiast
Engage and Embrace
Student of Systems
Engineering Excellence Evangelist
Junior Master Strategist
Author and Obsessive Programmer
Functional Domain Modeler
Distributed engineer, AFOL