Designing easy-to-use APIs is not always an easy thing to do. In fact, some developers feel guilty taking time from coding for design – especially spending design time on such things as method names, request and response objects or service names. If you don’t take the time upfront then you are destined to deal with technical debt (design debt) later. How would you feel going to work each day knowing you will use an API that was poorly designed? Yeah, not good. This Thursday, I’ll be speaking at the API Strategy conference, presenting a case study describing how Ancestry.com reinvented its internal APIs to be more consistent, discoverable and easy to use – while simultaneously serving millions of subscribers.
About Harold Madsen
Harold Madsen directs the APIs at Ancestry.com, the world's largest online family history resource with the mission to help everyone discover, preserve and share their family history. He has over 20 years’ experience in engineering and management and thrives on creating clean, easy to use and accessible APIs. Harold manages both internal and external APIs at Ancestry.com. His most recent endeavor involves leading the Company’s effort to redesign the internal APIs based on high internal standards and a unified presentation layer across all teams, stacks and departments.Harold enjoys hiking and camping in his free time and has hiked 10 mountain peaks and climbed one pyramid in Egypt. He is also distantly related to John Lackland, king of England of the Robin Hood legends.