Two things:

a) If you actually get that job at MDS, I will kill you, and start showing up to MDS to work in your place. So, do good at the interview... I need a 'nother victim job.

ii. Geez... you two love to reinvent wheels, don't you? That's fine and dandy, but the reason I bring it up is you'll probably want to do that when someone hires you, and that's a bad thing (tm). It's a waste of their time and money and your intellectual effort.

You both need to read this. And when you're done reading it and think you understand what it's saying, read it again.

Then think on it and read it a third time.

mmmm Joel is cool. I have read that article before and agree with it, throwing out all the old code in favor of new is never a good idea. I learned that lesson, at Com Dev, where we tried to build our own EMS system instead of buying one from a respected source. We eventually ended up abandoning the old system in favor of the commercial product. That seems to go against what you are preaching here, but I disagree. The lesson there is that a group of 8 people were trying to reinvent a wheel that had been perfected by a team of 100, Com Dev just thought they could do it cheaper, they were very very wrong. I have had the desire to throw out entire modules of the project I am working on now, but I am pretty good at suppressing those desires. Refactoring is far better than redoing.

I don't really consider what I am doing with the calendaring idea to be reinventing the wheel, but instead I am playing. I have never written a calendaring system before and it could pose some interesting problems. As I said in my reply to you in my journal, its more a learning experience than anything else. The fact that it is work inspired does not imply I would ask or even want WA to use any calendaring tool I would potentially write.