What is domain modeling?

[@seckinkukrer6920]

Good luck with your exploration!

[@dionbridger5944]

Hi Eric, A thought provoking video that mirrors some of my own feelings about the necessity of domain modelling (which in my view can be achieved through robust data modelling). Data modelling / domain modelling is an indispensable component of the software development process, but because these models are latent in code rather than made fully explicit, and because they are developed in an ad-hoc way by multiple programmers often working at cross-purposes, the code develops redundant and mutually incompatible partial domain models which require data to be translated between them so that data can be shared. Are you still working on the book about domain modelling?

[@jonnmostovoy2406]

Your basho shirt looks really fresh! Mine is completely demolished. :D Where did you get it?! Can we still get those? Those are the best!

[@AyuPapaBonanza]

I feel the same with TDD, it puts the test in the very front and centre, somehow is against my instinct. The ideal in my opinion should be the code is so efficient and correct and clear that it is so trivial to write tests, to a point that we do not need to write any tests. Or in other words, I feel tests are not essential for developing healthy complex systems, even though it is good technique to make things a little better.

[@elcapitan6126]

automated tests are a tool like all others. TDD is a nice idea around a process but it doesn't solve the core problem of programming any more than strong typing does: carefully thinking and designing *what* the system or library means and is with precision. TDD folk seem to think there's an automatic path from their strict process to a design that is useful and shown to fulfil the spec. But the devil is always in the spec itself