<?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: Jitendra Balla</title>
    <description>The latest articles on DEV Community by Jitendra Balla (@jkballa).</description>
    <link>https://dev.to/jkballa</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4023061%2F17eb46a5-78e9-4dc8-ba82-c7388a83c521.png</url>
      <title>DEV Community: Jitendra Balla</title>
      <link>https://dev.to/jkballa</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jkballa"/>
    <language>en</language>
    <item>
      <title>Stop retyping your API. Turn cURL into docs instantly.</title>
      <dc:creator>Jitendra Balla</dc:creator>
      <pubDate>Fri, 10 Jul 2026 17:35:00 +0000</pubDate>
      <link>https://dev.to/jkballa/stop-retyping-your-api-turn-curl-into-docs-instantly-38kb</link>
      <guid>https://dev.to/jkballa/stop-retyping-your-api-turn-curl-into-docs-instantly-38kb</guid>
      <description>&lt;p&gt;Here's an absurd thing I did for years.&lt;/p&gt;

&lt;p&gt;I'd test an endpoint with a cURL command. It worked. Then, to document it, I'd open a Markdown file and retype the whole thing by hand. The method, the URL, the headers, the body, a sample response. Information I already had, typed twice, in a format I hated.&lt;/p&gt;

&lt;p&gt;If that's you, today's a good day.&lt;/p&gt;

&lt;p&gt;The cURL to Markdown tool takes your cURL command and turns it into clean, formatted API docs. Paste, get Markdown, done: &lt;a href="https://markdown.co.in/tools/curl-to-markdown.html" rel="noopener noreferrer"&gt;CURL to Markdown&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Why it matters: the cURL command is the thing you actually ran and verified. When your docs come straight from it, they're accurate by default. No translating from memory, which is exactly where mistakes creep in.&lt;/p&gt;

&lt;p&gt;My flow now: test the endpoint, paste the cURL, tidy up the description, ship. Fifteen minutes of formatting became two.&lt;/p&gt;

&lt;p&gt;Try it on the last endpoint you built. Watch the boring part disappear.&lt;/p&gt;

</description>
      <category>api</category>
      <category>markdown</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Nobody writes bad docs on purpose. It just happens.</title>
      <dc:creator>Jitendra Balla</dc:creator>
      <pubDate>Thu, 09 Jul 2026 17:32:32 +0000</pubDate>
      <link>https://dev.to/jkballa/nobody-writes-bad-docs-on-purpose-it-just-happens-2kna</link>
      <guid>https://dev.to/jkballa/nobody-writes-bad-docs-on-purpose-it-just-happens-2kna</guid>
      <description>&lt;p&gt;Every project I've worked on had bad docs at some point. Not once was it a decision.&lt;/p&gt;

&lt;p&gt;It happens slowly. A feature ships without docs because the deadline was tight. The next one skips docs too, because last time nothing broke. Six months later someone opens the wiki and finds three pages that contradict each other and a README that still says "coming soon."&lt;/p&gt;

&lt;p&gt;Here's the reframe that changed things for me: docs are not a writing problem. They're a systems problem. Good docs come from removing the friction that makes people skip writing, not from trying harder.&lt;/p&gt;

&lt;p&gt;That's what this series is about. 30 days of making documentation less painful, using free tools you can start with today. No enterprise platform. No approval process. Just less busywork.&lt;/p&gt;

&lt;p&gt;Tomorrow we start with the one that fixed my whole workflow: turning API tests into docs without retyping anything.&lt;/p&gt;

&lt;p&gt;If your docs are held together with hope and copy-paste right now, welcome. Let's fix it.&lt;/p&gt;

</description>
      <category>markdown</category>
      <category>documentation</category>
      <category>webdev</category>
      <category>100daysofcode</category>
    </item>
  </channel>
</rss>
