I built a chatbot in React called Petty Bickerson, designed to argue with me. This serves as a proof of concept for creating an interactive chat interface.
The real experiment focuses on where UX craft fits into this AI-driven world. The app was prompted into existence, but the character is mine—featuring five expression states, custom-animated in Rive, and capable of listening to user input live while firing triggers as you type. Petty Bickerson reacts to CAPS, interrupts apologies, and takes it personally when you agree with him. All of this was accomplished in under a day.
I've long suspected that reactive characters could enhance AI chat engagement, but it's a dosage problem. At full intensity, it can become almost too annoying. Perhaps this concept would be better suited for voice chat? The intriguing design question has shifted from "can the interface react to you" to "how much should it?
0
110
Two Halloweens ago, I was given the opportunity to work with Uber Eats on a free candy promotion campaign, where I built the live website that updates each day with a new riddle to solve.
The idea was simple,
You solve the riddle 🎃, you get the candy. 🍬
The outcome was incredible!
👻 290,000 promo codes used in less than 8 hours!
🎃 2 million promo codes used by Halloween!
💀 44% new Uber Eats users!
The campaign turned out to be a huge success, and was the most successful promo code campaign for Uber Eats grocery delivery! Ever!
I hope to one halloween do something just as awesome again! Trick or Treat!
4
30
420
Currently deep in the early build phase of a new platform, focusing on system architecture, data models, and core domain logic. Much of the work right now involves designing scalable APIs, defining clean boundaries between services, and validating performance and reliability assumptions early.
This stage is less about features and more about foundations, choosing the right abstractions, reducing future technical debt, and ensuring the system can evolve safely as requirements become clearer. Quiet progress, deliberate decisions.
More updates as it matures.
14
181
A developer tool that makes React Server Components easier to understand, debug, and teach.
I built RSC Boundary, a dev-only overlay for Next.js App Router projects that visualizes where Server and Client Component boundaries exist at runtime.
React Server Components are powerful, but the mental model is still hard for many teams. The biggest issue is visibility: once use client starts spreading through a tree, it becomes difficult to reason about what runs where, what ships to the browser, and why certain code behaves the way it does.
RSC Boundary solves that by making those invisible boundaries visible.
It helps developers:
- See Server and Client Component boundaries directly in the app
- Understand how use client affects the component tree
- Debug unexpected client-side rendering behaviour
- Onboard teammates faster to the Next.js App Router model
- Build confidence when working with modern React architecture
The project reflects the kind of work I enjoy most: turning complex developer experience problems into simple, useful tools that make teams faster and more confident.
0
41
