I'm Urav. I build things with code.
This section auto-updates daily. It features one of my recent commits, or something interesting from my network, or a random gem from the wild. The commit gets roasted by an opinionated AI and rendered as a strange attractor.
Last updated: 2026-03-31
Commit: dualeai/seek by @clemlesne Β· 7e653b1
Message: "Switch test-unit to gotestsum for JUnit XML output (Blacksmith test analytics)
Blacksmith auto-detects JUnit XML files written to disk during CI jobs,
providing structured test visibility in the dashboard. Replace bare
go test with gotestsum --junitfile so each test-unit run emits a
JUnit XML report that Blacksmith can parse reliably instead of relying
on best-effort log auto-parsing.
CI changes:
- Install gotestsum before running tests
- Pass per-matrix JUNIT_XML env to make test-unit
- Upload JUnit XML as artifact (even on failure)"
Review: Moving away from desperate log-grepping to a dedicated JUnit XML report is a professional choice, a small but critical step towards proper test observability. The world has enough 'best-effort' parsing already; structured data is sanity.
Chaos: 35% Β· Mood: #4da6ff
What is this?
The Pipeline:
- A GitHub Action runs daily and picks a commit (my own β network β starred repos β fallback)
- The commit diff is fed to Gemini, which produces a witty critique, a chaos score (0-100), and a mood color
- A Lorenz attractor is rendered using these parameters:
- Chaos score β modulates Ο (rho), affecting how chaotic the butterfly looks
- Mood color β tints the gradient from black β color β white
- Commit hash β seeds the initial conditions, so every commit is unique
The Math:
The Lorenz system is a set of differential equations that exhibit deterministic chaos. Small changes in initial conditions produce wildly different trajectories. It's the "butterfly effect", fitting for visualizing commits.
Links: