Chapter I · The beginning

It started with a laptop, a curious kid, that's me!and a few lines of code. 

I got my first laptop in class 11. Programming started as curiosity — “What can I make this thing do?”

That question never really went away.

Since then, I’ve spent countless hours building software, breaking things, fixing them, starting side projects, abandoning half of them, and occasionally shipping something I’m proud of.

I still program for the same reason I started: I love making things.

the story begins below

Chapter II · The journey

Every story needs a road.

Mine started with a laptop, took a few unexpected detours, and somehow turned into a career in building software.

  1. 2019

    The compiler wins, repeatedly.

    Class 11 · Where it all began

    My dad got me a Lenovo laptop, and I picked Computer Science in class 11. C++ was my first language.

    I didn’t really know what I was doing. I just liked making the computer do things.

    Then came HTML, Bootstrap, Python, and a growing curiosity about how the websites and tools I used every day actually worked.

    First laptop ( Lenovo )

  2. 2020

    Tried everything. Came back to code.

    JEE was over · Too much free time

    After JEE, I suddenly had a lot of free time — so naturally, I tried to become a music producer, 3D artist, animator, and designer.

    Turns out, none of them clicked quite like programming did.

    So I went back to code.

    First phone ( Vivo )

  3. 2022

    Teaching DSA was a sneaky way to learn DSA.

    Coding Ninjas · Teaching Assistant

    I joined Coding Ninjas as a Teaching Assistant and started helping students with their DSA doubts. Explaining an algorithm to someone who absolutely did not understand it is a surprisingly effective way to discover whether you actually understand it.

    My DSA got better. My communication got better. And I learned that teaching is basically debugging, but with humans.

    And somewhere around the end of the year, my mom got me a MacBook Air. That laptop became a pretty important companion for what came next.

    MacBook Air ( Mom’s gift )

  4. 2023

    Started by fixing bugs.

    Glood.AI · Software Engineering Intern

    I joined Glood.AI as an intern and got my first real taste of professional software engineering. I started out fixing bugs and working on smaller tasks.

    By the end of the internship, I’d learned a ridiculous amount — not just about writing code, but about shipping it, maintaining it, and dealing with the things that inevitably break after you ship them.

    This was the beginning of my career.

  5. 2024

    Internship upgraded to full-time.

    Glood.AI · Software Development Engineer

    A few days after my final semester exams, I joined Glood.AI full-time as an SDE.

    Somewhere between building features, debugging production at questionable hours, and figuring out what not to build, I became a much better engineer.

    And with my first salary and bonuses, I bought something I’d wanted for a while: a MacBook Pro. Not a gift this time. I bought it myself.

    MacBook Pro ( salary + bonuses )

  6. 2025

    Apparently, I finally joined the club.

    First iPhone

    I’ve built and shipped a bunch of things for e-commerce — including AI Search & Discovery, Inventory Planner, and an AI Photo & Video Studio for Shopify merchants.

    And after years of Android phones, I finally bought my first iPhone.

    No profound career lesson here. I just wanted one. 😅

    iPhone 16 ( first iPhone )

  7. 2026

    Still hasn’t stopped opening the editor.

    Still building

    These days, I’m working on an AI platform for e-commerce. I can’t tell you much about it yet. Sorry. The story has a few spoilers. 🤫

    But outside of work, the side quests continue too. And in September 2026, I bought myself another thing I’d wanted for a while: a bike. 🏍️

    New bike ( Sep 2026 )

To be continued…

Chapter III · Things built along the way

Some ideas made it out alive.

Pressed and framed like botanical specimens — the projects that survived contact with production.

Chapter IV · The graveyard of sleeping ideas

Not every idea survives the night.

These rest here, fondly remembered. Hover — or tap — a stone and its ghost will tell you what really happened.

  • AI narration for any digital book — a lovely idea with brutal unit economics. The free tier listened generously; paying customers never arrived. The GPU invoices did.
  • A RAG-powered chatbot any website could embed to resolve customer queries. It grew from a weekend hack into a real product — but traction never grew with it.
  • The idea: tell Claude Code or Codex “deploy this,” and it just… deploys. Paused when life asked for attention elsewhere. Of everyone here, the most likely to wake up.