A few years ago I built an automated solution for tracking our trash and recycling schedules.
I did it because I was really getting tired of forgetting to take the trash/recycling to the curb,
or forgetting which weeks are recycling weeks and which aren't; staying on top of these becomes
particularly important on weeks where the pick up schedule(s) change (e.g., in observance of holidays).
The week/week after of Christmas is always a big one, because our trash and recycling typically ends up
full: the trash is full as a function of hosting Christmas dinner for the family, and the recycling
is full from cardboard boxes and wrapping paper and the like.
I've had this reminder program running for years now, but once per year — at this time of year —
I have to do some things to ensure it'll run correctly for the following year. This partly means
inputting the new schedule for the following year. I do this as soon as I can after it arrives at
the end of December. It's a little bit of a pain because I have to remember things like the numbering
Microsoft SQL Server uses for its days of the week enumerations. Trivial, but not trivial, if
you take my meaning.
So when the reminder was sent out this week, my reaction was satisfaction that the changes I'd
made hadn't broken anything. My reaction SHOULD have been (1) get the trash out to the curb tonight!
(2) satisfaction that the changes I'd made hadn't broken anything.
Yes, the trash truck came rolling around this morning at 7:15 AM, and I did not have my bin,
which filled to the top, out for pick-up.
My neighbors CANNOT KNOW this happened.
|