Normalizing 30 Judges Without Lying About It: the maths, a counterintuitive k, and what I chose not to build
TL;DR. I built Rubrica, a self-hosted hackathon portal, for DOGFOOD 2026. The interesting part is not the feature list. It is a judging engine whose maths you can verify by hand, one result I am uncomfortable with but kept, a parameter (k) that behaves the opposite of what you would guess, and a list of things I refused to build, with reasons. Repo: https://github.com/aanushiya170/rubrica · Python 3.12 · FastAPI · SQLite · one container · MIT Fixture 41 projects, 30 judges, 8 tracks, 40 teams, 126 scores Acceptance checker 7 checks, all T1/T2 My extra checker 31 live HTTP checks (T3 12/12, T4
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in