ontoref/assets/presentation/critical-phrases-blocks-30min.md
Jesús Pérez d59644b96f
feat: unified auth model, project onboarding, install pipeline, config management
The full scope across this batch: POST /sessions key→token exchange, SessionStore dual-index with revoke_by_id, CLI Bearer injection (ONTOREF_TOKEN), ontoref setup
  --gen-keys, install scripts, daemon config form roundtrip, ADR-004/005, on+re self-description update (fully-self-described), and landing page refresh.
2026-03-13 20:56:31 +00:00

5.5 KiB

Rustikon 2026 - Frases Criticas por Bloques (30 min)

Guia de control narrativo para saber si vas en tiempo o debes acelerar.

Resumen de Bloques

Bloque Slides Objetivo narrativo Tiempo bloque Acumulado
B1 Hook & Promise 1-3 Abrir con credibilidad y dolor real. 01:31 01:31
B2 Escalation 4-7 Mostrar que la complejidad crece sin control. 04:36 06:07
B3 Problem Anatomy 8-14 Hacer evidente la causa raiz y el costo de fallar tarde. 07:41 13:48
B4 Turning Point 15-18 Giro narrativo: no faltan tools, falta paradigma. 02:02 15:50
B5 Resolution by Types 19-23 Conectar Rust/tipos con respuestas concretas. 02:59 18:49
B6 Proof in Production 24-31 Probar con casos reales e impacto operativo. 08:32 27:21
B7 Close & CTA 32-35 Cerrar con mensaje memorable y accion. 02:39 30:00

Señales de Ritmo

  • Si en 10:00 no has llegado a Slide 12-13, acelera (reduce ejemplos y tablas).
  • Si en 20:00 no has llegado a Slide 24, recorta explicacion tecnica y ve a casos reales.
  • En 27:00 deberias estar entrando al cierre (Slide 32+).

B1 - Hook & Promise (Slides 1-3)

Tiempo objetivo bloque: 01:31

Objetivo: Abrir con credibilidad y dolor real.

Frases criticas por slide:

  • Slide 1: Why I Needed Rust / Finally. / infra Automation I Can Sleep On
  • Slide 2: Years. / One Problem. / Era Tool Lesson
  • Slide 3: The Evolution / How we got here

Regla de enfasis:

  • Habla lento. No vendas tecnologia; vende problema vivido.

B2 - Escalation (Slides 4-7)

Tiempo objetivo bloque: 04:36

Objetivo: Mostrar que la complejidad crece sin control.

Frases criticas por slide:

  • Slide 4: Stage 1. / Local (late 80s / early 90s) / Dumb terminals. / Single machine. / One state.
  • Slide 5: Stage 2. / Networks / Internet / Systems getting farther away. / More people. / More coordination.
  • Slide 6: Stage 3. / Containers / Cloud / CI-CD / Everything. / Everywhere. / All at once.
  • Slide 7: I could automate infra. / But I couldn't make it reliable.

Regla de enfasis:

  • Sube energia y marca cada "lesson" con pausa corta.

B3 - Problem Anatomy (Slides 8-14)

Tiempo objetivo bloque: 07:41

Objetivo: Hacer evidente la causa raiz y el costo de fallar tarde.

Frases criticas por slide:

  • Slide 8: Why I A C Fails / The restaurant problem
  • Slide 9: The Restaurant / Every restaurant has at least three actors.
  • Slide 10: The Truth That Mutates / State is not static. / It can change at every step of the chain.
  • Slide 11: "We Don't Have Mushrooms" / When an actor in the chain can't fulfill part of the order.
  • Slide 12: The Config Evolution / How we got from code to YAML hell
  • Slide 13: Continuous C I slash C D. / No semantic check.
  • Slide 14: Three Questions Without Answers / Fail late is expensive. Fail early is cheap.

Regla de enfasis:

  • Maxima claridad. Una idea por frase.

B4 - Turning Point (Slides 15-18)

Tiempo objetivo bloque: 02:02

Objetivo: Giro narrativo: no faltan tools, falta paradigma.

Frases criticas por slide:

  • Slide 15: The tools weren't the problem. / The languages weren't the problem.
  • Slide 16: Systems we don't know how to control. / We hope they work.
  • Slide 17: Rust / The answer to all three questions
  • Slide 18: The Bridge: From Serde to Types / Serde loads structurally valid config.

Regla de enfasis:

  • Haz silencio antes y despues del giro.

B5 - Resolution by Types (Slides 19-23)

Tiempo objetivo bloque: 02:59

Objetivo: Conectar Rust/tipos con respuestas concretas.

Frases criticas por slide:

  • Slide 19: What Rust Gives Us / Answer to Question 1: fail early. / fail cheap
  • Slide 20: The compiler check as Pre-Validator / Answer to Question 3:
  • Slide 21: The Human Impact / When the system is trustworthy:
  • Slide 22: Continuous C I slash C D. / Types. / compiler check. / Explicit state.
  • Slide 23: In Production / This is not theory

Regla de enfasis:

  • Tecnico, pero aterrizado a impacto operativo.

B6 - Proof in Production (Slides 24-31)

Tiempo objetivo bloque: 08:32

Objetivo: Probar con casos reales e impacto operativo.

Frases criticas por slide:

  • Slide 24: Provisioning architecture (visual) / One source of truth, typed end to end.
  • Slide 25: Nickel / YAML rejected. / TOML rejected. / Reason: no type safety.
  • Slide 26: Traits as Provider / The kitchen can change. / AWS ≠ UpCloud ≠ bare metal. / Same menu.
  • Slide 27: Dependency Graph / Failfast: bool is not a config option.
  • Slide 28: Real Applications / Kubernetes + validators in production conditions.
  • Slide 29: Disaster Recovery / Rollback as a type. / not a procedure
  • Slide 30: Self-Healing / When something breaks at 3 AM, the system responds first.
  • Slide 31: Without types. / Without compiler check. / Without explicit state. / MTTR > 30 minutes.

Regla de enfasis:

  • Menos teoria, mas evidencia: MTTR, DR, 3AM.

B7 - Close & CTA (Slides 32-35)

Tiempo objetivo bloque: 02:39

Objetivo: Cerrar con mensaje memorable y accion.

Frases criticas por slide:

  • Slide 32: Why This Matters / For everyone in this room
  • Slide 33: For You / If you've been frustrated like me
  • Slide 34: I have perspective from long production experience. / I have seen technologies come and go.
  • Slide 35: Why I Needed Rust / Three Closing Lines

Regla de enfasis:

  • Baja ritmo y cierra con conviccion.

Checkpoints Rápidos

  • 05:00 -> deberias estar en Slide 6
  • 10:00 -> deberias estar en Slide 12-13
  • 15:00 -> deberias estar en Slide 18-19
  • 20:00 -> deberias estar en Slide 24
  • 25:00 -> deberias estar en Slide 29-30
  • 30:00 -> Slide 35 (end)