No computer at home. No coaching centre. No course.

Just curiosity, a search bar, and eight years of trying things until they worked.

Before any of this was possible

I didn't grow up knowing I'd build websites for a living.

Whatever I know now, I picked up on my own. Curiosity. YouTube. Google. Documentation. A lot of trial and error.

Before that, I did whatever work was available.

I sold vegetables. Worked at a dairy. Then as a technician, a fitter, a helper. I've handled water tanks, mixed cement, spent a stretch in a perfume factory.

I sold pakodas and chole kulche and roasted chana from a cart. Worked a grocery counter, then a pan shop. Looked after goats and buffaloes, cut grass for them, did farm work when there was farm work to do.

None of it looks like a straight line to where I am now.

But it taught me the one thing that actually matters: keep working, keep learning, and something eventually gives.

An education that kept starting over

School never ran on one track for me.

Government school, then private, then back to government — through class 8. Years later, a chance to join a private school for class 9. I attended a few days. Then the lockdown shut everything down.

I passed class 10 in the middle of that disruption. That was basically the end of my formal education.

No stack of degrees. No computer certificates. Almost everything I actually use came from somewhere else entirely.

How it actually started

It began with something small: watching someone in my village use a computer.

I had no idea what they were doing. I just knew I wanted to know.

That curiosity stuck around longer than I expected. No teacher, no structured path — just me, YouTube, and Google.

If I wanted to understand something, I searched for it. If something looked interesting, I tried it. When it broke — often — I searched again and fixed it.

That loop became my entire education. Honestly, it still is.

The blog that didn't pay off — at first

I started blogging in 2017.

Like a lot of people starting out, I figured a live website would eventually mean money. It didn't. Not for a long while.

Traffic stayed low. Low traffic meant AdSense had nothing to pay me for.

So instead of walking away, I looked for other ways to make the sites I was already building actually useful — to someone, even if not to me yet.

What I learned from selling websites

One of those other ways became a business of its own: building and selling AdSense-approved websites.

Over the years, I've sold more than 200 of them.

It taught me, hands-on, what it actually takes to get a site approved — clean structure, real content, the small technical details reviewers check for.

But selling sites was never the plan I wanted to stay on. I didn't want a career spent building things just to hand them off. I wanted to build something I'd keep.

The first real payment

Eventually, AdSense started paying out on my own sites — not the ones built to flip.

That was a real turning point. The thing I'd spent years trying to understand — how a website actually earns money — had finally clicked.

From there, it widened. Other ad networks. Sponsorships. Different mixes for different sites.

There isn't one way to make a website pay. Advertising, sponsorships, selling sites outright — all of it can be part of the same journey, just at different points.

Building something that would last

As I got more confident, I started putting real time into projects of my own. Not sites built to sell — ones meant to grow.

The biggest is MemesTube. I built it from nothing and have kept building on it ever since.

It stopped being "just meme pages" a long time ago. Search, recommendations, APIs, SEO, performance, content systems, automation — the whole stack, learned by needing each piece.

Different projects, different lessons

I also run QuickAtHome, a local home-services site, plus a handful of smaller projects and experiments.

I like keeping a few different things going. Each one breaks in its own way.

One teaches me something about SEO. Another forces a better database design. Another needs automation, or a completely different way of thinking about the user's experience.

Working across projects, rather than staying inside one, is how most of what I know actually stuck.

Learning by needing to, not by being taught

I never took a course in PHP, databases, or APIs. I learned each one because a project demanded it.

A feature was missing — so I learned to build it.

Something ran slow — so I learned why.

Search didn't work — so I learned search.

Two systems needed to talk — so I learned APIs.

It's a slow way to learn. But almost everything I picked up was tied to a real problem I actually had — not a lesson sitting in a syllabus, waiting to be useful someday.

Then SEO became half the job

Building a site is one problem. Getting anyone to find it is a different one entirely.

Over time I picked up search intent, content strategy, internal linking, technical SEO, backlinks, site structure, performance — the whole picture of how search engines actually read a website.

SEO isn't something you learn once and file away. Search changes. Sites change. What works on one project quietly stops working on the next.

Most of what I know here came from watching my own sites, and paying attention to what actually happened — not what was supposed to happen.

Where automation and AI fit in

As the projects grew, so did the repetitive parts of running them. That pushed me toward automation and AI.

I've built agents that run on a schedule and handle pieces of the workflow on their own — pulling from content sources, processing new material, preparing it for different sites and languages, without me starting it by hand every time.

I use automation and AI across my work, MemesTube included, though I keep the private implementation details to myself.

What interests me isn't AI as a chatbot. It's AI doing real, useful work quietly in the background.

Still learning, still building

Eight-plus years in, and I still think of myself as someone learning, not someone who's arrived.

There's always another technology to understand. Another problem worth solving. Another old system that could be better.

The method hasn't changed since the beginning: search, read, try, break it, fix it, try again.

Where I am now

Today I work as an independent web builder, developer, and blogger. Building and running sites. Working on SEO and monetization. Making tools. Experimenting with AI and automation. Still starting new projects of my own.

The path from selling vegetables and cutting grass for buffaloes to running search infrastructure for my own products was never straight, and it was never planned.

It went through a blog in 2017. Two hundred websites sold to strangers. And finally, a handful built to keep.

I didn't have a traditional way into technology. So I built my own — one problem, one search, one fix at a time.

And I'm still building.