Archive for November, 2010

.

The secrets of an elusive santa

At some point late last year I decided thefamilywishlist.com should have a secret Santa tool. As useful a feature as it may be, I couldn’t decide on the details of integration. And as most of you know without a clear idea for a solution or interface, it’s easier to just put a feature off. There are just so many potential complications.

So put it off is what I did. However, I confidently marked Friday November 27, 2010 off on my calendar as the day that I would implement the secret Santa tool. And as unexpected as expected, that day eventually came.

I’m only partially joking. I did in fact mark November 27 for secret santa development, but did so on November 25. Less impressive, true, but — well, just less impressive all around.

I ended up adding it as a tool that can be used by registered and anonymous guests. As such, when logged in it appears under the tools menu. When not logged in, it appears as the item furthest right in the main menu.

You don’t have to be a family wishlist user to take advantage of the secret Santa tool, but it’s neater if you are. The participants you add don’t have to be registered users either, but it’s neater if they are.

 

Using the secret Santa tool

A secret Santa event is made up of some descriptive data, and a list of participants.

 

Event details

Title — The events title should be pretty self-explanatory. It lets your participants know which secret Santa the email they receive refers to. This should be especially useful if you are a participant in more than one, and if there is some participant overlap.
The initial event title is generated as “[current year] Secret Santa of [some word]“, but feel free to set the title to anything relevant to your event.

Name — The name field lets your participants know who set up the event. Useful if they need to contact you for any additional information, and in hope that when recognizing your name they won’t immediately discard the e-mail as spam.
If you’re logged in, the name field will not appear – the tool will use your name automatically.

Description — Provides a bit of space for any additional information you might like to convey (rules, gift-exchange location and time, or anything else you can think of).

 

Participants

There are two ways to add participants to your event. The easiest is if you’re logged in. Simply click on the users in the list of your friends to the left.
Additionally, You can enter e-mail addresses into the add field, and click the add » button. If the email address is already associated with a user of the system, their name will be displayed. If not, it will show their e-mail address.
If you make a mistake, click [oops] next to a participant to remove.

If you’re not logged in, don’t forget to add yourself!

 

 

Once you’ve set up your event, click the Done! (send the emails!) button. Participants will be randomly paired, and e-mails to each queued for sending.

Don’t be alarmed if they don’t receive the emails immediately. I’ve implemented a queuing system do distribute the actual mailing.
As long as the system is not in heavy use, e-mails should be sent within ten minutes. After that, you will still have to wait for them to make their way across the internet (or tangled mess, as we call it in the business).
Seriously though, I’ve called it that maybe once before.

 

The Result

Each participant is sent an e-mail which lets them know who they’re to purchase a gift for.

This should be especially useful for secret Santa events involving physically distant participants, who may otherwise need to be drawn for by another participant.

 

Tips

If you need ideas for a gift, an obvious place to look is the wishlist of the participant you’ve been assigned. If they’re not a registered user, you can add them as a friend and they’ll be invited. Beware, though, the invitation e-mail will reveal who they were invited by, which can spoil the surprise of a secret Santa. At that point, you may as well just call it Santa.

An obvious solution is to add all participants as friends before creating the event. This way, they will all receive invitations from you (the organizer) and what’s more, it will be easier for you to add them to the event.
An alternate (if less elegant) solution is to manually request that a friend invite them.

 

 

If you’ve gotten this far I expect you’re a little alarmed but not at all disgusted that I could write so many words on such a simple subject, and that I would choose to do so.
But why not put that wonder aside, and head over to the family wishlist to try out its entirely new secret santa tool?

 

Lead monitor

Remember the lead automation system I did for Cruise Experts Travel?

Probably not, but that’s okay! It’s up and it works nicely.

But what if something goes wrong. What if it stops polling for leads? The client won’t like that! Unfortunately, this can be discouraged but can’t be completely prevented. At least not within reason.

  • The server could be turned off
  • its connection could die
  • The service could be halted and not restarted

These could be the result of human or program error, or environmental conditions.

Since we can’t prevent disruption, we should at least deal with it – in this case, by responding to it.

With that in mind, I made a monitoring program. It checks the temporary lead database and notifies me when any are stale. Using it, I can quickly see when something goes wrong and can act accordingly. In many cases, I should be able to respond before the client even knows there was an issue.

Since the two most likely of those cases do not directly involve me or the lead automation system, I’ve set the monitoring program up to run on one of Twisted Pear‘s computers. (The company who handles their computer and network needs).

In the third case, should it be necessary, Twisted Pear can easily restart the service as well.

Airtime data 2

I’ve added this last month’s data (up to November 17th) to my database of airtime usage. I also adjusted the script to automatically generate the answers for me – instead of summing and averaging manually.

I also noticed that Koodo does something strange! Jt’s calls often come in as private, so the number they’re from won’t be in my usage logs. Koodo logs those calls as from my phone number!
This may be what all or most phone companies do, but it’s still strange.

I rarely get a private call from anyone other than Jt, and when I do they are either very short or “missed”. I’ve had it add those entries to his minute bars.
Once I did that, his minutes jumped way up, and it became pretty clear that I speak most with him.

For phone usage graphs, this is a mistake. I should display those as either private or me. I doubt they would count as his number in any sort of plan optimization I could do.

I do wonder if I could add my own number as a frequent caller though, and have that cover all private numbers. That would be neat.

How many minutes do I average per month? 440
This went way up! It was 195 before.

How many billable minutes do I average per month? 132
This didn’t change much! It was 117 before.

Who do I talk to most during billable time? jt, but it’s close (fiona is 92% of jt)

Who do I just talk to most? jt

Which hours do I use the most? 5pm, 6pm, 4pm

.
.