concept lab
The direction.
Both are built rather than mocked up, and both run on real data — 1,938 real contributions and the actual photograph. A third direction, a live-telemetry dashboard, was built and cut: it led every panel with a star count, and two of the three repos have none.
A lattice of dots and a single unbroken line that goes around every one of them, never crossing, closing where it began.
- why it fits
- The rule comes from tipkyanchi rangoli — the dot-grid form of Maharashtra, drawn in Vidarbha, where he is from. It is also a solvable constraint, and the figure on the page is the solution, computed at build time.
- the signature
- The stroke draws itself across a year of real commits.
- what it costs
- 0 KB of JavaScript. Static SVG. Renders with scripting disabled.
- what could go wrong
- Reads as decorative unless the algorithm is visible. Mitigated by showing the loop count collapsing to one.
A point cloud sampled from his photograph that reforms into the contribution lattice, then into the journey, and back.
- why it fits
- Maximum memorability, and the option closest to the 3D scroll spectacle he was drawn to.
- the signature
- His own figure dissolving into the record of his work.
- what it costs
- The heaviest of the two — a canvas render loop that runs continuously.
- what could go wrong
- Built and rejected. With the only photograph on file the cloud reads as noise rather than a person, and the genre signals creative developer — the exact misread that costs him backend roles. Kept here so the verdict is visible rather than asserted.
my recommendation — One Stroke. The dot lattice and the contribution grid are the same shape, so a single surface carries both the generative figure and the real record of work. Star counts stay off the page entirely except where the number is genuinely large; the proof strip leads with commits, users and the documented rating instead — all four of which stay true regardless of how any repo trends.