About

Questions start the work. Building tells me what I understand.

I am Aaditya Shah, a second-year B.Tech student in Computer Science and Engineering at IIT Gandhinagar, graduating in 2029. I am drawn to difficult questions at the meeting point of mathematics, computation, and engineered systems.

The common thread is not a fixed technology stack. It is curiosity: trying to understand why something works, what structure is hiding underneath, whether the explanation can be generalized, and what building it reveals.

I entered IIT Gandhinagar in Mechanical Engineering and changed to Computer Science after my first semester. I was certain that I wanted to move closer to computation; I was much less certain about what I wanted computation to lead toward. That uncertainty now feels less like a problem to eliminate and more like room to investigate.

Programming has been an important part of how I learn. I have built Android apps, simulations, web experiences, and small automated systems, but I increasingly see software as a medium rather than a professional identity: a way to make an idea concrete enough to test, share, or challenge.

Right now, the Enigma investigation is my main research thread. I am also beginning to study quantum computing through its mathematical foundations, learning algorithms more deliberately, and reading philosophy—especially questions about knowledge, consciousness, ethics, and what it means to understand something.

I have a habit of following questions further than I originally intended. Sometimes that becomes research; sometimes it becomes a prototype, a page of mathematics, or simply a better question.

Building with other people has widened that process. At Blithchron, I serve as a Design and Tech Coordinator and have deployed the Blithchron 2027 website. The work keeps reminding me that understanding a system also means understanding the people, constraints, and decisions around it.

Why this atlas

Make the work understandable.

I wanted this site to behave more like a working notebook than a polished résumé.

Questions can remain unfinished. Investigations can show failed assumptions and changed conclusions. A project can matter even when I no longer want it to define me.

The aim is not to make everything look impressive. It is to leave an honest, useful record of what I was trying to understand.

How I work

A question becomes clearer by moving through a few forms.

Every investigation can inherit this method, even when the order bends or a step sends me back to an earlier one.

  1. 01Notice

    Find the thing that does not yet make sense.

  2. 02Read

    Locate the history, language, and existing explanations.

  3. 03Model

    Make the structure explicit enough to reason about.

  4. 04Build

    Turn an idea into a system, simulation, or artifact.

  5. 05Test

    Look for evidence, counterexamples, and constraints.

  6. 06Explain

    Write down what changed and what still resists clarity.

  7. 07Return

    Come back when a better question or method appears.

Long horizon

The horizon is larger than software.

Over time, I want to move closer to technologies that change what humans can understand or build—especially quantum systems, intelligence, robotics, energy, and computation that meets the physical world.

These are directions of attention, not a settled ten-year plan. For now, the work is to build strong foundations, follow difficult questions carefully, and notice which of them continue to hold my attention after the novelty disappears.

This atlas is meant to grow with that process: notes can become investigations, investigations can become research or tools, and questions can be revised without pretending they were ever settled.

Working on something difficult?

I am always glad to hear from people thinking carefully about mathematics, computation, research, or complex systems.