fighting slop with slop — Vaibhav Gupta, Boundary

AI Engineer

Summary

Vaibhav presenta las prácticas de ingeniería no convencionales de su equipo, como la ausencia de revisiones de código, para construir un lenguaje de programación estable llamado BAML. Explica cómo "combaten el slop" (código no leído o de baja calidad) con más "slop", es decir, creando herramientas impulsadas por agentes que automatizan la comprensión, el diseño y la verificación del código. Destaca BAML como un lenguaje diseñado desde cero para agentes, abordando la gestión de errores y la interoperabilidad, y propone una revisión fundamental de las herramientas y lenguajes actuales para alcanzar la "velocidad de agente" en el desarrollo de software.

Chapters

  1. 0:00Introduction to "Slop"
  2. 1:27Fighting Slop with Tools
  3. 4:40Agent-Driven Code Trust
  4. 7:10Inherent Language Slop
  5. 9:16Agent-First Tooling Paradigm
  6. 14:56First Principles Error Handling
  7. 17:27Bridging ML with Languages
  8. 20:00Conclusion: Embrace Future Slop

Topics covered

  • Prácticas de ingeniería no convencionales
  • Definición y combate del 'slop'

+8 more topics (full content when you follow the channel)

Transcript excerpt

[music] >> Fighting slop with slop. My name is Vaibhav and I'm going to talk about something that is a little I would say maybe a little silly at first. I'm going to show you our team's engineering practices really quickly. We do no code reviews. We require every engineer to work on things in parallel. And we have no standardization on how people do AI. And I know immediately what almost all of you are thinking. We're probably a Zoomer YC startup. And I can guarantee you I'm clearly a millennial. So what do we actually do at our company without code reviews? Well, we built about 3 years ago we decided to build a programming language. That's something that has absolutely no room for slop. It's something that has to work every single time exactly the same way. It's something that you can't just change a year later or a month later because you made a bad design decision. You have to be corr…