Three branches, one Frankenstein
The team stops working in series and goes parallel. Julia gets her own local Severo and her own branch, so she can build gamification directly instead of designing mockups and waiting a week or two to see the coin she made appear. Juan owns the backend branch, and Carlos becomes the integrator, 'Dr. Frankenstein', stitching everyone's pieces into production and pushing weekly Wednesday releases. The teaching is about dependency and growth: work where one person waits on another breeds backtracking and stale versions, while separate branches plus a designated merger let each person move independently. And when Carlos broke the app on a backend piece he didn't understand, Juan let him struggle three hours and fix it himself, because a teammate who only ever gets rescued never learns to.
// trace: where this idea came from
- ↳ video diary @ 3:45 (cada uno en su rama; Carlos une las piezas)
- ↳ video diary @ 4:39 (dejarlo pelear con el bug para que aprenda)
- ↳ Entry 243-1: A manufactured audience (la fricción de trabajar en serie que aquí se resuelve)
The async pain they’d been feeling, one person’s changes invisible to another, “that’s not there anymore / for me it is”, finally gets restructured. Julia gets her own local copy of Severo and her own branch ▸ 0:52, because the old flow was killing her: she owns gamification, yet a coin she designed took a week or two to appear, since she had to hand a mockup to Carlos and wait for him to implement it and for someone to like the result ▸ 0:32. Now she builds it herself.
The new shape is three parallel branches and one integrator. Juan works the backend locally, Julia the gamification, and Carlos becomes “el Dr. Frankenstein”, the one who unites everyone’s pieces and pushes to production ▸ 3:45, on a weekly cadence, a version shipped every Wednesday, live by Friday ▸ 7:32. The teaching is about dependency: a pipeline where one person waits on another breeds backtracking and stale versions, “uno depende del otro”, while independent branches plus a designated merger let each person move at their own speed ▸ 3:00.
ramas paralelas y un integrador, no una fila →
The second lesson is about how a teammate grows. Carlos broke the app on a backend piece he didn’t fully understand, and Juan, who already saw roughly where the error was, chose not to fix it, “inténtelo, y si no puede, me avisa” ▸ 4:39. Three hours later Carlos had solved it himself, which is the point: a teammate who is always rescued never develops the skill to debug the next one ▸ 4:54. Independence is the same move at every scale here, give each person their own branch, and give them the room to be stuck…