Under the hood and working with .Net, TDD, Software Design, and Agile Stuff
It's time for another episode in the continuing saga of "doing stupid things in stored procedures."
My colleague is looking at some code that we need to modify with a temporary fix. The legacy system calls into a stored procedure which then takes the arguments coming in and passes them to a COM object (via DCOM) to send an email (it also decides whether to send the email). The COM object promptly opens up a database connection to go back to the very same database to get more information in order to create an email. And of course there's the issue that the stored procedure is called from middle tier code to begin with. WTF. There are so many things wrong with this scenario that I don't even know where to begin.
About Jeremy D. Miller
Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy previously worked as a systems architect building mission critical supply chain software for a Fortune 100 company and learned agile development practices as a .Net consultant at ThoughtWorks, one of the pioneers of agile development. Jeremy is the author of the open source StructureMap (http://structuremap.sourceforge.net) tool for Dependency Injection with .Net and the forthcoming StoryTeller (http://storyteller.tigris.org) tool for supercharged FIT testing in .Net. Jeremy's thoughts on just about everything software related can be found on his weblog "The Shade Tree Developer" at http://codebetter.com/blogs/jeremy.miller, part of the popular CodeBetter site. Jeremy is a Microsoft MVP for C#.
