Writing
Research notes, engineering problems, and the occasional detour.
byteforge, hack club, and the 24 hours that got too real
how a student community in kanpur went from hack club workshops to a four-day hacker house, execron, and backing the next wave of young builders.
day 1: the train south
yc startup school, a 32-hour train, and asking a co-founder for help instead of pretending i had a plan.
day 2: the room was not the point
vibecon was an excuse to be in the room. the conversations were the actual work.
day 3: coming home with a different team
tests were waiting in kanpur. so was the beginning of a three-person team.
day 4: research changed the pace
iit kanpur gave the work a second rhythm: slower questions, sharper evidence.
day 5: earn enough to go back
the second trip started with a little more money and the same unfinished plan.
day 6: four days with a roof
campus accommodation bought us the one thing early builders never have enough of: focus.
day 7: three hackathons, one codebase
the calendar got ridiculous. the work got simpler: build a base that survives the next demo.
day 8: the useful coffee
one long conversation about indian edtech made the problem in front of us much clearer.
day 9: feedback that made the product smaller
a direct conversation at 
prolearn cut the pitch down to the problem that mattered.
day 10: twenty-five days later
the planned week became 25 days, including two very broke days outside a petrol pump.
the first thing i built was a contra game
a laptop in lockdown, a scratch game, a python book, robot arenas, and the long route into ai.
two weeks in bangalore, or, how i ended up sleeping on a petrol pump and still called it productive
two weeks in bangalore, or, how i ended up sleeping on a petrol pump and still called it productive. 15 jun - 5 jul 2026.
getting sedd and llada to work on hindi
discrete text diffusion models are trained and benchmarked almost entirely in english. running them on hindi breaks in ways papers don't mention.
building ARGUS's camera ingest pipeline
ARGUS pulls in rtsp feeds, ads-b, and ais data and renders it live in webgl. the ingest side alone took longer than the renderer.