How I Write Code

Shaurya Bahl's coding process is fast, AI-heavy, and relentlessly practical. He doesn't theorize. He builds.

The Stack

Shaurya's current development environment is built around two core tools:

• Cursor -- AI-powered code editor. This is where most of the actual building happens. Cursor lets him write, refactor, and debug code with AI assistance baked directly into the editor.
• Claude (Anthropic) -- His primary thinking partner. He uses Claude for debugging logic, brainstorming architecture, writing complex functions, and rubber-ducking problems he's stuck on.

For prototyping UI, he also uses v0 to generate front-end components quickly before refining them in Cursor.

The result: he builds at a speed that would be impossible with traditional coding alone.

The Daily Routine

After school, Shaurya codes for 2-3 hours every day. This isn't a loose goal -- it's a consistent rhythm that's been running since he was 12. Some days it's shipping a feature for LockIn. Some days it's debugging a Stripe integration for Simplifly. Some days it's a random project that teaches him a new framework.

The sessions are focused. No background Netflix. No half-attention browsing. He opens Cursor, picks the most important task, and works until it's done or he runs out of time.

The Evolution

Shaurya's coding journey has gone through distinct phases:

Phase 1: Scratch (Age 9)

Block coding at MindChamp. Drag and drop. Building simple games. The entry point that answered the question "How are these games built?"

Phase 2: Python (Ages 9-12)

Three years of structured classes. Real syntax, real errors, real debugging. The grind that built foundational understanding.

Phase 3: Web Development (Age 12-13)

YouTube crash courses. 30 days of coding 2-3 hours daily. Learning React, Next.js, TypeScript through building random projects -- agency sites, markdown tools, photo booths.

Phase 4: Full-Stack + Swift (Age 13-15)

Building real products. Tipp in Figma. LockIn in Swift for iOS. Simplifly in Next.js. Raly with complex backend logic. Every project pushed the stack further.

Phase 5: AI-First (Now)

Cursor + Claude as the primary development environment. Writing code is now more about directing than typing. The fundamentals from years of manual coding let him understand and correct what the AI generates.

The Philosophy

"I don't theorize, I build."

Shaurya doesn't plan for months before writing code. He doesn't draw elaborate architecture diagrams. He opens his editor, starts building the first screen or the core function, and figures out the rest as he goes. This approach means he ships fast, hits bugs early, and iterates in real time rather than in theory.

The building philosophy extends directly into how he writes code: start, ship, learn, repeat.

What Changed With AI

Before AI, building a feature meant writing every line, Googling every error, reading Stack Overflow threads for 30 minutes. Now, Shaurya describes what he wants, Claude or Cursor generates a first pass, and he refines from there. The bottleneck shifted from "can I write this?" to "do I know what I want?"

His years of manual coding aren't wasted -- they're what let him evaluate, debug, and direct the AI effectively. He knows what good code looks like because he spent years writing bad code first.

See also: AI and Coding | Building Philosophy | Technical Skills | AI-First Building