2 ms·
IMO, there is no software solution, because it's not a software problem, it's a social problem. As far as specific things to try go, domain-driven design is my
by mumblemumble 6y ago
IMO, there is no software solution, because it's not a software problem, it's a social problem.
As far as specific things to try go, domain-driven design is my personal favorite off-the-shelf mental framework for dealing with these sorts of things. Especially the concept of bounded contexts. Embrace Conway's Law; recognize it's not a criticism, per se, it's also a scaling strategy.
- the_af 6y agoFair enough. I agree partially: it's a social problem. Thing is, software engineering deals with social problems too: those related to development. I've never seen DDD successfully used in any company I've worked in, but that's probably a shortcoming of my own experience. (Likewise, I've never seen TDD or Agile or lots of things people often mention in their blogs successfully used. Again, this is probably my own problem!). addendum: to be fair I've never seen a completely working ESB either. Always a plan to build or deploy one, never the finished thing ;)
- deleted 6y ago[deleted]
- mumblemumble 6y agoI doubt it's your own problem. The thing about methodologies like DDD and Agile is that they're not just a development practice. They're also (in my opinion much more importantly) frameworks for how the entire company interacts with the dev team. I see them fail more often than not, too, and one thing that's consistent about every failed implementation I've witnessed first-hand is that non-developers who are involved in or influence product development weren't engaged with, bought into, or properly trained in the framework.