Developer • Designer • Builder

Hi, I'm Arnav.

I like taking an idea that exists in my head and turning it into something people can click, play and poke at. Most of what I build sits somewhere between web development, games and algorithm testing, where a technical problem and a creative one can be resolved using the same solution.

  • Web

    • Interactive websites
    • Front-end development
    • User experiences
  • Games

    • Game development
    • Game systems
    • Mechanics and design
  • Code

    • Algorithms
    • Software development
    • Problem solving

The part of building I enjoy most is the implementation of an idea. Seeing a tangible solution that solves an problem is the most satisfying aspect of why I code. An idea costs nothing. Making it real means deciding how it should feel, finding the algorithms that makes it possible, and working through every small problem that stands between a rough prototype and something another person enjoys using.

That's why I keep ending up where programming meets design. A game mechanic is a systems problem and a feel problem at the same time. A website is the server code, but it's also layout, motion and the few seconds someone spends deciding whether to stay. I like to work where getting the logic right and getting the experience right are the same job.

Learning
  • Java
  • Python
  • Algorithms
  • Web development
Building
  • Personal projects
  • Games
  • Interactive websites
Exploring
  • Game design
  • Creative development
  • Software engineering
Looking toward
  • Opportunities to build interesting things and keep learning from other developers.
All projects →

Color Flood Solver

A Python solver for Ponder Club's daily Color Flood puzzle. The program scrapes the board straight off the screen, then searches for solutions.

  • Python
  • Playwright
  • OpenCV
  • NumPy
  1. Build it to understand it

    Rebuilding something from scratch — a board game, a puzzle solver, this website — teaches me more than reading about it. I'd rather know how a thing works than only know how to use it.

  2. Working is the halfway point

    Once a feature works, the real work starts: timing, feedback, QOL, and the small details that the users see at an immediate galnce. These decide whether something feels good to use or just technically functions.

  3. Small working steps

    I build in milestones that each leave something usable behind. I am not afraid to commit small changes to test end user implementation. This very site went from a static meadow to an archer that fires arrows one working step at a time.

  4. Comparing different solutions

    When two approaches compete, I quantify them to find the optimum. Part of the point of the Color Flood solver was comparing a greedy heuristic against A* on the same boards.

Want the formal version, or want to talk?