
Hablo de tecnología, inteligencia artificial, Arquitectura de Software También me puedes seguir en mi perfil dedicado a Experiencias Blockchain en @duberblock
Colombia
Joined December 2009
- Tweets1.2K
- Following1K
- Followers258
- Likes213
Pinned Tweet
Porque si lo ves, lo crees.
Y si lo crees, lo creas.
Así nace una plataforma donde las ideas se transforman en procesos, y los procesos en automatización inteligente.
⚡ Estamos construyendo el futuro… paso a paso.
(esta es mi señal de: "En construcción") 🚧
Duberney Lopez Piza retweeted
#SinManos 6/20 | Te prometieron un Jarvis y te entregaron un loro.
Cuando un sistema dice «Listo», ¿terminó un paso o se hizo cargo de la tarea?
En la sexta edición: qué trabajo vale la pena delegar y cómo comprobar que se hizo.
linkedin.com/pulse/de-predec…
Duberney Lopez Piza retweeted
Coincidences Magnified - Are We Under Attack?
I will preface this with the humility that I might be totally wrong and all these recent events really are some type of coordinated cyber-attack, although I would say if it is it’s all rather pointless and unfocused. But, I doubt this is really an “attack” in any way. However, just because you’re paranoid doesn’t mean that they are not really out to get you.
No, the most likely explanation of what is going on is:
1. Fragility of increasingly large-scale and under-maintained, complex and brittle infrastructure.
2. Our increased digital dependence such that when these events happen we notice them more.
3. A few independent incidents coincidentally occurring together which causes the media and the rest of us to be more attuned to other outages that would normally go unreported, that we now bucket into some mythologized growing category.
4. Lack of resilience in the presence of failures so that their impact is longer-lasting and more impactful.
Let’s pick on a few of these. First, independent occurrences of events that seem to be connected. One example I remember was a day many years ago when the New York Stock Exchange was down for the day (software error), a US airline was ground stopped (hardware event), and on the same day a bunch of major bank CISOs, including me, were going into the White House Situation Room for a totally unrelated threat briefing (we had to hide from the White House Press Corp in case that was further coincidental evidence of “attack on America”.) After this I looked at what else happened that was unreported that day and there were dozens of other unrelated outages at hospitals, power plants, and so on. Perhaps even more happened that one day than has been happening this past week. It just went unreported.
Second, do we have any base rate data to understand if what of anything that has happened is actually so unusual or surprising? [Note: something being unsurprising doesn’t mean it’s acceptable, in fact we want such events to become ever more surprising of course].
- Microsoft outage: yes, this was unusually big, but a Microsoft outage isn’t a new occurrence. (Other large-scale tech providers have outages also, to be fair to Microsoft).
- FAA outage: maybe this was a minor change to one of 1000’s of cables that had previously been fine that had some weird accidental effect they’d not seen before hence this wasn’t the situation of “why do a production change on a Friday?” Organizations do changes all the time that they think are distant from impact risk. Perhaps this was like that. But it does seem their network should not have been so brittle in the face of this. I guess we will find out.
- NSA Net outage: do you know how many times NSA Net goes down per year? I don’t. But perhaps NSA Net isn’t a literally 100% available system (most things aren’t [literally], even stupendously critical things), so perhaps this was still within their four or five 9’s SLO. Perhaps it goes down several times a year but we just don’t normally hear about it. I don’t know, most of everyone else doesn’t either.
The list could go on.
The thing that should be disturbing to us though is the point on resilience.
I really worry when things like this happen together or in isolation and our response is: “This [bad thing] must never happen again.” and the organizations involved, sometimes when compelled to, make that system less likely to break. Then we build up more dependence on it, but again it will inevitably break in some new way for some other reason and the damage will be bigger because that increased confidence induced more dependence, because we all said “this must never happen again.”
The real lesson here is that we need to not just build resilience to failure in specific components but resilience in the overall “system”, like let’s always assume FAA comms may go down albeit at some increasingly low probability and have a true back-up emergency communications approach to at least sustain some operations. Maybe they’re working on this, I don’t know. And make sure that critical industrial systems don’t depend on alerts only being delivered by cloud-based email.
I’ll start where I began. It will be darkly funny if I’m wrong and this really is a set of related attacks. But when you look at how much breaks regularly everywhere all the time, I doubt it.
The actual need here is to reduce brittleness and increase resilience on the assumption that everything will always fail in some way at some time.
Duberney Lopez Piza retweeted
¿Y si el problema ya no fuera generar más código, sino tomar mejores decisiones antes de programar?
Google propone algo interesante con Elephant-Goldfish Model: diseñar, especificar y cuestionar antes de implementar.
Mi reflexión y sus 3 fases:
linkedin.com/feed/update/urn…
Duberney Lopez Piza retweeted
Octubre es el mes de la ciberseguridad, pero hacía años que no veíamos tambalear los cimientos de internet de esta manera. Hay tanto por contar que un tuit se queda corto. Abro hilo. 🧵👇
Duberney Lopez Piza retweeted
Deploying DiffusionGemma-Jev (djev) just got a lot easier. You can now spin up a Jev API-compatible endpoint on Google Cloud Run using a single command.
Performance is solid: ~35-60 ms for single step latency and batch@32 is ~100-123 requests/sec.
It's a straightforward way to experiment without needing your own GPU. Runs at roughly $3/hr and drops to $0 when idle.
Get the code and instructions here: github.com/taeold/djev-run
#Jev está a punto de absorber una parte enorme de la lógica de negocio del planeta en cuestión de días. Y no estoy seguro de que todos dimensionemos lo que eso significa.
1
37
Jev is the "Internet" moment for the AI industry
It tells your agents and LLMs what to do next, in milliseconds and at almost zero cost
If you set it up correctly, you will have the AI engineer’s stack for 2028
In this article, I show you how
Yo no le tengo miedo a la #IA (generativa, clásica o agéntica).
Le tengo miedo a un "humano" que le coloca un arma a un dron y deja que lo controle un LLM, a ese señor, si que le tengo mucho miedo
#Mickey, #Goethe y el #vibecoding tienen más en común de lo que parece.
La tecnología nos da cada vez más poder. El reto es desarrollar el #criterio para saber usarlo, detenerlo y responder por sus consecuencias.
linkedin.com/feed/update/urn…
𝗡𝗼 𝗺𝗲 𝗱𝗶𝗴𝗮𝘀 𝗾𝘂𝗲 𝗹𝗼 𝗵𝗶𝘇𝗼. 𝗗𝗶𝗺𝗲 𝗾𝘂𝗲́ 𝗺𝗼𝘃𝗶𝗼́.
Una de las mejores ideas que he visto sobre Ingeniería Agéntica:
Más código, tokens o agentes ≠ más valor.
Mide outcomes, no actividad.
linkedin.com/feed/update/urn…
#AgenticAI #AIEngineering
#OpenAI cambió las reglas para crear y compartir #GPT en cuentas personales.
Después de usarlos desde noviembre de 2023, hoy me encontré con el cambio de primera mano.
La lección: el GPT no debería ser el activo. La capacidad debe ser portable.
linkedin.com/feed/update/urn…
23
Si vas a invertir en #IA Generativa, no empieces por la herramienta.
Antes responde 4 preguntas:
1
66
#ai No siempre falta contexto.
A veces sobra #contexto sin criterio.
Un #agente útil no necesita recordar más: necesita saber qué sigue siendo cierto ahora.
Compartí el documento completo en PDF aquí:
linkedin.com/feed/update/urn…
🤖 Made with AI
1
1
94
Lo que empieza a importar no es solo recuperar información, sino entender:
⚫ Qué sigue vigente.
⚫ Qué fue reemplazado.
⚫ Cuándo cambió una decisión.
⚫ De dónde salió cada afirmación.
⚫ Qué relación existe entre personas, decisiones, documentos y eventos.
1
9
GStack, de @garrytan, muestra una señal interesante: pasar del prompt vacío a un flujo guiado con skills y comandos para Claude Code.
Menos prompts sueltos.
Más proceso para trabajar con agentes.
Repo: github.com/garrytan/gstack
#SinManos
49
Duberney Lopez Piza retweeted
En el Día de la Madre de 2023 tomamos esta foto. (la versión real)
Ese año había nacido Susana.
Y al verla, apareció una canción.
𝗟𝗮 𝗳𝗼𝘁𝗼 𝗾𝘂𝗲 𝘀𝗲 𝘃𝗼𝗹𝘃𝗶𝗼 𝗰𝗮𝗻𝗰𝗶𝗼𝗻
Así nació Flor de Cuatro Tiempos.
En OpenCode funciona porque hago que funcione, en PI funciona por que le digo que funcione. Thanks @badlogicgames
















