• DDD Weekly: Issue #34 - Secure by Design [slides] Manning. As a developer, you need to build software in a secure way. But you can’t spend all your time focusing on security. The answer is to use good design principles, tools, and mindsets that make security an implicit result - it’s secure by design. The secret of better UI composition [blog] Mauro Servienti. What we immediately realized is that there seems to be no canonical guide to designing UIs that retrieve and aggregate data from different sources. [DDD Weekly]
• Emergent Boundaries - Video of my DDD eXchange 2017 talk in London Video of my ExploreDDD 2017 talk in Denver Abstract Modelling is more than knowledge management. It’s complexity management. To reduce cognitive load, you split things up, whether at small scale, in code, or in the large, such as Bounded Contexts. But if you choose large boundaries upfront, you risk getting it wrong, and being stuck to them for a long time. Join Mathias in a discussion of better ways of empirically discovering boundaries instead. [Mathias Verraes]

Permalink | From 24 April 2017 to 30 April 2017 | Last updated on: Mon, 7 Jun 2021 09:11:25 GMT

• Call for code review - When I started this blog, I had one idea in mind: create some sort of repository of programming principles and practices so that I myself and other people would have an easier time navigating around them. That’s a nice goal to aim for but I noticed that when it comes to the actual process of writing code, having such a repository is often not enough. [Enterprise Craftsmanship]

Permalink | From 17 April 2017 to 23 April 2017 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT

• Awkward Aggregate Root relationships and how to rethink them - I have an Order that can be split into multiple Shipments. A Customer orders Quantity X of Product Y, represented as a single OrderLine with Quantity = X. In order to optimize shipping costs, Quantity X of Product Y is split into Z number of Shipments…. [Nick Chamberlain on Nick Chamberlain]
• DDD Weekly: Issue #33 - The Tale of State and Behaviour, Part 1 with Scott Wlaschin [podcast] Three Devs and a Maybe. Part 1 and Part 2. “In this weeks episode we are lucky to be joined by Scott Wlaschin again, to discuss his recent ‘Thirteen ways of looking at a turtle’ talk.’” DDD eXchange 2017, April 27th - April 28th [conference] SkillsMatter. Strategic Domain Driven Design: Project Management Simplified [blog] Robert Reppel. “Just like realising the benefits from choosing a CQRS/ES based architecture requires a business domain- rather than technical mindset in order to properly establish transactional boundaries and to manage coupling and cohesion, DDD needs certain practices to be firmly established and continuously applied in order to be of value. [DDD Weekly]
• Temporal coupling and Immutability - This topic is partly covered in my Applying Functional Principles in C# Pluralsight course, Module 2. Here, I’d like to elaborate on how temporal coupling and immutability are related to each other. Temporal coupling Temporal coupling is coupling that occurs when there are two or more members of a class that need to be invoked in a particular order. A common example is the following: var calculator = new PriceCalculator(); calculator. [Enterprise Craftsmanship]

Permalink | From 10 April 2017 to 16 April 2017 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT