Tech Roots » Christopher Bradford http://blogs.ancestry.com/techroots Ancestry.com Tech Roots Blogs Fri, 19 Jun 2015 16:53:54 +0000 en-US hourly 1 http://wordpress.org/?v=4.2.2 2015 Hack Days at Ancestryhttp://blogs.ancestry.com/techroots/february-2015-hack-days/ http://blogs.ancestry.com/techroots/february-2015-hack-days/#comments Wed, 29 Apr 2015 16:23:51 +0000 http://blogs.ancestry.com/techroots/?p=2984 Several years ago, we introduced FedEx Day at Ancestry: a 24-hour hackathon to build something fun & innovative, work with people other than your everyday team, and learn new technologies and skills. Participation is voluntary and we noticed that the number of people participating was starting to decline. We gathered feedback from the teams and made… Read more

The post 2015 Hack Days at Ancestry appeared first on Tech Roots.

]]>
Several years ago, we introduced FedEx Day at Ancestry: a 24-hour hackathon to build something fun & innovative, work with people other than your everyday team, and learn new technologies and skills. Participation is voluntary and we noticed that the number of people participating was starting to decline. We gathered feedback from the teams and made a few changes in February of this year in response.

First, the name “FedEx Day”, as noted in the post linked above, came from the report of Atlassian‘s 24-hour hackathon in Daniel Pink‘s book, Drive — essentially asking “What can you deliver in 24 hours?” Atlassian has since renamed their event “ShipIt Days”, and we have also changed the name of our event to “Hack Days”. Our format has shifted from a single 24-hour period to 2 full business days with our showcase on the afternoon of the second day. Teams are still welcome to stay as long as they like overnight, but we had learned that for many people, the 24-hour format was a deterrent. Another important point of feedback was that there were essentially two kinds of projects people wanted to work on: “just for fun” projects that may not have any connection to our business, and product ideas that they would like to see included in our product offerings. (It’s remarkable how many of our software developers are really passionate about our customers and the service Ancestry offers!) So we decided to create two corresponding prize categories, with fun awards (board games, trophies, bobbleheads, etc.) for the first and cash awards for the second.

So, what was the outcome of these changes? We had our highest participation ever, with over 30 teams showcasing their work (we even had to extend our showcase by half an hour to accommodate everyone). We also noticed that the quality of the projects was very high, with far fewer crashes, bugs, and “it worked on my machine 15 minutes ago!” (we think this may be because people actually slept at some point during the night).

Judges for our event include senior executives, including our CEO, Tim Sullivan, who were very impressed with the great ideas and execution.

The prize-winning projects included:

“Just For Fun” awards

Bug Award: Team Automagic — Michael Russo, Jed Burgon. This was an internal tool built by IT folks to help automate the configuration and installation of custom software packages for teams.

Most Evil: Roots of Evil — Ishpeck Tedjamulia, Peter Funk, Emanuel Blanco — a dungeon-like game that pits your battle skills against those of ancestors in your family tree!

Geek Award: Team Loosely Coupled — Robert Schultz, Alex Arkhipov, Chris Bradford — a proof-of concept for cloud deployed, automatically managed microservices running Node & Zookeeper on AWS

Most Entertaining: Team Rewarders — Ramya Rengarajan, Phani Kumar Balusu, Bonnie Bingham, Jason Bramble — award badges, merchandise, and discounts for activity on the site

Product-related cash awards

Honorable Mention: Team Awesome — Danny Darais, David Graham, Dave Menninger, George Gerard, Chris Adams, Jeff Alton, Kelv Cutler, Mike Smeltzer, Jeff Lord, John Mulholland — break through “brick walls” in your research by requesting help from other users, and offer your help to others for recognition on a leaderboard

3rd Place: 1940CEnsRecs2AMT — Roy Mill, Jeff Gardner — Give a face and a story to those in the census; connecting you from census-to-picture-to-story

2nd Place: Mobile — Gary Mangum, Brian Mullen, Jon Bott, Eric Williamson, Sam Gubler, Kory Garner, Keld Sperry, Bart Whiteley, Dan Lincoln, Sophal Mok — a new mobile app experience

1st Place: Eye of Sauron — Gaurav Shetti, Gann Bierner, Alex Kudinov, Max Bolotin, Hui Zheng — A guided search experience drawing on the characteristics of our data collections to help users narrow down searches

We were very pleased with the success of our first event this year incorporating these changes. We have heard from a number of teams that their good experience with Hack Days has started to influence how they work together as a team in their day-to-day work — an added benefit! Teams find themselves really energized by sitting and working together to brainstorm and solve problems without as much regard to roles & process. Some teams are incorporating short “Hack Days”-like sessions into their sprints to swarm on solving interesting problems in their current projects.

With the success of Hack Days, our next big challenge is to figure out how to make this scale as participation continues to grow.

The post 2015 Hack Days at Ancestry appeared first on Tech Roots.

]]>
http://blogs.ancestry.com/techroots/february-2015-hack-days/feed/ 5
Technical Management at the Right Levelhttp://blogs.ancestry.com/techroots/technical-management-at-the-right-level/ http://blogs.ancestry.com/techroots/technical-management-at-the-right-level/#comments Tue, 23 Apr 2013 16:14:35 +0000 http://blogs.ancestry.com/techroots/?p=493 As is often the case with technical managers, I started out as a software engineer, and miss the experience of day-to-day coding. I became a team lead and then “officially” moved into the ranks of management as I took responsibility for multiple development teams. As I considered how to be more aware of how these… Read more

The post Technical Management at the Right Level appeared first on Tech Roots.

]]>
As is often the case with technical managers, I started out as a software engineer, and miss the experience of day-to-day coding. I became a team lead and then “officially” moved into the ranks of management as I took responsibility for multiple development teams. As I considered how to be more aware of how these teams were running and how to provide constructive feedback to the leads of those teams, I decided to try an experiment: I would spend a few hours each week pair programming on these teams. This way I could be in the midst of the operation of the team, see how they interact, what their code looks like, their testing practices, their communication, and so on – with the added benefit of scratching my own coding itch.

I went into the experiment excited about the opportunity to work on a single-page application in Javascript, a back-end Java integration project, a WinForms C# desktop application, an ASP.NET MVC Web API service, a Ruby on Rails app, iOS and Android applications. Maybe I could even squeeze in some time on our Windows 8 app. With several of these technologies, my experience was limited to dabbling, so I was looking forward to learning, as well as contributing to the production code base. After all, that was how I measured my contribution to the company before moving into management.

I paired with several teams over the course of about a month. What I discovered was that I got so involved in the specifics of the problem at hand that I didn’t get the benefit of the insight into the team that I had been hoping for. I thoroughly enjoyed coding, designing, talking through solutions, identifying areas that affected multiple teams, and even (believe it or not!) occasionally teaching a developer a new trick. But I didn’t really get a great sense for the team dynamics.

I decided to abandon the experiment and replaced it with more in-depth one-on-one meetings with my team leads. I got a much better sense for what was going well and where my leads and their teams needed my input. Lesson learned: lead and manage at the right level. As much as I wanted to be in the code, it was the wrong level for me.

The post Technical Management at the Right Level appeared first on Tech Roots.

]]>
http://blogs.ancestry.com/techroots/technical-management-at-the-right-level/feed/ 1