Talk on expressing architecture in code: AgileRoots 2010
This talk that I delivered at AgileRoots 2010 was recently posted (or at least I recently learned it was posted). It's one of my favorite talks to deliver and the topic is important for all developers since writing code that expresses your design intent is hard but so very helpful for everyone who must read it later (including you!).
Abstract: Because of Eric Evans' Domain Driven Design, agile developers are familiar with embedding their domain models in their code, but architecture and design remain hard to see from the code. How can we improve that? This session presents a new agile technical practice, an architecturally-evident coding style, that lets you drop hints to code readers so that they can correctly infer the design and architecture. It builds upon ideas like Kent Beck's Intention Revealing Method Name pattern and provides a set of lightweight coding patterns and idioms that let you express your design intent in the code.
You should see an embedded video player above, but if you don't, try another link to the video.