Bob: a tour of Duplo, McLoop, Orchestra, and Vroom

Software engineering used to have a guy named Bob. Bob's job was to

look at what you were doing, ask why, and tell you to slow the hell
down. Bob read the spec before the code. Bob read the code before the
commit. Bob read the commit before the deploy. Bob was annoying. Bob
was correct. I miss Bob.

Vibe coding does not have Bob.

This talk presents four tools that put Bob back.

Duplo is Bob creating the spec. Tell Duplo what you want, point it at
a product URL, drop in screenshots, PDFs, or a demo video, whatever
you have. Duplo produces a phased build plan. The quality of the
output is a direct function of the quality of the plan. This restores
the incentive to design carefully, a habit the field has been losing.

McLoop is Bob running, testing, and debugging the build while you
sleep or binge Netflix. It runs autonomous coding sessions for hours
or days, with fresh context per task, tests and lint after every
change, and only clean code committed. It will bug you if
necessary. McLoop builds what Duplo designed.

Orchestra is grumpy Bob fighting LLM slop. Any single LLM can fail
spectacularly. Bob doesn't like that. Orchestra gives different models
different jobs, then makes them argue, interact, and sing harmonies
before anything touches the workspace. Multi-model architectures are
not an optimization; they are how you get review, disagreement, and
judgment back into a process that is quickly losing them.

Vroom is Bob reading what shipped and asking what he should
have done differently. Vroom runs parallel auditors on your system,
coalesces their findings, and proposes a corrected or expanded
version. Eventually Vroom becomes Bob running the whole thing in a
loop: proposing changes on branches, gating them on verification, and
merging what survives. You can sleep through this.

Short live demo of all four. Where Bob came from. Where Bob
breaks. Bring questions, and bring the kind of skepticism the field
used to have before it fired Bob.