The boss learned to vibe code

The setup arrives via the vibe-coding group, right after the day’s omen, Claude Code went down and the members joked about touching grass, superpowers revoked ▸ 0:24. Daniel’s dilemma: his boss, who knows no programming, now vibe-codes in Cursor, front and back, shipped a feature nobody could understand, and needs Daniel to review and deploy it all, delaying Daniel’s own work ▸ 1:23. The role inversion gets named on camera: you become your boss’s babysitter, and when he breaks something, “la culpa es tuya” ▸ 2:44.

The thread’s proposals map the whole option space. The negotiator: cap support at five official hours a week, billed visibly against your own KPIs, though Daniel predicts the boss will ignore the agreement ▸ 5:33. The defensive camp: let it burn, keep a parallel version, “a veces hay que dejar que el mundo arda un poco” ▸ 8:54, which he distrusts. The accountant: log your hours so the boss sees what his burradas cost when invoicing dips ▸ 14:37.

si el jefe ya traduce su idea a código, tu puesto nuevo es revisar que no se rompa →

His own posted answer is the entry’s thesis: the trend is friction removal. An idea passing from head to head to code is a broken telephone, your square becomes my circle and ships as a triangle ▸ 10:53; the person holding the idea translating it directly is strictly better, the same reason he skips Figma and goes mockup-to-code in one tool ▸ 11:52. So if the boss makes useful things, let him work and you review: win-win, “es como volverse el senior”, the one who delegates and fixes what breaks ▸ 13:26. The job security argument is his brother’s asymptote: the AI does 80%, then 95, then 99, and the last percent always needs someone technical ▸ 4:13. Whether that percent pays less as a commodity or more as scarce expertise, they leave honestly unresolved ▸ 4:56. What’s settled is the posture: the threat framing loses to the promotion framing, every time…