<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Swagger on Random Ramblings</title><link>https://blog.foundev.pro/tags/swagger.html</link><description>Recent content in Swagger on Random Ramblings</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 05 Mar 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.foundev.pro/tags/swagger/index.xml" rel="self" type="application/rss+xml"/><item><title>The Joy and Pain of Swagger</title><link>https://blog.foundev.pro/2021/03/05/the-joy-and-pain-of-swagger.html</link><pubDate>Fri, 05 Mar 2021 00:00:00 +0000</pubDate><guid>https://blog.foundev.pro/2021/03/05/the-joy-and-pain-of-swagger.html</guid><description>&lt;h1&gt;The Joy and Pain of Swagger&lt;/h1&gt;&#10;&lt;p&gt;I have had to use &lt;a href="https://swagger.io"&gt;Swagger&lt;/a&gt; for many a project since my first introduction to it while working for an ecommerce site in 2015. I did like being able to&#10;easily convert documentation into viewable API docs complete with executable examples and forms ready to go that let me actually try out my new API. In many ways it is the closest&#10;to the promise of API first development.&lt;/p&gt;</description></item></channel></rss>