I’m a product architect in Chicago. I’ve spent more than 25 years turning complicated decisions into working software.
The short version
I started in software engineering, moved through architecture and consulting, and now work as a Product Architect at commerce.com. I still prefer the part where a decision becomes a working system.
Outside the day job, I run Let’s Pepper, build and operate Rally HQ, shoot volleyball through Flickday Media, publish Signal Dispatch, and keep a music practice on SoundCloud. They look different, but each has to work for the people in front of it.
The practice has a newer shape too: I take engagements outside my own domain and come back in days with working software, evidence a client can check, and problems they couldn’t see. AI agents supply the depth; the architecture years supply the steering. I wrote about the first full test of that model in The Depth Penalty Is Gone.
- Current role
- Product Architect
- Organization
- commerce.com
- Home
- Chicago
- Software practice
- Since 1999
What connects the work
The form changes. Each practice asks me to make something useful, run it under real conditions, and own the result.
- Live operations
- Run registration, schedules, brackets, scoring, and the event around them. See volleyball work →
- Photography
- Anticipate the point before it happens, then make the result easy to find and keep. Open photography →
- Writing
- Turn working evidence and unfinished thinking into published arguments. Read Signal Dispatch →