<?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: Himanshi Kumari</title>
    <description>The latest articles on DEV Community by Himanshi Kumari (@himanshi_kumari_c878daee7).</description>
    <link>https://dev.to/himanshi_kumari_c878daee7</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%2F3868840%2Fbc6897b1-9aa5-4bd2-ad4f-53b221ed2487.png</url>
      <title>DEV Community: Himanshi Kumari</title>
      <link>https://dev.to/himanshi_kumari_c878daee7</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/himanshi_kumari_c878daee7"/>
    <language>en</language>
    <item>
      <title>From" Just Another Event" to " Wait...This Is Big" - My Yake on Google Cloud Next '26</title>
      <dc:creator>Himanshi Kumari</dc:creator>
      <pubDate>Fri, 24 Apr 2026 18:03:52 +0000</pubDate>
      <link>https://dev.to/himanshi_kumari_c878daee7/from-just-another-event-to-waitthis-is-big-my-yake-on-google-cloud-next-26-dbp</link>
      <guid>https://dev.to/himanshi_kumari_c878daee7/from-just-another-event-to-waitthis-is-big-my-yake-on-google-cloud-next-26-dbp</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/google-cloud-next-2026-04-22"&gt;Google Cloud NEXT Writing Challenge&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;🌐 Introduction&lt;br&gt;
I was reading about Google Cloud Next '26, and one thing that really stood out to me was how everyone kept talking about the “Agentic Era.”&lt;br&gt;
At first, I didn’t think much of it, but then it clicked — AI isn’t just something we use anymore, it’s starting to act on its own. It can take initiative, handle tasks, and reduce the amount of back-and-forth we usually do. That shift feels subtle, but it’s actually huge.&lt;/p&gt;

&lt;p&gt;💻 Gemini for Coding&lt;br&gt;
When I read about Gemini in coding, it felt very relatable.&lt;br&gt;
It’s not just about generating random code snippets — it actually helps you think through problems. Like, if you’re stuck on a bug or confused about logic, it can break things down in a simple way.&lt;br&gt;
It almost feels like having someone sitting beside you while coding, helping you move forward instead of staying stuck for hours.&lt;/p&gt;

&lt;p&gt;📄 Gemini for Workspace&lt;br&gt;
What I found interesting is how Gemini is not limited to developers. It’s already part of tools like Gmail and Google Docs.&lt;br&gt;
So even in daily tasks — writing emails, summarizing long notes, or even rewriting something better — it just makes things smoother.&lt;br&gt;
It’s not something loud or flashy, but it quietly saves time and effort, which honestly matters more.&lt;/p&gt;

&lt;p&gt;🧠 Gemini for Building AI&lt;br&gt;
Another part that caught my attention was how developers can actually build their own AI tools using Gemini.&lt;br&gt;
Earlier, creating something like this felt complicated and out of reach. But now, it feels more accessible. You can experiment, try ideas, and build something useful without needing to be an expert from day one.&lt;br&gt;
That’s what makes it exciting — it opens the door for more people to create.&lt;/p&gt;

&lt;p&gt;🚀 Conclusion&lt;br&gt;
By the end of it, I didn’t feel like I was reading about some far-away future.&lt;br&gt;
It felt like things are already changing, just quietly.&lt;br&gt;
And honestly, that’s what makes it interesting — AI isn’t just getting smarter, it’s becoming more useful in everyday life.&lt;br&gt;
If this is what the “Agentic Era” looks like, then it feels like we’re just getting started.&lt;/p&gt;

&lt;h1&gt;
  
  
  Googlecloud #ai #gemini# webdev #productivity
&lt;/h1&gt;

</description>
      <category>devchallenge</category>
      <category>cloudnextchallenge</category>
      <category>googlecloud</category>
    </item>
    <item>
      <title>CSS Horror Story</title>
      <dc:creator>Himanshi Kumari</dc:creator>
      <pubDate>Sun, 12 Apr 2026 18:30:52 +0000</pubDate>
      <link>https://dev.to/himanshi_kumari_c878daee7/css-horror-story-5akf</link>
      <guid>https://dev.to/himanshi_kumari_c878daee7/css-horror-story-5akf</guid>
      <description>&lt;h2&gt;
  
  
  &lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/aprilfools-2026"&gt;DEV April Fools Challenge&lt;/a&gt;&lt;/em&gt;
&lt;/h2&gt;

&lt;h1&gt;
  
  
  I Built an AI That Turns CSS Bugs Into Horror Stories 👻
&lt;/h1&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;For this challenge, I created &lt;strong&gt;CSS Horror Story Generator&lt;/strong&gt; — a completely unnecessary but emotionally important app that transforms cursed frontend bugs into dramatic horror stories.&lt;/p&gt;

&lt;p&gt;It’s based on one of the most universal developer experiences:&lt;/p&gt;

&lt;p&gt;You deploy your project.&lt;br&gt;
Everything works perfectly.&lt;br&gt;
Then someone says:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“The layout is broken on mobile.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;You inspect the page…&lt;/p&gt;

&lt;p&gt;…and the bug disappears.&lt;/p&gt;

&lt;p&gt;At that point, you’re no longer debugging.&lt;br&gt;
You’re performing an exorcism.&lt;/p&gt;

&lt;p&gt;This app lets users generate ridiculous horror stories inspired by frontend nightmares like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Bugs that only exist in production&lt;/li&gt;
&lt;li&gt;Layouts breaking for no visible reason&lt;/li&gt;
&lt;li&gt;Infinite &lt;code&gt;z-index&lt;/code&gt; wars&lt;/li&gt;
&lt;li&gt;Random legacy CSS from 2017&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;position: absolute&lt;/code&gt; used in places it should never be&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Think of it as a trauma journal for frontend developers.&lt;/p&gt;




&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;👉 &lt;strong&gt;GitHub Repo:&lt;/strong&gt; [&lt;a href="https://github.com/himanshi022356/CCS-horror-story" rel="noopener noreferrer"&gt;https://github.com/himanshi022356/CCS-horror-story&lt;/a&gt;]&lt;/p&gt;




&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;I built the project using:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;HTML/CSS/JavaScript&lt;/strong&gt; for the frontend&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI Prompt Engineering&lt;/strong&gt; to generate the horror stories&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An LLM API&lt;/strong&gt; to turn cursed prompts into cursed literature&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Core Prompt Used
&lt;/h3&gt;



&lt;p&gt;```txt id="x3m92"&lt;br&gt;
Tell a horror story where the monster is a CSS bug that only appears in production and vanishes when inspected.&lt;br&gt;
Make it funny, dramatic, and relatable for frontend developers.&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;


The AI then generates absurd frontend horror content based on that idea.

---

## Prize Category

**Best Google AI Usage**

Because I firmly believe AI’s highest purpose is not solving humanity’s greatest challenges—

It is generating fictional trauma for frontend developers.

---

## Final Note

This project may not improve productivity.
It may not change the world.
It may not even help anyone.

But it *will* make developers laugh while they cry over CSS.

And honestly, that’s enough.

&amp;gt; If the bug disappears when you inspect it…
&amp;gt; it knows you’re watching.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>devchallenge</category>
      <category>418challenge</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
