<?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>Forem: Komal Harshita</title>
    <description>The latest articles on Forem by Komal Harshita (@komal_harshita_018ba8ae14).</description>
    <link>https://forem.com/komal_harshita_018ba8ae14</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%2F3587558%2F0927130b-40b4-4c84-9b41-e1dadcfb055c.jpg</url>
      <title>Forem: Komal Harshita</title>
      <link>https://forem.com/komal_harshita_018ba8ae14</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/komal_harshita_018ba8ae14"/>
    <language>en</language>
    <item>
      <title>Deploying My Portfolio with Kuberns AI — Easier Than I Expected</title>
      <dc:creator>Komal Harshita</dc:creator>
      <pubDate>Mon, 02 Mar 2026 10:12:33 +0000</pubDate>
      <link>https://forem.com/komal_harshita_018ba8ae14/deploying-my-portfolio-with-kuberns-ai-easier-than-i-expected-4359</link>
      <guid>https://forem.com/komal_harshita_018ba8ae14/deploying-my-portfolio-with-kuberns-ai-easier-than-i-expected-4359</guid>
      <description>&lt;p&gt;I’ll be honest.&lt;/p&gt;

&lt;p&gt;Deploying projects is usually the part I delay the most.&lt;br&gt;
Not because I don’t finish building them — but because hosting, setup, and infrastructure always feel overwhelming.&lt;/p&gt;

&lt;p&gt;This time, I decided to try deploying my portfolio using Kuberns AI’s one-click deployment.&lt;/p&gt;

&lt;p&gt;And it was… surprisingly simple.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;My Portfolio Is Now Live&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Here’s the link:&lt;br&gt;
👉 &lt;a href="https://portfolio-main-73f0916.kuberns.cloud/" rel="noopener noreferrer"&gt;https://portfolio-main-73f0916.kuberns.cloud/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Seeing it live felt good — especially knowing I didn’t struggle with complicated configuration to get there.&lt;/p&gt;

&lt;p&gt;What the Process Looked Like&lt;/p&gt;

&lt;p&gt;It was basically:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Connect my code&lt;/li&gt;
&lt;li&gt;Click deploy&lt;/li&gt;
&lt;li&gt;Wait a few minutes&lt;/li&gt;
&lt;li&gt;Get a live URL&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No server setup.&lt;br&gt;
No manual infrastructure configuration.&lt;br&gt;
No confusing steps.&lt;/p&gt;

&lt;p&gt;For someone who’s still learning and not deeply into DevOps, that made a big difference.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Dashboard Experience&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The Kuberns dashboard was straightforward.&lt;br&gt;
I could clearly see:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Deployment status&lt;/li&gt;
&lt;li&gt;Resource usage&lt;/li&gt;
&lt;li&gt;My live URL&lt;/li&gt;
&lt;li&gt;Build history&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Everything was organized in one place, and I didn’t feel lost navigating it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How AI Helped&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;What stood out most was how smooth everything felt.&lt;/p&gt;

&lt;p&gt;Instead of worrying about technical setup, I could focus on improving my portfolio itself — refining content, fixing UI details, and making sure everything worked properly.&lt;/p&gt;

&lt;p&gt;The AI-driven deployment removed that “deployment fear” barrier.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why This Matters (At Least For Me)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As students and early developers, we build a lot.&lt;br&gt;
But we don’t always ship.&lt;/p&gt;

&lt;p&gt;Making deployment easier makes it more likely that we actually publish our work instead of leaving it on localhost.&lt;/p&gt;

&lt;p&gt;If you’re building projects and want a simpler way to go live, you can check it out here:&lt;br&gt;
👉 &lt;a href="https://kuberns.com" rel="noopener noreferrer"&gt;https://kuberns.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This experience reminded me that sometimes the hardest part isn’t coding — it’s putting your work out there.&lt;/p&gt;

&lt;p&gt;Now that my portfolio is live, I’m more motivated to keep building and keep shipping.&lt;/p&gt;

