May be I should be more precise, and say 'No one developer owns the Domain Model...'. We all share the 'code ownership' and no one coder is responsible for the state of the domain model. Now you're probably thinking I'm going to elaborate on the fact the team I'm currently working with don't take code ownership seriously - they don't - but I'm not going to mention that. I'm talking about when you're a tech lead\coach you don't have 'first dibs' on the structure of the model and how it's implemented. To be honest in a DDD environment we don't have control over the structure of the domain model, the business do!
So this week I realised I was living up to my pseudonym, I've been being awkward about other coders adding to the domain model, I've been worrying about what they're going to add or change. Now this is just my hang-up and I realised, how are they going to improve at modelling & design if they aren't allowed to fail. Just because other developers & management recognise you're the best coder they've got doesn't give you the right to stamp the domain model as yours.
To put it another, way by acting as the only person who can change the domain model you're creating a single point of failure and you're lowering the standards required by your team. Now this is an anti-pattern in the making and has no place on in an emerging Agile environment.
Post a Comment