DEV Community: Jyotish Pabbisetti

The Ten Days I Wasted My AI Usage Limits (And What I Learned After)

Jyotish Pabbisetti — Thu, 06 Aug 2026 16:33:07 +0000

For almost four months, I did nothing but dream. I would think up a product, imagine how it would work, picture it finished — and never write a single line of code. In my head, building it was the easy part. I had ChatGPT and Claude. How hard could it be?

Then summer break came. May 2026. And one thought kept hitting me: I had spent four months thinking about products and zero months building them.

So I decided to actually start.

The naive part

People had already warned me — learn the basics first, don't skip the fundamentals. I nodded along, but I didn't really believe that was the real problem. I still thought AI was some kind of magician. Explain the idea, get the code, done. One idea, one solution, no friction.

Here's how naive I actually was: I would describe my idea to ChatGPT, ask it for a plan and a prompt, then copy that prompt straight into my IDE — without reading what the prompt actually told the AI to do. I just trusted it.

The output, unsurprisingly, was often the opposite of what I wanted. I burned through my usage limits chasing fixes for problems I had created myself, just by not reading my own prompts.

The part nobody warns you about

The real barrier was never syntax or libraries. It was the gap between having an idea in your head and actually turning it into something real. That gap doesn't show up in any tutorial. You only find it by trying to cross it — and falling in.

What changed

The first ten days were pure confusion. But somewhere after that, things started clicking. I learned actual prompt engineering — not just "ask nicely," but understanding what a prompt does before I run it. I got a real feel for what AI is actually good at, and where it quietly hands you garbage dressed up as an answer.

Oddly, this made me a better programmer, not a lazier one. Reading and correcting AI output forced me to understand code faster than writing it alone ever did. I started filling the gaps AI left with my own thinking, instead of just more prompts.

It also made me more consistent — not just in coding, but in how I studied and how I showed up to work every day.

The one thing I'd tell myself in May

None of this — the prompt engineering, the sharper code sense, the consistency — happens if I don't take that first messy, confused step. The confusion wasn't a sign I was doing it wrong. It was the cost of finally doing it at all.

Rivalry Roast — you talk smack about your team or favorite player, out loud, and an AI rival fan claps back at you, in voice, in real time.

Jyotish Pabbisetti — Mon, 13 Jul 2026 02:26:21 +0000

This is a submission for Weekend Challenge: Passion Edition

What I Built

Tomorrow I have my semester exam. Between assignments, revision, and general exam-season chaos, my schedule right now is not exactly forgiving. And yet — every day, no matter how packed things get, I carve out an hour, sometimes an hour and a half, just to build. Not because I have to. Because it's the one part of my day that actually feels like mine.

So when this challenge landed during exam week, it felt less like bad timing and more like an invitation. I'm a solo developer on this one, and I'm also a lifelong football fan — Ronaldo has been my guy for as long as I can remember. Building something around fan passion and rivalry wasn't a stretch for me; it's basically autobiographical.

The goal was simple: talk smack, get roasted back — out loud, not just in text.

Demo

Youtube demo link(https://youtube.com/shorts/QNnVdpfzGNE?si=GFmKuYos3FgXRtx4)

https://dev-uq5k.onrender.com

Code

https://github.com/Jyotish08/dev

How I Built It

The flow is simple to describe but has three real moving parts: you speak your trash talk, it gets converted to text, that text goes to an AI for a witty comeback, and the comeback gets converted back into voice so you actually hear the rival roast you.

I used Groq for speech-to-text, Google Gemini for generating the roast itself, and ElevenLabs for turning that roast into voice.

The voice piece was the part I was most excited about, and it wasn't totally unfamiliar territory — I've built voice cloning from scratch before, using open-source models, piecing together my own pipeline to get a voice to sound right. This was my first time using ElevenLabs specifically, and it was humbling: what used to take real pipeline-building effort on my end, it handled almost instantly once I found my footing with it.

Gemini impressed me just as much on the other side — fast turnaround, and it consistently understood the tone I was going for without me needing to over-engineer the prompt.

The part nobody tells you about: building the idea took maybe twenty minutes of thinking. Getting it working took closer to two hours, and almost all of that time went into APIs that had quietly moved on without telling me. A model I called by name had already been retired. A voice model I picked had been phased out on the free tier. The specific voice I wanted wasn't available to my account at all due to a free-tier restriction I didn't know existed. Deployment brought its own round of small chaos — a build tool throwing a permission error, a config silently skipping a dependency it needed, a server going live but unable to find its own front end.

None of these were dramatic bugs individually — each took a couple of minutes to fix once I knew what it was. But stacked back-to-back, on exam eve, with the clock ticking, it turned into a genuine debugging crawl through error messages and dashboards. And honestly, that's passion too — not just the fun highlight-reel part, but the part where something keeps refusing to work and you keep showing up anyway because you already care too much to walk away.

Prize Categories

Best Use of Google AI, Best Use of ElevenLabs

Building Confidence out of Chaos: How Copilot Saved My First AI Project

Jyotish Pabbisetti — Sun, 07 Jun 2026 06:04:10 +0000

This is a submission for the GitHub Finish-Up-A-Thon Challenge

What I Built
I built Local PDF, a completely local, privacy-first utility website designed to handle all your PDF processing needs right in the browser. The idea started because I wanted a fast, reliable tool that didn't force users to upload their sensitive documents to the cloud. As I navigate my first year of computer science, what makes this project so meaningful to me is that it was my true gateway into advanced, real-world development. It wasn't just another assignment; it was something I built from scratch to solve a real problem.

Demo:

Localpdf — Your PDFs. Done in Seconds. Right in Your Browser.

Free online PDF tools that work entirely in your browser. Compress, merge, and split PDFs instantly with no uploads, no registration, and no data stored.

localpdf.dev

The Comeback Story
When I first started this project, my workflow was a complete mess. It was entirely disconnected. At one crucial point, the app was lagging horribly, the components were breaking, and I couldn't figure out why. I sat there for 45 incredibly frustrating minutes, just staring at my screen, trying to trace the errors by myself.

It was my very first time experimenting with AI agents in a development environment, and the complexity felt overwhelming. Honestly, I was completely drained. I was so close to just shutting my laptop, throwing my hands up, and postponing the whole thing for "tomorrow"—which, let's be real, often means abandoning it entirely. The barrier felt too high.

But instead of giving up, I decided to try a different approach. I stepped back, engineered a clear prompt to gather my thoughts using ChatGPT, and then I turned to the auto model selection feature in GitHub Copilot right inside VS Code.

My Experience with GitHub Copilot
That decision completely turned the project around. I asked Copilot to analyze the repository, and within just a few minutes, it handed me a comprehensive report detailing exactly where the bottlenecks were and why the app was breaking. I was absolutely blown away by how it handled the chaos of my code. I applied the changes it suggested, and it worked flawlessly.

If Copilot hadn't helped me in that exact moment, that bug would have been the end of the road for Local PDF. But more importantly, solving that problem gave me an incredible surge of confidence. It made me realize that I can build complex, ambitious things. Since that night, I've gone on to build multiple other projects, and I haven't felt those negative emotions or the heavy weight of imposter syndrome while coding ever again. Copilot didn't just fix my code; it changed how I feel about being a developer.