Builds systemsthat haveto be fast.

The AI cannot break a report

Civic issue reporting — people photograph a pothole or a broken streetlight, mark it on a map, and the report enters a tracked dashboard.

Hard part. Two people photographing the same pothole must not become two reports, and an embedding comparison against every prior report does not scale. Dedup runs as an agent: Gemini embeddings at 768 dimensions over a pgvector HNSW index narrow the field, Groq-hosted reasoning judges the survivors, and a human confirms. A rejection-memory constraint records every dismissed match so the same false positive is never raised twice.

Stack

Next.js, Express, Prisma, PostgreSQL, pgvector, pg-boss, Gemini, Groq

Role

Solo — backend first, then the frontend on it

Status

Deployed

Deterministic by construction

Pulls your solve history from LeetCode and Codeforces, works out which topics you are actually weak at, and ranks what to solve next.

Hard part. Mastery could not be solved/total, which hands you 1.0 for a single lucky solve. It is a Laplace-smoothed rate pulled toward 0.5 by a confidence term that scales with sample size, so one solve out of one reads as "no evidence" rather than "mastered". The selection is ordinary arithmetic end to end — no model chooses, ranks or filters anything, so identical inputs always give identical output. The LLM only writes hints on top of decisions already made.

Stack

Node, Express, TypeScript, Prisma, PostgreSQL, Next.js 16, Groq

Role

Solo

Status

Deployed

Routes around what it cannot trust

A distributed real-time network simulation where the routing layer reroutes around nodes it no longer trusts.

Hard part. Two routing algorithms run concurrently over the same live topology — a naive OSPF-style shortest path against a health-aware Dijkstra — so the cost of trust-blind routing is visible rather than argued. Node health feeds back into the cost function, letting the health-aware router drop compromised nodes mid-transit without any manual intervention.

Stack

Node, Express, Socket.IO, React 19, Three.js

Role

Solo

Status

Not public

No cloud database at all

Group trip planning — shared trips, destination tabs, and hotel links collected in one place instead of scattered across chat threads.

Hard part. Built deliberately as a weekend project, and the interesting call was dropping the cloud database entirely. It runs on a local SQLite file through better-sqlite3, with passwordless name-plus-email sessions, which removes the whole OAuth and connection-pooling surface from a tool that only ever needs to serve one group at a time.

Stack

Next.js 15, better-sqlite3, NextAuth v5, Zod

Role

Solo — weekend build

Status

Source available