<?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: Hari</title>
    <description>The latest articles on DEV Community by Hari (@harish_e2092259238667e0da).</description>
    <link>https://dev.to/harish_e2092259238667e0da</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%2F3259476%2Fecfeb47b-9599-47e8-8914-d2aaf203265e.png</url>
      <title>DEV Community: Hari</title>
      <link>https://dev.to/harish_e2092259238667e0da</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/harish_e2092259238667e0da"/>
    <language>en</language>
    <item>
      <title>#Day 1 - Learning MCP</title>
      <dc:creator>Hari</dc:creator>
      <pubDate>Mon, 06 Apr 2026 03:06:02 +0000</pubDate>
      <link>https://dev.to/harish_e2092259238667e0da/day-1-learning-mcp-hfa</link>
      <guid>https://dev.to/harish_e2092259238667e0da/day-1-learning-mcp-hfa</guid>
      <description>&lt;p&gt;I recently started learning MCP (Model Context Protocol), introduced by Anthropic, and it gave me a clear view of how AI actually works with real systems.&lt;/p&gt;

&lt;p&gt;At a basic level, the flow is simple:&lt;br&gt;&lt;br&gt;
AI (inside a Host app) → MCP Client → MCP Server → Tools/Data.&lt;/p&gt;

&lt;p&gt;The client acts as a bridge, the server exposes tools, and the host is where AI lives. Instead of guessing, AI can now fetch real data and perform actions.&lt;/p&gt;

&lt;p&gt;It’s a small concept, but it opens the door to building real AI-powered systems.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>learning</category>
      <category>llm</category>
      <category>mcp</category>
    </item>
    <item>
      <title>MCP Server</title>
      <dc:creator>Hari</dc:creator>
      <pubDate>Thu, 02 Apr 2026 17:49:14 +0000</pubDate>
      <link>https://dev.to/harish_e2092259238667e0da/mcp-server-5167</link>
      <guid>https://dev.to/harish_e2092259238667e0da/mcp-server-5167</guid>
      <description>&lt;p&gt;Over the past few days, I’ve been diving deep into the Model Context Protocol (MCP), introduced by Anthropic, and it completely changed how I see AI systems.&lt;/p&gt;

&lt;p&gt;Earlier, I thought AI was just about prompts. But MCP showed me something bigger — AI becomes truly powerful when it connects with real-world tools, data, and systems. Instead of guessing answers, it can fetch live data, run actions, and behave like an intelligent assistant.&lt;/p&gt;

&lt;p&gt;What I learned is simple but powerful: AI is not just a brain, it needs hands. MCP gives those hands through tools and structured communication.&lt;/p&gt;

&lt;p&gt;In this AI era, MCP-like architectures will shape how we build copilots, agents, and smart workflows. It’s not about smarter models alone, but better integration.&lt;/p&gt;

&lt;p&gt;Going forward, I’m excited to build my own MCP servers and custom AI tools that solve real problems. This feels like the next step in becoming not just a developer, but an AI builder.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>learning</category>
      <category>mcp</category>
    </item>
    <item>
      <title>What I learned this month</title>
      <dc:creator>Hari</dc:creator>
      <pubDate>Tue, 31 Mar 2026 17:55:19 +0000</pubDate>
      <link>https://dev.to/harish_e2092259238667e0da/what-i-learned-this-month-1gi0</link>
      <guid>https://dev.to/harish_e2092259238667e0da/what-i-learned-this-month-1gi0</guid>
      <description>&lt;p&gt;Over the past month, I’ve been diving deep into Prompt Engineering, and it completely changed how I interact with AI.&lt;/p&gt;

&lt;p&gt;I learned that Prompt Engineering is not just asking questions—it’s about giving clear context, defining roles, setting constraints, and guiding the AI toward the exact outcome you need. The quality of output depends heavily on how well you structure your input.&lt;/p&gt;

&lt;p&gt;I explored techniques like breaking problems into steps, using examples, refining prompts iteratively, and thinking from the AI’s perspective. Small changes in wording can lead to big differences in results.&lt;/p&gt;

&lt;p&gt;My biggest takeaway: Prompt Engineering is a skill. The better you communicate, the smarter the AI becomes.&lt;/p&gt;

&lt;p&gt;Still learning, but excited about how this skill can improve productivity and problem-solving 🚀&lt;/p&gt;

</description>
      <category>ai</category>
      <category>promptengineering</category>
    </item>
  </channel>
</rss>
