Atharva Kumar

I started with Scratch — dragging blocks around until something moved on screen — and kept going because the loop of build it, break it, fix itnever got boring. That was a few years ago. Since then I've worked through plain HTML and JavaScript, browser games, Flutter and React Native apps, and now mostly AI tools and web products.

I'm 13. I mention it because it's context for the timeline, not because it's the point. The work is the point: whether the thing I shipped works, whether someone can use it, and whether I understood the problem well enough to solve it properly rather than just make the error go away.

How I work

In public, and in small pieces. I'd rather ship a narrow thing that works than plan a wide thing that doesn't exist yet. Most of what I build starts as a problem I hit myself — a recording I wanted clipped, a post I kept forgetting to schedule, a question I couldn't answer about how AI models talk about products.

I write about it on Substack and record some of it on YouTube. Not because every build deserves an audience, but because explaining something is the fastest way to find out whether I actually understand it.

What I'm learning now

How to take a project past the demo stage — reliability, edge cases, the unglamorous parts. Building something that works once is straightforward. Building something that works every time, for people who aren't me, is the actual skill.

Elsewhere

I'm on X, YouTube, Instagram, and Substack. The fastest way to reach me is email (learninwithak@gmail.com).