Final stop · the pilot

A person wholikes makingthings work.

I'm Amartya — from Kanpur, living in Bengaluru. Right now I build the tools Walmart store teams run their day on, and lead the AI work on my team. Before that I taught a phone to read lab reports at Samsung. The title on the badge keeps changing — the habits underneath it don't.

currently: learning CUDA, and how inference actually gets fastarrived
learns in public
finishes things

Right now

On the shelf

the one part of this page that's meant to go out of date

Learning

CUDA, at night

Kernels, memory, and what actually makes inference fast. Slowly, properly, from the bottom.

Building

Agents that file the paperwork

The multi-agent system that writes and scores change requests, still growing new hands.

Writing

Notes as I go

Whatever I just worked out, written down badly first so it can be written down properly.

Next

A layer down

Closer to the metal than last year, and closer again next year. The direction has never changed.

The route so far

Where I've flown

he changes clothes at every stop — scroll and watch

2020

Started building things in Kanpur

Four years of Information Technology at HBTU, and a lot of evenings making things that were not on the syllabus. Left with a 9.0 and the habit of finishing what I start.

HBTU, KanpurB.Tech IT

2024

Six months teaching a phone to read

Samsung's Generative AI team in Noida: a pipeline that turns a photograph of a lab report into a health dashboard. It ships pre-installed on Galaxy devices.

Samsung R&DComputer vision

2024

Moved to Bengaluru, met 4,600 stores

Walmart Global Tech, on the tools store associates open every morning. Eleven services, a labour-law deadline, a Bravo award — then I started handing the boring parts to agents.

Walmart Global TechBengaluru

Now

Going a layer down

Learning GPU work properly — CUDA, kernels, and what actually makes inference fast — and writing down what I find as I go.

CUDAInference

Regardless of the job

How I work

four promises, in the order they happen

01

Day one

It gets drawn

Before any code, a sketch of how the thing works. If I can't draw it, I don't understand it yet — and it's much cheaper to argue with a drawing than with a pull request.

02

Day two

Something already runs

A small working thing beats a beautiful plan. You get something you can click while the spec is still warm, even if it's ugly — especially if it's ugly.

03

Then

Correct, kind, fast — in that order

Right first, pleasant to use second, quick third. Every other order I've tried spends someone else's week.

04

Always

The notes are public

Whatever I worked out gets written down, so the next person doesn't have to come and ask me. Half of what I know came back to me that way.

The short version: you'll see something working before you see a status update.

that's the whole method

The guestbook

Sign the page?

Every visit is counted — nothing about you is. Press the stamp and I'll tell you how many people have been here.

the ink is real, the tracking is anonymous →

Say hi

Tell me what
you're making.

© 2026 Amartya · drawn, then built

Bricolage Grotesque · Instrument Sans · Shantell Sans