For more than 25 years I have searched for ways to build better software more frequently and with less stress. In that time I discovered the raw designer in me that was working all along. I have built software systems ranging from data systems to websites, API integrations to ecommerce and much more. Some of these have lasted a decade or more and were very healthy systems, workhorses. I even have a patent on an automation system.The domain, the business model, was often my biggest inspiration in my software design process. When that was the case, it was fantastic. When it was not, it did not go well.In the middle of that career I ran into Domain Driven Design (DDD) by Eric Evans. I was puzzled and intrigued. I have, for more than a decade now read that book several times, attended a few conferences and even helped friends in in the business present good ways to model software. I now understand the material well enough to go through the book again and this time, write commentary and enrich my training material even more.Doing software is easy and hard. I propose we do the hard work of a good design to make life a little easier by creating adaptive systems. I promote this in my interactions, discussions and the trainings I have done.If you have a software need that is not quite getting met, reading the domain and articulating it well is likely a first step to getting on track. It takes some effort to learn to do this. I will always be learning how to do this better. Teams are important. Tech is important. But if you don't have a culture of respect for the truth of the narrative of the domain, it will seem like success is always within reach but never quite grasped to its high potential.I help companies search for true success in software through connecting the business and technology teams using DDD and the related methods that emerge from this paradigm.I live in Oregon with my wife Sandy and we go to the beautiful Oregon Coast any chance we get!