<?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: Tushar Patil</title>
    <description>The latest articles on DEV Community by Tushar Patil (@tusharpatil25).</description>
    <link>https://dev.to/tusharpatil25</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%2F4083127%2Fc9a4ea21-e8fb-4eb7-91fe-d2171a193f12.jpg</url>
      <title>DEV Community: Tushar Patil</title>
      <link>https://dev.to/tusharpatil25</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tusharpatil25"/>
    <language>en</language>
    <item>
      <title>### 🚀 Developer Tool Discovery: Hurl</title>
      <dc:creator>Tushar Patil</dc:creator>
      <pubDate>Tue, 13 Oct 2026 12:28:50 +0000</pubDate>
      <link>https://dev.to/tusharpatil25/-developer-tool-discovery-hurl-o9l</link>
      <guid>https://dev.to/tusharpatil25/-developer-tool-discovery-hurl-o9l</guid>
      <description>&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuyle1pnr5pd3qlv8vwwe.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuyle1pnr5pd3qlv8vwwe.png" alt=" " width="800" height="404"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you work with REST APIs, you probably know how repetitive it can be to test the same requests manually.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hurl&lt;/strong&gt; is an open-source command-line tool that lets you write HTTP requests and their expected results in simple, readable text files. You can chain requests, capture values from responses, and verify that your API behaves as expected.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What makes it worth exploring?&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Readable tests:&lt;/strong&gt; Store API requests and assertions in plain-text &lt;code&gt;.hurl&lt;/code&gt; files.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Request chaining:&lt;/strong&gt; Capture a token from a login response and use it in the next request.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Automated checks:&lt;/strong&gt; Validate status codes, response headers, JSON values, and request duration.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CI/CD integration:&lt;/strong&gt; Run the same tests locally and in your build pipeline.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Where it fits:&lt;/strong&gt; Backend development, API testing, QA automation, and CI/CD workflows.&lt;/p&gt;

&lt;p&gt;🔗 Official website: &lt;a href="https://hurl.dev/" rel="noopener noreferrer"&gt;https://hurl.dev/&lt;/a&gt;&lt;br&gt;&lt;br&gt;
💻 GitHub: &lt;a href="https://github.com/Orange-OpenSource/hurl" rel="noopener noreferrer"&gt;https://github.com/Orange-OpenSource/hurl&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A useful alternative to consider if you prefer keeping API tests alongside your source code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How do you usually test your APIs — Postman, curl, or automated tests?&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>devops</category>
      <category>opensource</category>
      <category>softwaredevelopment</category>
      <category>apitesting</category>
    </item>
    <item>
      <title>🚀 Developer Tool Discovery | Mergiraf</title>
      <dc:creator>Tushar Patil</dc:creator>
      <pubDate>Tue, 13 Oct 2026 12:15:49 +0000</pubDate>
      <link>https://dev.to/tusharpatil25/developer-tool-discovery-mergiraf-4oi3</link>
      <guid>https://dev.to/tusharpatil25/developer-tool-discovery-mergiraf-4oi3</guid>
      <description>&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5dcbm4o6j9oor72tne5m.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5dcbm4o6j9oor72tne5m.png" alt=" " width="572" height="562"&gt;&lt;/a&gt;Ever had a Git merge conflict even when both developers’ changes could work together?&lt;/p&gt;

&lt;p&gt;I came across Mergiraf, a tool that takes a different approach to resolving these conflicts. Instead of looking only at individual lines, it considers the structure of your code to determine whether changes from both branches can be combined.&lt;/p&gt;

&lt;p&gt;What makes it useful?&lt;/p&gt;

&lt;p&gt;• Works with Git workflows, including merge, rebase and cherry-pick.&lt;br&gt;
• Can resolve certain conflicts that traditional line-based merging struggles with.&lt;br&gt;
• Supports multiple programming languages and configuration formats.&lt;br&gt;
• Leaves conflicts for manual review when it cannot safely resolve them.&lt;/p&gt;

&lt;p&gt;Who might find it useful? Developers working on shared repositories who regularly deal with merge conflicts.&lt;/p&gt;

