Re: Write Change-Resilient Code With Domain Objects

Loved this short excerpt from Google Testing Blog of why we want to use domain concepts in the code. I particularly noticed that this is a friendly introduction for developers working in emerging domains where the best domain knowledge is just “product idea”.

Write Change-Resilient Code With Domain Objects https://testing.googleblog.com/2024/09/write-change-resilient-code-with-domain.html#comments

I worked with both applications with established domain, such as government processes, and modern “service” apps like instant groceries and internship portals that does not have a very well-defined domain. In Eric Evans’ original formulation, domain-sourced ideas are obvious because there is a clear source — the domain expert. However, many developers today work on startups or SaaS products where the business concepts are sometimes less well-agreed upon. In these environments, you still want to solve business problems, but sometimes your best proxy to that knowledge is product ideas.

An adjacent but interesting problem — I’ve found it counterproductive to “marry” code to the domain while finding product-market fit (PMF) because the business may pivot in unexpected directions, so your “generalizations” often drag you down. My best answer to this conundrum so far is that write throwable code until you find PMF, but be ready for a rewrite once you find it. I’d be very interested if anyone has tried anything different and what the outcomes are.