Most design feedback fails in one of two ways: “looks great,” or a giant list with no sense of priority. I built The Crit around a different question: what is the most useful thing to tell someone while the file is still open? You bring the actual work. The Crit returns a clear read, points to visible evidence, and names the first move worth making. The critique stays with the project through notes, questions, and a revision check, so the feedback can change the next version instead of becoming another report you read once. The product comes from more than a decade of teaching design and trying to name why work feels clear, confusing, ready, or not quite there. AI can make more screens. Judgment is still the scarce part.

Most inspiration libraries are good at helping people collect examples and weak at helping them explain why something works. Taste Cabinet is my attempt at a different kind of learning object: a growing cabinet of design principles, each translated into an interactive specimen. Open one idea, manipulate it, then pair it with another and use the tension between them as a critique lens. The product is not the size of the archive. It is the path from noticing an idea to using it on something you made.

The score is probably the least interesting part of the critique. What people actually want is the sharp part. What's off. Why it matters. What to fix first. A number looks clean in the UI, but it's rarely the thing that builds trust. The useful part is the note that makes you reopen the file.

A lot of legacy software does not need a total reinvention. It needs taste, restraint, and a better visual system. The hard part is not making it look new. The hard part is making it feel current without breaking the habits people rely on.

Rebuilt Pixel Lab from scratch for v2 — all client-side, your image never hits a server. Canvas API does the heavy lifting. The real upgrade is Floyd–Steinberg error diffusion. Hard palette quantization without dithering gives you flat color bands; with dithering you get expressive gradients from just 4 colors — Game Boy greens that actually look like photography. 9 palette presets, color levels that always posterize before palette snap, compare-original toggle, quick recipes. Started because I needed Game Boy greens fast.

AI is great at getting you moving. It is not great at taste. It can help you ship faster, write faster, test faster. But knowing what to keep, what to cut, and what feels slightly off still takes judgment. That part is annoyingly human.

DriftKit is a motion-first component library — every interaction starts from spring physics (mass, stiffness, damping) instead of CSS easing curves. Easing flattens velocity; springs have weight. 52 components across two tiers. Showpieces (magnetic dock, cursor glow, digit roll, jelly hover) and Standard UI (buttons, inputs, tabs, dialog, accordion) with motion baked in. Zero install — copy-paste React with just two deps: React and Framer Motion. Built it to teach students how spring animations actually work. Turned out everyone wanted the presets without the lesson.

Good product design is often just complexity management in a nice outfit. A lot of the job is deciding what gets emphasized, what gets hidden, what can wait, and what needs to feel obvious right away. Not glamorous. Very important.

Most people know when something feels off. Fewer people can name why. That's the part I'm most interested in — in teaching, in critique, and in product work. Taste is useful. But taste with language is where things actually start improving.

I trust live products more than polished case studies. A real thing with users, edge cases, ugly constraints, and a weird bug backlog tells me more than a perfectly lit deck ever will. The work is more honest when you can actually click it.

I teach design classes every term and I don't have a case study portfolio. My case studies are the products themselves. The irony isn't lost on me. 🫠

Font Pairing Tool lives inside The Crit — 20 Google Font pairings, previewable with your own copy, CSS you can copy and paste. The hard part wasn't the pairings. It was the framework for picking them. Most pairing guides lean on pattern ("serif + sans") or taste ("this looks nice") — neither helps a junior designer decide. So I grouped them by function: editorial, UI-safe, expressive, neutral. The choice leads with intent, not category.

FFSF is a listing site for family-friendly SF spots — 230 places across 36 neighborhoods, curated with real photos and tags for age range, indoor/outdoor, weather-friendliness. Built on Next.js + Supabase + Puppeteer for photo scraping. Server-rendered so listings show up for the real search queries parents actually type. I just garden occasionally. 🌱

Grading thousands of student assignments taught me more about design than a decade of practice. You see every mistake. Every font crime. Every "I did this because I didn't know what else to do." And then you see the ones who just get it, and it reminds you why you teach.