Mathematics → game development → AI engineering.
I like understanding the structure underneath an answer: what it assumes, and whether the evidence actually supports it. A bias for honest evaluation over shiny demos, most recently SteamLens, a live LLM product that cites its own measured accuracy. Built in public.
What do Steam reviews actually praise and criticize and how much trust should you place in the answer? SteamLens is an evaluation-first review analysis system planned as four milestones; the first three are built, measured and live, and the fourth is deliberately deferred. It turns unstructured reviews into measured, aspect-level evidence, with the labeler's quality, cost, and failure modes published beside the numbers.
Two deployed projects, two hosts, one edge, and one shared operational layer between them. It appeared when the second project's ingress changes started landing in the first project's repository. That layer was extracted into its own repository behind an explicit ownership line, then held to one test per claim: what existed adopted on zero-diff plans, the host rebuilt from a blank machine by a playbook, and a rebuild-and-restore drill from nothing in about an hour.
A four-part research arc: a measurement instrument that had to earn trust first, then one question asked three times with the ground truth progressively removed — can learning rediscover optimal play as a table, as a network, and finally as a bet-sizing rule whose signal is buried fifty-deep in per-hand noise?
A learned A* heuristic that looked like a wash — until the pooled average was split and two opposite effects appeared. One regime-tag feature turns it into 17% less search at a 0.2% cost; moved off its training distribution, it fails in two opposite ways. Two axes, never collapsed into one score.