Most developers attempt to ignore and put off documentation as long as possible during the development process. However, the return on investment is worth the time and effort — far more than most of us realize. This is particularly true with API documentation.
Working with a recent client, I had the opportunity to use Swagger to document APIs and provide structure around the development process. During daily standups, I may have been known to say that my task for the day was to “get my Swagger on.”
In this post, I want to walk you through my journey with Swagger along with general thoughts, tips, and tricks that I’ve learned along the way so that you too can “get your Swagger on.” Let’s get started…