📓 "Teorema del cuaderno": cómo una intuición guardada durante años terminó abriendo una nueva capa de infraestructura para IA.
Con @andresmac73, Director & Founder de SEMQ.
📓 "Teorema del cuaderno": cómo una intuición guardada durante años terminó abriendo una nueva capa de infraestructura para IA.
Con @andresmac73, Director & Founder de SEMQ.
¿El próximo gigante de la tecnología es argentino? 🇦🇷 De Pergamino a Silicon Valley: la historia de Andrés Macallister y cómo su "Teorema del Cuaderno" está revolucionando la Inteligencia Artificial. 🧠✨
Optimización de datos, ahorro de energía y una startup que ya está en la mira de Google y Meta. ¡Mirá cómo el talento nacional sigue liderando el mundo! 🚀
https://t.co/2FI1khsOVk
#Argentina #IA #Tecnologia #Emprendedores #AndresMacallister #CiudadanoNews #Mendoza #Innovacion
El teorema del cuaderno: el emprendedor argentino que guardó una idea durante quince años y hoy impresiona a Silicon Valley | Por Fernanda Jara https://t.co/DpJy8r6GVv
@simplifyinAI ACE is interesting because it turns learning into incremental state updates instead of weight updates.
But then everything depends on how that state is encoded. If the representation is inefficient, the system keeps patching instead of truly accumulating...
@ubrmnschn@PI010101 But there’s an interesting separation here, what helps gradients isn’t necessarily what’s needed to store the learned structure. High dimensionality may be useful to find the solution but redundant once you have it.
I think AGI isn’t just the ability to approach new tasks, it’s the ability to retain structure while doing so. Humans don’t start from scratch every time, they carry forward stable internal representations that make new learning cheap.
Current systems still re-derive too much of their state instead of building on it...
@patrickc@karpathy We’re getting close to “infrastructure as code for agents.” The next step is “state as infrastructure”, otherwise agents will keep rebuilding what they already did...
Feels like the hard part isn’t just orchestration but state continuity. Each step (auth, deploy, debug,etc) depends on a shared understanding that currently lives in fragile prompts and logs.
I think that until that state becomes stable and persistent, agents will keep re-deriving context instead of building on it...
@rryssf The interesting pattern here is separation of concerns.
Rollout vs training is one example. Representation vs compute might be another.
@thesemqgroup is exploring this layer...
@bingxu_ Blind coding shifts the bottleneck from humans to representation.
Once agents explore 24/7, the question is no longer who searches but how big the space they search is.
Most of that space is probably redundant...