Notification Service: DAO refactoring
3 November 2008This morning Ray Krueger was nice enough to stop by and show me the error of my ways on my copy of a copy of a copy of a Data Access Object for the Notification Service. It’s always nice when someone who actually knows what they are doing drops by to give you a little much-needed guidance.
Really. I appreciate the feedback.
Of course, now I am going to have to study this and this, and probably this as well. If I am successful in making the transistion (… and let’s face it, there’s no real guarantee there!), then I will really feel compelled to not only refactore the NotificationTemplateDao, but also the LookupTableDao, and if I get really motivated, the data managers for the Approval Service and Authorization Service as well. Might as well clean it all up while I’m at it!
What is that old agile/xp philosophy again … “relentlessly refactor”?!
I’m not really afraid of a little work. In fact, I can lay right down beside and go right to sleep with no problem! But I was actually making a little progress on this portion of my project and now I have that deer-in-the-headlights hesitation as I ponder the choice between stopping now and making things better while I am thinking about it or just forging blindly ahead while lying to myself about coming back around later and cleaning it up once things are finished and working.
Decisions, decisions, decisions …
One Response to ' Notification Service: DAO refactoring '
Leave a reply
You must be logged in to post a comment.
on November 5th, 2008 at 5:43 am
lol glad I could drop by and cause you some stress
Honestly, I don’t know that there’s an answer to the “copy of a copy of a Dao” in there at all.
Though there really were no errors in your ways, there are just other ways