Entry list · car 08
Garsondiya
Final-year Computer Science student with a business and economics minor — which is a formal way of saying I like knowing both how a thing is built and why anyone would pay for it. Most of what I make starts the same way: something looked interesting, nobody had built quite the right version of it, and I wanted to see whether I could.
This site is a fair example. I wanted to know exactly what it would take for my driver to still win the championship — not a pundit's guess, the actual arithmetic — and no one was showing the working. So here it is, showing the working.
Technical specification
What I run
- Power unit
- PythonJavaScript JavaSQLC
- Chassis
- ReactNode PandasGitFigma
- Aerodynamics
- Data analysis, front-end that doesn't look like everyone else's, and the unglamorous middle bit where messy real-world data becomes a clean number.
- Ballast
- Business & economics — market sizing, unit economics, and a working suspicion of any dashboard that can't explain where its numbers came from.
- Currently testing
- Whatever's caught my attention this month. Right now: this.
- Team radio
- Email · GitHub
Stint history
The degree, as a race strategy
Currently on the last stint, tyres holding on, radio quiet. Graduating 2027 and looking at what comes after.
Colophon
How this site was built
No framework, no build step, no database. Three HTML pages, one stylesheet, six scripts. It runs on ordinary shared hosting because there's nothing to run — every number on the site is fetched fresh from a public API when you open it.
The data
Standings, results and margins come from Jolpica-F1, the volunteer-run successor to the Ergast database that shut down after 2024. Session detail — sectors, speed traps, tyre stints, telemetry — comes from OpenF1. Both free, both open, neither affiliated with F1.
The maths
The simulator doesn't predict anything. A driver is out when their maximum possible total can't reach the leader's current total — that's it. Every win count on the page is a solved minimum, not an estimate. The one modelled number is the title probability, and it's labelled as such.
The honest bit
There's no free public API for genuine live timing — the official feed isn't licensed for it. So the weekend page fills in shortly after each session ends rather than during it. I'd rather say that plainly than pretend otherwise.
Open the channel
Got something worth building?
I'm finishing my degree and looking at what's next — internships, grad roles, or just a good problem someone hasn't solved properly yet. If you've got one, say so.
Get in touch