Joel and Aaron unpack a recent client project where the only spec was “make these two systems talk.” They share how console-level prototypes helped them clarify data mapping, test tricky scenarios, and keep the client looped in without over-building a UI. If you’ve ever had to code first and document later, this one’s for you.
- (00:00) - Bridging two APIs with minimal specs
- (03:30) - Choosing an exploratory workflow over full UI
- (06:00) - Console closures for quick, testable steps
- (09:15) - Hand-off strategy: letting others poke the prototype
- (11:45) - Silly bit
Episode 128
