The camera is a code review

Mid-demo, showing the payments screen, Juan interrupts himself: the page is called “Manage subscription”, but the daily pass isn’t a subscription; only the monthly plan is. “Tengo que cambiar ese nombre. Ay, Dios mío” ▸ 2:12. He and Julia workshop replacements on the spot and he writes down the ticket.

Then he notices what just happened, and it becomes this entry: “cuando comenzamos a grabar estos videos, yo estoy en modo análisis, y encuentro estas cosas, porque esta página ya la vi durante el día 50,000 veces y es como que está bien” ▸ 3:05. Fifty thousand glances during the workday found nothing; one pass in front of an audience found the bug in seconds.

explicar la pantalla es volver a verla →

The mechanism is well known to anyone who has fixed a bug while writing the question about it: explaining a thing forces you to actually look at it. The daily video does this to the whole product, every day, for free. It’s rubber-duck debugging where the duck is the audience, and it means the build-in-public format isn’t just marketing with extra steps; it’s a review ritual the product passes through nightly.

The same session logs the sibling principle: fresh eyes that aren’t yours. Yesterday Julia tried the live payment flow and got bounced to localhost after paying, a redirect Juan could never hit because he works on localhost ▸ 12:33. Between the camera and the co-founder, the product gets examined from two positions its builder physically can’t occupy.

Neither reviewer was hired. One came with the YouTube channel, the other with the marriage. The teaching is to notice you have them, and to run the demo like it counts…