Netflix introduced some brilliant easter eggs for Arrested Development fans in preparation of Season 4. Here’s what I’ve found:
Blue handprints on searches that involve the word “blue”
Bananas instead of stars on Arrested Development rating in instant queue (props to Scott Nellé for pointing this one out)
Les Cousins Dangereux
Girls with Low Self Esteem
Girls with Low Self Esteem: Newport Beach
Families with Low Self Esteem
Franklin Comes Alive
World’s Worst Drivers
El Amor Prohibido
Mock Trial with J. Reinhold
Ready, Aim, … Marry Me!
This is an impressive list, nice work Netflix! I probably enjoyed seeing El Amor Prohibido the most, they reached deep for that one. I know I watch too much AD, and as a result, here is a list of titles I was greedily disappointed were absent:
I recently launched a new plugin on the WordPress plugin repository: SuperCPT. SuperCPT is a WordPress Plugin to help developers build insanely easy and attractive custom post types, custom post meta boxes and fields, and custom taxonomies. Install it from the WordPress.org Plugin Repository.
My dog Boomer, a 4-year-old Australian Shepherd, has a funny parlor trick: he sings happy birthday. One day, when we were singing it for someone’s birthday, he just started singing along. It’s the darnedest thing, and he only does it with Happy Birthday. Pretty quirky. Anyway, here he is singing to one of my best friends for his 30th birthday.
At Union Street Media, we have a support ticketing system that uses ticket IDs of the form ABC-123456. That gives a total range of 17,576,000,000 possible ticket values, roughly (I’m sure they removed some dirty words from the three-letter combo). Today, we had a ticket ID collision (where a new ticket has the same ID as an old one) and I thought, “wow, what are the odds of that happening?” Well, it struck a chord in me so I decided I’d figure out exactly what the odds were!
Essentially, this is the birthday problem on a much bigger scale. We have about 26,000 tickets in our system. Here’s the math:
The result? At 26,000 tickets, there’s about 2% chance of a collision. Those odds may be low, but they are considerably higher than I was expecting!
The take-away here is that as a software developer, you need to know that you can’t depend on variability to prevent collision. Kayako should have been checking to see if a ticket ID exists in the database before assigning it to a new ticket*. I’m sure there are people using their software who have many more tickets in their system than we do. At 157,000 tickets, there’s a greater chance of having a collision than not having a collision.
*To be fair, we’re using an old version of Kayako’s software. I would expect that they’ve since fixed this bug.