</description>
      <category>kuberns</category>
      <category>studentdeveloper</category>
      <category>aichallenge</category>
      <category>kubernschallenge</category>
    </item>
    <item>
      <title>From Prompts to Pipelines: What I Learned About Building Real AI Agents</title>
      <dc:creator>Komal Harshita</dc:creator>
      <pubDate>Thu, 04 Dec 2025 05:06:43 +0000</pubDate>
      <link>https://forem.com/komal_harshita_018ba8ae14/from-prompts-to-pipelines-what-i-learned-about-building-real-ai-agents-2b7i</link>
      <guid>https://forem.com/komal_harshita_018ba8ae14/from-prompts-to-pipelines-what-i-learned-about-building-real-ai-agents-2b7i</guid>
      <description>&lt;h2&gt;
  
  
  From Prompts to Pipelines: What I Learned About Building Real AI Agents
&lt;/h2&gt;

&lt;p&gt;When I joined the AI Agents Intensive, I thought “agents” were nothing but just smart chatbots. And by the end, I was building &lt;strong&gt;ProdigyFlow&lt;/strong&gt; — a full multi-agent pipeline that loads raw data, cleans it, analyzes it, creates charts, and finally produces an automated report.&lt;/p&gt;

&lt;p&gt;This course completely changed how I think about AI.&lt;/p&gt;

&lt;p&gt;The biggest shift for me was understanding that agents are not one big model — &lt;strong&gt;they’re a team&lt;/strong&gt;. Each agent has a job, its own tools, and a clear role in the pipeline.&lt;br&gt;
In ProdigyFlow, we built:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a &lt;strong&gt;Cleaning Agent&lt;/strong&gt; to fix messy data&lt;/li&gt;
&lt;li&gt;an &lt;strong&gt;Analysis Agent&lt;/strong&gt; to derive insights&lt;/li&gt;
&lt;li&gt;a &lt;strong&gt;Visualization Agent&lt;/strong&gt; to generate graphs&lt;/li&gt;
&lt;li&gt;and a &lt;strong&gt;Main File&lt;/strong&gt; to make them work together smoothly&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Seeing these parts collaborate felt like building a small company inside Python.&lt;/p&gt;

&lt;p&gt;There were a lot of behind-the-scenes struggles too:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;API keys broke so many times we memorized our &lt;code&gt;.env&lt;/code&gt; file 😭&lt;/li&gt;
&lt;li&gt;GitHub workflows failed at 2 AM for reasons we did not understand&lt;/li&gt;
&lt;li&gt;We learned how important logs, error handling, and reproducible runs really are&lt;/li&gt;
&lt;li&gt;Python libraries (Pandas, Matplotlib, tqdm) became our superpowers&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But every challenge made the final system more real.&lt;/p&gt;

&lt;p&gt;This project also became a true team win. My teammate &lt;strong&gt;Priyamvadha&lt;/strong&gt; and I figured things out together — fixing bugs, testing agents, and redesigning the pipeline more than once.&lt;/p&gt;

&lt;p&gt;Here are the project links if you want to explore:&lt;br&gt;
🔗 GitHub: &lt;a href="https://github.com/komalharshita/prodigyflow" rel="noopener noreferrer"&gt;https://github.com/komalharshita/prodigyflow&lt;/a&gt;&lt;br&gt;
🔗 Kaggle Submission: &lt;a href="https://www.kaggle.com/competitions/agents-intensive-capstone-project/writeups/ProdigyFlow" rel="noopener noreferrer"&gt;https://www.kaggle.com/competitions/agents-intensive-capstone-project/writeups/ProdigyFlow&lt;/a&gt;&lt;br&gt;
🔗 My LinkedIn: &lt;a href="https://www.linkedin.com/in/komalharshita/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/komalharshita/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Huge thanks to &lt;strong&gt;Google&lt;/strong&gt;, &lt;strong&gt;Kaggle&lt;/strong&gt;, and the mentors for creating this opportunity. I started this course writing simple prompts, and finished by building an end-to-end intelligent pipeline.&lt;/p&gt;

</description>
      <category>googleaichallenge</category>
      <category>ai</category>
      <category>agents</category>
      <category>devchallenge</category>
    </item>
  </channel>
</rss>
