Episode 153 David Biesack, Chief API Officer at Apiture

If you enjoyed the lengthy API discussion last week, then this episode will be no different. We’re speaking to David Biesack, Chief API Officer at Apiture, where they’re using efficient solutions to hold together a network of their banking APIs for a variety of financial institutions. As you can imagine, nearly a hundred customers will have hugely varying needs. So how do David and the Apiture team do it? David explains their system of avoiding versioning, by constantly thinking ahead to what features will always be timeless? It’s due to this attention to detail that APiture has avoided the classic pitfall of “API sprawl”, something we went into earlier this week on the podcast. If there’s one thing to know about David, it’s that he is a lover of documentation, and perhaps unsurprisingly, this love generates from the many times he’s been assigned to tasks with documentation that, quite frankly, sucks. So it’s become a passion of his, to not just write things down in a meaningful way, but also to get people in a room, and answer questions in a judgement free way. We think the success of Apiture speaks to the immense value of this practice. Reach out to David here: https://www.linkedin.com/in/davidbiesack/ Find out more and listen to previous podcasts here: https://www.voxgig.com/podcast Subscribe to our newsletter for weekly updates and information about upcoming meetups: https://voxgig.substack.com/ Join the Dublin DevRel Meetup group here: www.devrelmeetup.com

Episode source