The hole and the brick truck
The launch-restraint of the approval week inverts. The socio wants Severo perfect before publishing; Juan pushes to ship it to open testing now, because the bottleneck has flipped from ratings to feedback. Without users, he's been digging alone, and the danger is digging a ten-meter hole in the wrong place before anyone tells you it belonged ten meters over (or, in the Brazilian version, a truck dumping a thousand bricks at the wrong house). Fast feedback is Severo's own core promise (write, get answered, no waiting for next class), and the same principle governs their development. The punchline: the socio finally published, and published a two-month-old version by mistake.
// trace: where this idea came from
- ↳ video diary @ 27:49 (nos hace falta feedback, ese es el bottleneck)
- ↳ video diary @ 28:13 (el hueco de diez metros en el lugar equivocado)
- ↳ Entry 221-1: The council approves, nobody rushes (la misma decisión de lanzar, ahora invertida)
- ↳ video diary @ 1:11 (postscript: ya en open testing, todo el mundo lo puede probar)
When Google approved the app, the smart move was to wait, because a store rating is forever and the app wasn’t ready for strangers. A few weeks later the calculus flips. The socio still wants it perfect before publishing, a polished PK passed around internally first ▸ 26:56, and Juan pushes the other way: “publiquen open testing” ▸ 27:10, with expectations set so early users know it may break. The reason is a changed bottleneck: it’s no longer the rating, it’s the absence of feedback. When updates went out constantly, testers responded fast and he corrected fast; now everyone’s stuck ▸ 27:49.
The metaphor carries it: working without feedback is digging a hole, and you keep digging, ten meters down, before anyone tells you “acá no era que tenía que hacer un hueco” ▸ 28:13. Julia supplies the Brazilian version, the truck that dumps thousands of bricks at the wrong house ▸ 28:35. Fast feedback is not a nicety, it’s the difference between correcting a heading and excavating in the wrong lot.
sin feedback cavas diez metros donde no era →
The elegance is that this is Severo’s own thesis pointed inward: the product’s whole promise is that you write and get answered immediately, instead of waiting for the next class to ask the teacher ▸ 28:20, and the same speed-of-feedback that teaches a learner steers a team. The whole reason the curriculum stalled is that Juan is the only one using it, with no one to say whether it’s even the right thing ▸ 29:49. The punchline is on-brand: pushed to publish, the socio published, and published a two-month-old version, 0.10, by mistake ▸ 32:29, now waiting in review. Feedback, requested; feedback about the wrong build, delivered…
Postscript, videos 236-239: the right build went out. Severo passed review and sits in open testing, anyone can install it from the link ▸ 1:11, and Julia’s landing page went live at severo.luarai.com ▸ 7:04. The hole, finally, has other diggers.
// continued in
no entry has continued this idea yet: the arc is still open