PN
Prashanta NayakAI Product Builder
Back to Blog

More About Me

2026-04-01

#journal#personal#product#mindset

tldr; small-town kid, very online, dropped out of IIT Madras. The real syllabus was whatever rabbit hole was open that week: Bubble docs at 2am, Flutter screens, EV dashboards, LLM SQL hacks, ML papers, Premiere timelines, the occasional standup set.

The longer version: I dropped out with no backup plan, and the next few years were mostly me finding out what I didn't want to do.

Design was first. Didn't take. I'd been editing videos for fun for years, so I put a portfolio on Twitter and got offers from MotorOctane, Finance with Sharan and ThinkSchool, channels I used to watch, not pitch to.

Then one of the biggest YouTube creators in India offered me a full-time editor job. I could cut a good video. I'd also already gone cold on the process, so I said no. I tried running a design and media agency after that, mostly because it looked like the obvious next step. Turns out I was bad at managing people, or at least I was then.

So I swung the other way: an Electrical Engineering role at L&T Construction, highest package in my diploma college batch, at nineteen. I left within a month. Corporate life at nineteen felt like the fastest way to kill whatever curiosity I had, and I couldn't picture doing it long term.

Hardware was next. Courses, a portable body cooler, a payment tracker. None of it went anywhere. Then Foodaspas, a social app for foodies, six months of work before I admitted it was never going to ship to real users. Yeh sab gile sikwe leke mai nikla safar pe.

So I travelled. Mountains, cities, villages, less of India than I'd planned and more than I'd seen before. Somewhere in there I got into no-code because it let me ship fast, worked alongside people like Aditya Pati who were pushing India's no-code community forward, and ended up consulting on low-code EV operations for Driveo, which went well for a few months. Then Jagruti Yatra: fifteen days on a train across India, sitting with entrepreneurs in person instead of reading their case studies on a screen.

The one line I kept from all of it: coding doesn't make money, solutions do.

I picked tech because I have too many interests for one lane: biology, physiology, evolution, nutrition, medicine, sports, media, strength training, flying, space. Tech is the one base that holds all of them without making me choose. Could be commitment issues. I'm calling it a strategy.

Somethings I believe in

  • Clarity shows up after you start, and checking in before every step just makes you a headache for whoever's paying you to act.

  • Your first attempt is supposed to suck, the second one is the point.

  • Do not confuse motion with direction: execute, check the feedback, adjust, and only then go faster.

  • Iteration x consistency compounds. Neither one does much alone.

  • If you can control it, it's a skill issue, and if you can't, stop spending energy complaining about it.

  • A dopamine source that doesn't build anything is a leak, not a habit.

  • Polished decks, fake plans, research tabs and premium UI kits are usually just fear with better fonts.

  • No live URL means it's still an idea, and a live URL with no users means ship harder.

  • I've hired for senior roles, and a GitHub link with no live demo gets skipped, because nobody is cloning your repo to find out if it works.

  • Genuine beats rehearsed, since people clock the performance long before they're impressed by it.

  • Break it in public over polishing it in private, which is rich coming from me, with months of documentary footage still sitting unposted in my gallery.

  • Working software and a conversation beat a deck and a roadmap: two weekends after quitting my last job, I pitched two rough micro-SaaS builds to people I'd already worked with, and they asked for changes and started paying.

  • Code and media keep working after you stop touching them, which is why one of those weekend builds still makes money even though I haven't touched it in weeks.

  • Someone has probably hit your problem already, so read before you reinvent.

  • Treat the people and feeds you let near you like a decision, not an accident.

  • Do not confuse urgency with burnout: one gets things shipped, the other gets you benched.

  • I'll keep shipping rough tools and weird bots until more people pay me to ship theirs faster.

"nothing helps; i must help myself, or i am finished" - Friedrich Nietzsche

Email ID is Copied