VP Engineering @ Specialist in Software Development, Entrepreneur in Technology and Startups | Fractional CTO Expert | AI Developer with Proven Impact
I frequently emphasize the need to study Domain-Driven Design deeply. If you have a business challenge, it's essential to invest in obtaining a suitable and customized solution. The domain is the heart of every business and often brings out the details of each context. We always use generic themes in presentations for the same reason. A good source for reading are the books by Vaughn Vernon and Eric Evans. 🏃🏆🏆🏆🏆 #software #ddd #domain #domaindrivendesign
Software Ecologist, Architect, Modeler | Optimizer of Teams and Individuals | Domain-Driven Design and Systems Transformation
There are at least four rather significant problems with "more open source examples" of implementations using #dddesign: 1. Proprietary models can't be disclosed because they are in fact serious IP; that is, they are core differentiating value after all. 2. Examples of other businesses' domain aren't your domain, but they are copied and used as generic without working with domain experts. (What's the point?) 3. OSS models require a lot of work, and most times I and others using DDD don't have time. 4. Time is money. I have to pay my bills the same as everybody else, and *nobody* pays me for spending the time to create more free models so others can make money.
Tech Lead | Software Engineer | Solutions Architecture | MBA | MIT Specialization
1moThis is the way of the truly amazing and innovative software solutions.