I’m thrilled to have been invited to deliver the keynote talk at CodeStock 2013 in Knoxville this July. I’ll be talking about how Domain Driven Design (DDD) has inspired me a-new after almost 25 years of software development. And I hope to inspire others to take a closer look at DDD as well.
In addition to the keynote, I submitted two conference sessions and sessions are selected by a voting process where registered attendees vote for the talks they want to hear. Such a cool idea.
I feel a little guilty submitting sessions since I already will be presenting the keynote and there are so many awesome abstracts including some on EF and DDD.
Here are the two talks I submitted if you’re planning to attend CodeStock and interested in hearing me go on about them. But if that’s the case, you’ll need to go vote.
Demo-ware is great for getting your head around a new topic but we’ve been seeing Entity Framework demo ware for 5 years now. You’re probably not writing an application to manage your music collection or composing yet another Twitter client. You need to build complex applications related to the Core-Domain in the enterprise and therefore you need to know how to integrate Entity Framework in serious and decoupled architectures. In this session we’ll look at breaking up your domain-models following the Domain Driven Design Bounded-Context pattern, splitting and defining entities and aggregates properly in the different domain models and implementing repositories and units of work that are relevant to EF DbContext and DbSets, in the data persistence infrastructure layer. You’ll also see how to build automated tests around code that involves Entity Framework, whether they be integration tests or strictly unit tests where Entity Framework seems to get in the way.
Sometimes learning about Automated Testing from the testing gurus might be a little daunting. It's hard for them to relate to the fears that developers who've never used automated tests before – especially those of us who have been coding for years and years. This will not be a "drink the unit testing or TDD Kool-Aid" session. Instead, I will share revelations that have helped me ease myself and clients into automated testing. Not only has it benefitted my development process, but looking at code from the perspective of "can I test this?" has resulted in a huge improvement in how I design my application architecture. Come dip your toe in the water and see if automated testing might be for you.