<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: dage212</title>
    <description>The latest articles on DEV Community by dage212 (@dage212_62c1f5ac2eef6ab26).</description>
    <link>https://dev.to/dage212_62c1f5ac2eef6ab26</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3394720%2Fc9844ce4-0390-4fe1-afeb-f420e2665cba.png</url>
      <title>DEV Community: dage212</title>
      <link>https://dev.to/dage212_62c1f5ac2eef6ab26</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dage212_62c1f5ac2eef6ab26"/>
    <language>en</language>
    <item>
      <title>Hope fire-doc can provide a better development experience for everyone</title>
      <dc:creator>dage212</dc:creator>
      <pubDate>Mon, 11 Aug 2025 15:00:59 +0000</pubDate>
      <link>https://dev.to/dage212_62c1f5ac2eef6ab26/hope-fire-doc-can-provide-a-better-development-experience-for-everyone-36p4</link>
      <guid>https://dev.to/dage212_62c1f5ac2eef6ab26/hope-fire-doc-can-provide-a-better-development-experience-for-everyone-36p4</guid>
      <description>&lt;p&gt;&lt;a href="https://github.com/dage212/fire-doc" rel="noopener noreferrer"&gt;&lt;strong&gt;fire-doc&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Supports local API request debugging.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A more user-friendly interface than Swagger.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Simpler to use than Postman.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Frnct2pb5kvw5w39zbims.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Frnct2pb5kvw5w39zbims.png" alt="Fire-Doc Actual Page" width="800" height="410"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>api</category>
      <category>postman</category>
      <category>documentation</category>
      <category>tooling</category>
    </item>
    <item>
      <title>"Would combining Swagger and Postman make a better tool?"</title>
      <dc:creator>dage212</dc:creator>
      <pubDate>Thu, 07 Aug 2025 15:38:14 +0000</pubDate>
      <link>https://dev.to/dage212_62c1f5ac2eef6ab26/would-combining-swagger-and-postman-make-a-better-tool-5gf1</link>
      <guid>https://dev.to/dage212_62c1f5ac2eef6ab26/would-combining-swagger-and-postman-make-a-better-tool-5gf1</guid>
      <description>&lt;p&gt;"As a developer, I've been thinking a lot about what Swagger actually brings to the table — and why tools like Postman still don’t quite meet the needs of developers who care about both testing and documentation.&lt;/p&gt;

&lt;p&gt;So I asked myself: what if we just combine the two? That idea became Fire-Doc.&lt;/p&gt;

&lt;p&gt;I wanted something simple: test an API right away, no need to install heavy tools. Just open and go. And once you're done testing, it should instantly generate the API docs — without having to write a bunch of annotations or boilerplate code.&lt;/p&gt;

&lt;p&gt;In the time it takes Swagger to generate a doc, I could’ve already tested and shipped the endpoint. That’s the inefficiency I wanted to fix."&lt;br&gt;
&lt;a href="https://github.com/dage212/fire-doc" rel="noopener noreferrer"&gt;fire-doc&lt;/a&gt;&lt;/p&gt;

</description>
      <category>go</category>
      <category>api</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Would it be better to combine Swagger and Postman into one tool?</title>
      <dc:creator>dage212</dc:creator>
      <pubDate>Thu, 07 Aug 2025 15:22:48 +0000</pubDate>
      <link>https://dev.to/dage212_62c1f5ac2eef6ab26/would-it-be-better-to-combine-swagger-and-postman-into-one-tool-4dd1</link>
      <guid>https://dev.to/dage212_62c1f5ac2eef6ab26/would-it-be-better-to-combine-swagger-and-postman-into-one-tool-4dd1</guid>
      <description>&lt;p&gt;"As a developer, I've been thinking a lot about what Swagger actually brings to the table — and why tools like Postman still don’t quite meet the needs of developers who care about both testing and documentation.&lt;/p&gt;

&lt;p&gt;So I asked myself: what if we just combine the two? That idea became Fire-Doc.&lt;/p&gt;

&lt;p&gt;I wanted something simple: test an API right away, no need to install heavy tools. Just open and go. And once you're done testing, it should instantly generate the API docs — without having to write a bunch of annotations or boilerplate code.&lt;/p&gt;

&lt;p&gt;In the time it takes Swagger to generate a doc, I could’ve already tested and shipped the endpoint. That’s the inefficiency I wanted to fix."&lt;br&gt;
&lt;a href="https://github.com/dage212/fire-doc" rel="noopener noreferrer"&gt;fire-doc&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>postmanapi</category>
      <category>swagger</category>
      <category>webdev</category>
    </item>
    <item>
      <title>fire-doc published</title>
      <dc:creator>dage212</dc:creator>
      <pubDate>Tue, 29 Jul 2025 14:45:28 +0000</pubDate>
      <link>https://dev.to/dage212_62c1f5ac2eef6ab26/fire-doc-published-25p4</link>
      <guid>https://dev.to/dage212_62c1f5ac2eef6ab26/fire-doc-published-25p4</guid>
      <description>&lt;p&gt;Recently, I found that Swagger is not always satisfactory to me during development, and Postman also needs to be downloaded and logged in, so I thought about developing a lightweight interface debugging tool that combines the functions of Swagger and Postman.&lt;br&gt;
&lt;a href="https://github.com/dage212/fire-doc" rel="noopener noreferrer"&gt;fire-doc&lt;/a&gt;&lt;/p&gt;

</description>
      <category>api</category>
      <category>postman</category>
      <category>tooling</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
