Jax London 26

 

Wed 07.10.2026

1. Welcome and Opening Keynote of JAX London 2026
   Sebastian Meyen
   
   
2. Worth a Million Arguments
   Venkat Subramaniam (prototype!)
   
   
3. Low Latency Machine - Can Generative AI Write High-Performance Code?
   Mark Price
   
   
4. Four Green Ticks – Yet Still Hacked: Threat Modelling for AI Agents
   Christian Schneider
   
   
5. Security in the Age of AI – Ask the Expert
   Charles Weir
   
   
6. Small Signals, Big Incidents: Catching Production Problems in the Performance Lab with JFR & AI
   Ram Lakshmanan
   
   
7. Building Agentic AI with Small Language Models — Locally and Efficiently
   John Davies| Incept5
   
   
8. Build Your Own Private AI Cluster for the Office
   John Davies| Incept5

Thr 08.10.2026

1. AI and the Future of Enterprise Software
   Rod Johnson| Embabel
   
   
2. Create Your Own Role-Playing Game with Agentic AI Using Spring AI
   Arnaud Jean| AWS
   
   
3. Architecture Observability in Agentic Engineering
   Victor Rentea| Independent Trainer
   
   
4. AI Literacy for Developers: Thinking Clearly While AI Writes the Code
   Russell Miles| TechTalk
   
   
5. Trade-Offs Are Everything: Non-functional Requirements For the AI Era
   Eoin Woods| Artechra
   
   
6. A2UI & MCP-UI: Agent-Driven Interfaces
   Diego Ligtenberg| Rabobank
   
   
7. Patterns and Anti-patterns of Agentic Engineering
   Victor Rentea| Independent Trainer

Fr 09.10.2026

1. Agentic Engineering Workshop: Building Secure, Autonomous AI Agents and Multi-Agent Systems in Production
   Victor Rentea| Independent Trainer

https://www.youtube.com/@JAXLondonCon

 

Musa al-Khwarizmi

Nombre de Algoritmo!

Musa al-Khwarizmi

Gauss Billete

Billete antiguo de marcos alemanes del principe de las matematicas Carl Friedrich Gauss.

 

Rüpü

Del mapudungun:

 

Camino, senda, vía.

 

https://es.wiktionary.org/wiki/r%C3%BCp%C3%BC

 

Alan Turing Billete

Un homenaje del Banco de Inglaterra al poner a Alan Mathison Turing en el billete de 50 libras esterlinas.

 

Outbox Pattern

TL;DR

Primero insertar dato en base datos y desde ahi (message relay) publicarlo en cola.

The Transactional Outbox Pattern is a crucial architectural design pattern used in microservices to ensure reliable message publishing to Apache Kafka. It solves the dual-write problem, which occurs when a service tries to update its local database and send an event to Kafka at the same time.

Because databases and Kafka cannot share a single distributed transaction, a network failure or application crash right after the database commit means the Kafka event is lost forever. The outbox pattern completely eliminates this risk by leveraging the atomicity of local database transactions.

 

https://developer.confluent.io/courses/microservices/the-transactional-outbox-pattern/

https://www.decodable.co/blog/revisiting-the-outbox-pattern

https://microservices.io/patterns/data/transactional-outbox.html

Ley de Brooks

La Ley de Brooks afirma que añadir más personal a un proyecto de software retrasado hace que se retrase todavía más. 

Este principio fue acuñado por Fred Brooks en su libro clásico de 1975, The Mythical Man-Month (El hombre-mes mítico), basándose en su experiencia al dirigir el desarrollo del sistema operativo OS/360 en IBM. Como resumen de su idea, Brooks popularizó la frase: "Nueve mujeres no pueden tener un bebé en un mes".

Este es uno de las leyes mas basicas que ocurre en desarrollo de software donde la gente no involucrada en la fabrica tienden a confundirse.

Ahora surge el fenomeno de la IA... habria que ver con este nuevo approach.

Historia de las APIs

Siempre existen conversaciones de APIs, desde el boom de los microservicios se le dice coloquialmente APIs donde se refiere por default a API Rest o Web API, sin duda, los mas senior solo piensan en la API de C, C++, Java, etc.

Dicho esto es simpatico cuando aparece por primera vez ese termino.

Todo apunta que fue en:

• AFIPS Spring Joint Computer Conference: Data Structures and Techniques for Remote Computer Graphics, I. W. Cotton y F. S. Greatorex Jr., 1968

Finally, hardware independence at the central computer means that a consistent application program interface could be maintained if that computer were replaced...

Ademas, los siguientes libros y presentacion hablan mas de la historia de las APIs:

• A Brief, Opinionated History of the API, Joshua Bloch (InfoQ, 2018) 
• Building an API Product Design, implement, and release API, Bruno Pedro, 2024
• Enterprise API Management, Luis Weir, 2019
• Learning API Styles_ Understanding the Trade-Offs of Common, Lukasz Dynowski & Marcin Dulak, 2025

TL;DR

Sigue usando API para cosas modernas estilo API Rest, y ponle el adjetivo si quieres hablar mas claro de otro tipo de APIs, como:

EDSAC subroutine library, FORTRAN libraries, IBM System/360 interfaces, Application Program Interface (1968), Unix system calls, C Standard Library, POSIX API, MS-DOS API, Macintosh Toolbox, Windows API, Xlib, RPC, OpenGL, CORBA, Java API, SOAP Web Services, .NET API, REST APIs, GraphQL, gRPC.
 

Algorithm Recreational Programming

Newsletter de inicio de los 90s que es como la continuacion del articulo de Scientific American que desde matematicas recreativas paso a programacion recreativa.

Amdahl’s Law

Amdahl’s Law can be expressed mathematically as follows:

$$ \mathrm{Speedup}_{\max} = \frac{1}{(1-p) + \frac{p}{s}} $$

• SpeedupMAX = maximum performance gain
• s = performance gain factor of p after implementing the enhancements.
• p = the part whose performance needs to be improved.

Let’s take an example. If the part that can be improved is 30% of the overall system and its performance can be doubled, then:

$$ \displaystyle \mathrm{Speedup}_{\max} = \frac{1}{(1-0.30)+\frac{0.30}{2}} = 1.18 $$

Oregon State University — Amdahl’s Law

If you buy a system with n cores, you should get n times Speedup (and 100% Speedup Efficiency), right? Wrong! There is always some fraction of the total operation that is inherently sequential and cannot be parallelized no matter what you do. This includes reading data, setting up calculations, control logic, storing results, etc.

Tutorialspoint — What is Amdahl’s Law?

Wikipedia — Amdahl’s Law

La Ley de Amdahl dice que el rendimiento total está limitado por la parte del sistema que no podemos acelerar.