Eric Evans' JavaPolis talks on Domain-Driven Design

The Monday morning talk on JavaPolis I attended this year, was exactly in my domain of interest: DDD. Eric Evans started -after a ten minute tech problem- by setting up a small domain example - something with shipping lines and routing of containers.
His talk started quite slowly, and with a lot of side information distracting the audience of DDD, so I got a little distracted, but there I underestimated Eric, he came back on the exact DDD powers shortly after. I learned a lot with his talk, mostly that there is no 1 domain model in a -larger- project, you have to find out what are the sub domains and concentrate in getting each sub-domain right and think about a strategy on how to join them together or have them communicating.
I also like Eric's statement that a good domain model can -will- make the difference between a bad/medium or an excellent result coming out of the project. The way he explained this statement is a good way of how to explain is to management, if you are a requirements analyst/software designed just like me.
On Friday morning I also went to Eric's second -and shorter- talk, where he repeated the case details of the shipping company, but to make some other statements, more on the strategic side of domain modelling. Since these two talks, I am a real fan of Eric Evans, and his experience and tactical advice on DDD - I ordered his book this morning!
More info here:
http://domaindrivendesign.org/
http://www.domainlanguage.com/