meeting-scheduling software
Feb. 25th, 2005 02:49 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
cellioI just used MeetingMaker to schedule a weekly meeting. It requires that you specify an end date -- or you can just check "ongoing". Doing the latter causes it to fill in an end date of 12/31/2039. (Which is a Saturday, just in case you were wondering. My recurring meeting is on Tuesday, so one could argue that it should have set the end date differently.)
It quickly reported the two dates this year that some attendee isn't available. This made me wonder whether it was, in fact, searching a sparse calendar all the way through 2039, in which case it gets points for speed but maybe not for appropriateness, or whether it has some built-in limit for how far ahead it will search for conflicts.
By the way, the odds are very good that the room in which my 34-year recurring meeting occurs will cease to be available later this year.
It quickly reported the two dates this year that some attendee isn't available. This made me wonder whether it was, in fact, searching a sparse calendar all the way through 2039, in which case it gets points for speed but maybe not for appropriateness, or whether it has some built-in limit for how far ahead it will search for conflicts.
By the way, the odds are very good that the room in which my 34-year recurring meeting occurs will cease to be available later this year.
(no subject)
Date: 2005-02-26 12:07 am (UTC)But if you look at the dates on my bug, it's Job Immortality. Which would be fine if it worked that way. :-)
(no subject)
Date: 2005-02-27 01:22 am (UTC)Yeah, if only that worked: "gee, I'll insert a bug in the leap-year code that introduces a problem every 4000 years, and wait for them to call me to fix it!".