David Biesack serves as Chief API Officer at Apiture. David applies his passion for building great APIs and a compelling developer experience to the design and architecture of Apiture's Amazing API ecosystem. David has over thirty years of industry experience creating reusable, robust, and elegant enterprise software systems. He strives to make software [development|developers] better, stronger, faster at solving complex customer problems.
The Reality of API Programs Shane O'Conner (Founding Team @ Scalar ) has started a new Q&A series on LinkedIn called Behind The API. Shane graciously asked me to participate, and also allowed me to re-publish the content here. Below is Shane's initial announcement of the Q&A, followed by the full content. Introduction Below is Shane's first LinkedIn announcement on Nov 11, 2025, sharing the "Behind The API featuring Davod Biesack" article: Shane wrote: I've been thinking a lot about what...
Note: Below is an article I originally wrote for Nordic APIs, published as Meet Hyrum and Postel on December 9, 2020. -- djb, Nov 16, 2025 How do Hyrum’s Law and Postel’s Law affect API designs? Luckily for us humans, and especially that narrow subclass of humans who build APIs, API design is a field that has not been automated or botified… yet. Sure, one can point at a database schema and generate what one can label an “Application Programming Interface.” But it is an API only in a literal...
To kick off The Language of API Design series, we will take a brief but important diversion from the OpenAPI Specification and it’s unique but powerful language of API design. Our detour will focus on a different sort of language: the ubiquitous language. In other words, today, I’m “Mr. Language Person”.1 The term “API Design First” is quite popular now, but it is misleading. If one began by first creating an API design (fun as that may be for some of us), the result is likely not going to...