The longer version / Vol. 01
A student
with a wide
syllabus.
I am Ishan Asati — a student, developer and maker based in India. I am interested in how technology works, and in turning that curiosity into things that run.
01 / The short story
Not one
discipline.
I am more interested in understanding systems deeply than in collecting achievements. That has taken me across software, machine learning, electronics and the spaces in between.
My interests span artificial intelligence and computer vision, application development, Python, robotics and embedded systems, Linux and open-source software, and small creative experiments. I do not treat these as separate identities. They are different angles on the same question: how does this work, and what can I make with it?
I learn best through projects. Most of what I know has arrived by building something slightly beyond me at the start — then reading, breaking it, and trying again. I am still early in that process. That is the honest position, and it is also the interesting one.
“My interests rarely stay in one place, and that's exactly how I like it.”
02 / Fields of interest
Five directions,
one curiosity.
In use means the field appears in a project on this site.Exploring means I am actively learning, without claiming mastery. There are no percentages here because proficiency is not a progress bar.
- 01
Artificial intelligence
Machine learning, deep learning, computer vision, neural network architectures and local AI experimentation.
In use - 02
Software engineering
Application development, architecture, TypeScript, React and the practice of making software maintainable.
In use - 03
Hardware & robotics
Embedded systems, microcontrollers, sensors and the point where code has to survive the physical world.
Exploring - 04
Systems & open source
Linux, operating systems, development environments and how software actually meets the machine.
Exploring - 05
Creative programming
Python, Pygame and interactive experiments made for curiosity rather than a product roadmap.
Exploring
03 / A working inventory
Tools, not
trophies.
Used in projects
- Python
- PyTorch
- TypeScript
- React
- Vite
- Tailwind CSS
- shadcn/ui
- Dexie / IndexedDB
- ESP32
- Sensors & displays
Also working with
- HTML & CSS
- Astro
- Git & GitHub
- Linux / WSL
- VS Code
- Command-line tools
Currently learning
- Systems programming
- Local AI models
- Pygame & game loops
- Computer-vision evaluation
- Embedded systems
- Software architecture
This is a living inventory. A tool appears here because I have used it in something, or because I am spending time with it — not because it belongs on a résumé keyword list.
04 / How I work
Three
habits.
Not a manifesto. Just the working rules I keep returning to.
- 01
Build to understand
Reading about a system is useful. Building one, watching it fail and fixing it is what makes the knowledge stay.
- 02
Keep the loop short
Small, finished experiments teach more than large, abandoned ones. Scope is a design decision, not an apology.
- 03
Document honestly
A result is more useful when its limits travel with it. I would rather show an unfinished thing clearly than a finished-looking thing falsely.
A note on credentials
I am a student. I do not have years of industry experience, a list of publications or a company to my name, and this site does not pretend otherwise. What it documents is real work at its real stage: research that is research, software that is still being built, and hardware that is still on the bench.