When the call for speakers was announced, I submitted a couple of topics. My Real-Word N-Layered Domain Oriented Architecture with .NET session was voted up and ultimately approved and I was thrilled! I relished the opportunity to share my own experiences and hear about other people’s experiences. What I failed to truly take into consideration was that I’d have a mere 60 minutes to make it happen.

When the realization did finally hit me, I made a critical decision. Rather than prepping a presentation, I’d drive right into the code. In hindsight, this was probably a big mistake given the breadth of the topic and the wide range of experience. In fairly short order, my session became disjointed, confusing, and probably left the attendees with far more questions than answers. Mental images of monkeys and footballs came to my mind and about 15 minutes in to the session I thought to myself, “Well, isn’t this ironic?”

You see, my intent with SaltFx is to provide a helpful, cohesive, and practical example of a domain-oriented architecture. I want to provide code and a learning experience that people can study, explore, and perhaps even leverage in their own real-world implementations. During my session, however, I transformed into the very bespectacled antithesis of that rapidly estranged goal. In my own defense, I was running on a mere 3 hours of sleep.

I learned a bitter lesson to be sure. Hope for redemption, however, is in the source code (which is currently grossly over-commented and has an alarming lack of unit tests) and the blog posts I intend to write in the coming weeks. Follow this space and we’ll explore the details together. Whether you choose to view it as a purely academic venture, an investment into a practical tool, or comedy relief, I will do my best to keep my end of the deal.