for Heavybit's DevGuild conference, July 27 2016
When building for developers, many of us start by scratching our own itches. That's great for pulling together an MVP — and doing some interesting engineering along the way — but it's all too easy to get wrapped up in the functionality of the thing and lose sight of what it's like to be on the other side of your API.
To prevent your shiny new tool from being reduced to just a set of inputs and outputs, we explore best practices worth baking into your team's culture — and how to carry those principles through growth and change.