Hello, world

Hello. I am Vishal Chavda, and this is the first post on this site.

I like to design websites, apps and write the code, These days, I’m less of a website developer and more of an AI quality inspector—reviewing, testing, and fixing the websites and AI codes, behind the interest started long before any of the jobs, so that is where I will begin.

The part that started early

As a kid I already leaned this way. Games first, then apps. I would open something new and keep going through it, trying to see how it was put together.

A menu that felt quick. A screen that left you lost. I noticed those things before I had any reason to. I still notice them.

The work started somewhere else. In 2010 I was a delivery boy. I was waiting for my class 10 result, and I was not 18 yet, so that was the work I could get. The day was addresses and parcels, and it ended when the last one was dropped off.

I was doing the job in front of me. Websites were not in that picture yet.

A long run of other jobs

What came next did not arrive as a plan. Data entry. Accountant. Sales. Graphic design. Digital marketing. Website support. One after another, each one the thing that was available.

Lined up on a page they look tidy. Lived one at a time, they were just the next stretch of work.

Each of them left something.

Data entry is patience. One wrong character and the whole row is a lie. Accounts is that same pressure with money on it. The totals have to agree, and when they do not, you go back through the pages until they do.

Sales put me in front of people. The real request usually shows up in the second or third sentence, after the polite one.

Graphic design is where I learned to look. A layout can be finished and still feel wrong, and the wrongness is often a few pixels, or a type size you talked yourself into.

Digital marketing showed me the other side of the work. You can like what you made and still watch people leave.

Website support was the first time a broken site was mine to repair. A message comes in. You open the page, you do what they did, and you find the step where it fails.

I liked that last one more than the others. A broken page, then a working one. You can see the difference with your own eyes.

Learning to build the whole thing

Support is meant to keep someone else's site standing. I started editing. A heading that sat too low. A form with one field too many.

Changes small enough to undo if anyone minded. Then a whole page. Then a site I had made, rather than only repaired.

The questions got bigger after that. Where does the text live. What runs when the button is pressed. Can I build the part behind the page, along with the page.

I learned it by reading, by pulling small ideas out of open source projects, and by breaking my own experiments until the error started to mean something. I still work that way.

If a tool or an app is good, I want to see how. With open source, the answer is sitting in the files.

The work I do now is full-stack development. The screen, and the system under it. I still start from the screen. That is the part I learned first, back in the design jobs, and it is the part I trust. If the page is confusing, people never reach the clever code underneath.

On the side I am learning game development. It is the old interest, the one from before any of the jobs, when it was just games and wanting to know how they did that.

I am early. The things I make are small and a bit rough. I am fine with that. A side interest is one of the few places you get to be a beginner on purpose.

What I will write here

This site is where I will keep some of it. Pieces of the path from delivery routes to shipping a feature, when there is something in them worth keeping.

A tutorial when I have walked a problem carefully enough that someone else could follow the same steps. Notes on tools, apps, and open source projects I have been taking apart.

I will write when I have something to say. You can come back here, or follow the RSS feed at /rss.xml and let it tell you when a new post is up.