I changed teams at the beginning of the year from search services to an R&D team working on some exciting projects. The team has created a distributed system to repeatedly process and analyze many billions of family history records using a complex and time consuming algorithm that has been challenging to scale up and out. Read More
Tyler Jensen is a senior software engineer in R&D at Ancestry.com. He has worked in the software industry since 1992. He loves to solve difficult technical challenges. When he's not working or writing or reading, he enjoys spending time with his wife and four children.
Today is Halloween and my whole team got into it. I brought the costumes and they graciously agreed to wear them long enough to join the company costume contest. The Search Services Team Humor warning — we didn’t win the contest but we did experience collective shame and humiliation–or what we prefer to call team Read More
So much has been written on the subject of work-life balance that it has become an Internet cliché, an overloaded phrase with nearly as many interpretations as there are Google results (247 million). Nearly every employer’s website claims a great work-life balance, which has become marketing fluff that enjoys very little credibility with many considering Read More
Ancestry.com, like any other site with millions of subscribers, experiences predictable load patterns throughout the day. To maximize site performance and customer satisfaction, we make every effort to schedule maintenance during off-peak intervals. Content processing, especially our repository of hundreds of millions of images, on the other hand, is a constant ongoing effort, and in Read More
About 450 years ago John Heywood wrote, “many hands make light work.” The same can be said of image and data processing. Distributed parallel computing (DPC) makes it possible for us to do the work described by Michael Murdock in his series on the image processing pipeline. If you haven’t already, take a moment to Read More
Imagine a world that corrects itself when something goes wrong. A customer clicks a link to an image and gets a message that the image could not be displayed. An hour later that same customer or another customer clicks that same link and the image can now be displayed. This is what we call user Read More