<?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: Anushka Singh</title>
    <description>The latest articles on DEV Community by Anushka Singh (@anushka_singh09).</description>
    <link>https://dev.to/anushka_singh09</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%2F3651595%2Fec9c8945-8078-4c67-9705-e16b0bcae11b.png</url>
      <title>DEV Community: Anushka Singh</title>
      <link>https://dev.to/anushka_singh09</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/anushka_singh09"/>
    <language>en</language>
    <item>
      <title>Glimpses of Agentic AI practises</title>
      <dc:creator>Anushka Singh</dc:creator>
      <pubDate>Wed, 14 Jan 2026 18:28:51 +0000</pubDate>
      <link>https://dev.to/anushka_singh09/glimpses-of-agentic-ai-practises-1dg9</link>
      <guid>https://dev.to/anushka_singh09/glimpses-of-agentic-ai-practises-1dg9</guid>
      <description>&lt;p&gt;In continuation of my Agentic AI learning &lt;em&gt;I got to make a project&lt;/em&gt; &lt;strong&gt;complaint-triage-system&lt;/strong&gt; by incorporating process automation with the help of LLM API. For database I used Sqlalchemy and when admin intends to check the lodged complaints on separate dashboard, they have to authenticate with their email and password secured by JWT token. It took me so long because first I used Gemini API key and at last I had to revoke because some glitch happened to be there (as usual). Oh I completely forgot to write that why did I use API key because it was helping me to triage the complaint status to high/medium/low and it was responsible for analysis of complaint submitted but the twist came when I wished to create the email send reply button by admin side along with regenerate and  edit button.&lt;/p&gt;

&lt;p&gt;I don't know how but my gemini key crashed, I rushed into changing the models but it didn't work. I switched to grok API because it was free, triage was working correctly and the analysis was a bit short (very specific in keywords).In between all of this It was all pain to use JWT based tokenization , I had to cancel otp based authentication when entering email, the otp was appearing to me in my backend server. I got so confused, my biggest red flag was lack of system design or clear workflow, and I mean it you not only need mere inspiration,but also clarity in your aim...&lt;/p&gt;

&lt;p&gt;LET'S Get back to the topic so i just made a create_admin file and added my email, password in the env. After this, everything was working fine and I finally wanted AI-generated customized editable reply to be sent to the user.. I used APP password of one of my email ids but again it didn't work out. What came as my saviour &lt;em&gt;&lt;strong&gt;Twilio Sendgrid&lt;/strong&gt;&lt;/em&gt;. Sendgrid API key and my application was working without bugs, I edited my reply to add some human touch and specific details to the email however the edited reply was not going to the payload.. I debugged one last time and magic it is running smoothly.&lt;/p&gt;

&lt;p&gt;Deploying is another pain and I tried on AWS Elastic Beanstalk but that http and https mismatch because I was using AWS amplify(using https), I turned to EC2 and tried installing nginx but the timeout in free tier and repeated commands exhausted me...This is how my full-stack application came into the life and the github commits&amp;gt; 11 has other memebase.&lt;br&gt;
Today My aws free tier expired and I have multiple quests to create many projects, to contribute.&lt;br&gt;
P.S. I intend AI to routing the complaint to specific department as per the user needs for faster  issue resolving as my project grows &lt;/p&gt;

</description>
      <category>ai</category>
      <category>vue</category>
      <category>vite</category>
      <category>python</category>
    </item>
    <item>
      <title>Whitepapers, Labs and loads of learning</title>
      <dc:creator>Anushka Singh</dc:creator>
      <pubDate>Mon, 08 Dec 2025 18:47:25 +0000</pubDate>
      <link>https://dev.to/anushka_singh09/whitepapers-labs-and-loads-of-learning-1638</link>
      <guid>https://dev.to/anushka_singh09/whitepapers-labs-and-loads-of-learning-1638</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/googlekagglechallenge"&gt;Google AI Agents Writing Challenge&lt;/a&gt;: Learning Reflections&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Agentic AI is the evolution of automation which is agile in adaptive &lt;br&gt;
decision making.&lt;/p&gt;

&lt;h3&gt;
  
  
  Fellas ! It was truly an amazing event packed with practical implementation
&lt;/h3&gt;

&lt;p&gt;I started with &lt;a href="https://drive.google.com/file/d/1FM7NK-E2O8CTl_pNVTagxBHuQ0CB2dYc/view?usp=drive_link" rel="noopener noreferrer"&gt;Building your first Agent&lt;/a&gt;, it was quite fun and accomplishing to record the working of an agent. The learning is based on utilising ADK and Gemini for API keys and compatible model. As I geared up on day 1, I got to know the very basics of what is Agentic AI and the method it invokes to work with, then the types of agents and clear workflows of architecture in multi-agent systems.&lt;/p&gt;

&lt;p&gt;I caught up with &lt;em&gt;Interoperability with MCP and tools&lt;/em&gt; to get to know the deeper side of orchestration behind an agent's success. The best part was that you can connect the documents to the NotebookLM and learn the core concepts a way much better. They even provided the summary podcast created by NotebookLM.&lt;/p&gt;

&lt;p&gt;I was able to call get tiny image tool from MCP server to test on my local host and it worked. Furthermore I wanted the output of image of an anime girl when asked from the agent just to work with different MCP server, let alone Replicate MCP server. There was a glitch and I moved on to day 3, however on day 2, I worked with agent with approval and definitely wouldn't have missed.&lt;br&gt;
Day 3 and the dawn of context engineering &lt;em&gt;Sessions and Memory&lt;/em&gt; one of my favourite topics, I put pen to paper and dived into how to make the agent stateful and the labs were my only resources cut to the chase for any beginner and I am glad everything was so smooth while I learned.&lt;/p&gt;

&lt;p&gt;Day 4 was the addition to Responsible AI and if the agent is capable to solve problem Should it actually do or not, they must be evaluated too.&lt;br&gt;
From Glassbox and Blackbox evaluations to pillars of observability. There was proper guidance depending on the roles of any professional.&lt;/p&gt;

&lt;p&gt;While Day 5 was all about &lt;em&gt;Prototype to Production&lt;/em&gt; , Deploying the agent.&lt;br&gt;
On a good note, I would say the event was more than worthwhile&lt;br&gt;
The curated playbooks and the steps to develop the agents on &lt;em&gt;kaggle&lt;/em&gt; is the foundation to my next move which is developing Agentic AI project end to end.&lt;/p&gt;

&lt;p&gt;Thank you for the day&lt;/p&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%2Fds504f05q8g9fph50hs7.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%2Fds504f05q8g9fph50hs7.png" alt="Thank you for the day" width="393" height="344"&gt;&lt;/a&gt;&lt;/p&gt;

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