&lt;p&gt;🔗 Official website: &lt;a href="https://mergiraf.org/" rel="noopener noreferrer"&gt;https://mergiraf.org/&lt;/a&gt;&lt;br&gt;
💻 Source code: &lt;a href="https://codeberg.org/mergiraf/mergiraf" rel="noopener noreferrer"&gt;https://codeberg.org/mergiraf/mergiraf&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A useful tool to know about if Git is part of your daily workflow.&lt;/p&gt;

&lt;p&gt;Have you tried any tools that make Git conflict resolution easier?&lt;/p&gt;

</description>
      <category>programming</category>
      <category>opensource</category>
      <category>git</category>
      <category>productivity</category>
    </item>
    <item>
      <title>🚀 Developer Tool Discovery: binsider</title>
      <dc:creator>Tushar Patil</dc:creator>
      <pubDate>Mon, 28 Sep 2026 15:36:03 +0000</pubDate>
      <link>https://dev.to/tusharpatil25/developer-tool-discovery-binsider-4ldi</link>
      <guid>https://dev.to/tusharpatil25/developer-tool-discovery-binsider-4ldi</guid>
      <description>

&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft1rp6jj5fgt9h9z74j5y.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft1rp6jj5fgt9h9z74j5y.png" alt=" " width="800" height="361"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Found an interesting tool for anyone working with &lt;strong&gt;Linux binaries&lt;/strong&gt;: &lt;strong&gt;binsider&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It’s a terminal UI for analyzing &lt;strong&gt;ELF binaries&lt;/strong&gt;, bringing several useful tasks into one place — binary structure, symbols, linked libraries, strings, hex data, and runtime tracing.&lt;/p&gt;

&lt;p&gt;🔍 &lt;strong&gt;Why I found it interesting:&lt;/strong&gt;&lt;br&gt;
• Combines multiple binary-analysis tasks in one terminal interface&lt;br&gt;
• Useful for debugging and understanding unfamiliar Linux binaries&lt;br&gt;
• Can provide useful build and environment metadata during investigation&lt;/p&gt;

&lt;p&gt;👨‍💻 &lt;strong&gt;Useful for:&lt;/strong&gt; Linux developers, DevOps/SRE, system administrators, security engineers, and anyone working with native binaries.&lt;/p&gt;

&lt;p&gt;🔗 &lt;strong&gt;Official:&lt;/strong&gt; &lt;a href="https://binsider.dev" rel="noopener noreferrer"&gt;https://binsider.dev&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💬 &lt;strong&gt;Have you used binsider before, or do you use different tools for ELF analysis?&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>linux</category>
      <category>cybersecurity</category>
      <category>devops</category>
      <category>softwaredevelopment</category>
    </item>
    <item>
      <title>🤖 One Prompt. Multiple AI Models. Different Perspectives.</title>
      <dc:creator>Tushar Patil</dc:creator>
      <pubDate>Sun, 27 Sep 2026 18:28:29 +0000</pubDate>
      <link>https://dev.to/tusharpatil25/one-prompt-multiple-ai-models-different-perspectives-2pj2</link>
      <guid>https://dev.to/tusharpatil25/one-prompt-multiple-ai-models-different-perspectives-2pj2</guid>
      <description>&lt;p&gt;Developers often switch between ChatGPT, Claude, Gemini, and other AI models to solve the same problem.&lt;/p&gt;

&lt;p&gt;I recently explored &lt;strong&gt;Multi (getmulti.ai)&lt;/strong&gt; — a tool that lets you send a prompt to multiple AI models and compare their responses in one place.&lt;/p&gt;

&lt;p&gt;💻 &lt;strong&gt;Useful for:&lt;/strong&gt;&lt;br&gt;
→ Debugging&lt;br&gt;
→ Code reviews&lt;br&gt;
→ Brainstorming&lt;br&gt;
→ Research&lt;br&gt;
→ Learning&lt;/p&gt;

&lt;p&gt;Instead of asking:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;“Which AI should I use?”&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Try asking:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;“How would different AI models solve this?”&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;🔗 &lt;a href="https://getmulti.ai/" rel="noopener noreferrer"&gt;https://getmulti.ai/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;One problem → Multiple perspectives → Better understanding.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>devlopercommunity</category>
      <category>aitools</category>
      <category>softwaredevelopment</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
