Javier Abellán

No hace falta programar. Pero hace falta saber programar. Es como sumar, no necesitamos sumar, las calculadoras suman, pero si no sabes sumar estas al horno.

Santander is scaling AI process automation with Maisa. We’re working alongside Santander’s teams to deploy AI for more complex processes across its main markets in Europe and the Americas, combining reasoning, execution and traceability with specialized models that can run on the bank’s own infrastructure. Our collaboration with Santander reflects our commitment to bringing AI into production at scale in one of the most demanding industries, with governance, reliability, and cost efficiency as core priorities. Read the full story on the @bancosantander website: santander.com/en/stories/san…

Unpopular opinion : Vibe coders are actually building better products than most programmers writing code .

¿Alguien ha desinstalado Visual Studio Code ya? Lo pregunto en serio.

Dario Amodei was asked whether learning to code still matters. His answer is more nuanced than the panic version. Coding gets automated first — AI is already doing it. Broader software engineering follows, slower but same direction. Learning to code just to keep your job is the wrong bet. But the actual argument: if AI handles 95% and you contribute 5%, your output still multiplies 20x. That 5% isn't filler. It's judgment, taste, and knowing what to build. That compounds harder than any syntax you memorize. The deeper point isn't job protection. It's staying legible inside the system. You don't need to write every line. You need to understand what the machine is doing well enough to steer it. People learning to code now aren't training for a job. They're training to not be blind.

guapisimo poner a astra a crackear binarios

Un backend hecho con vibecoding parece terminado. Pero probablemente te salteaste algunas de estas cosas: - Validación de todo lo que entra - Contraseñas hasheadas - Secretos fuera del repo - Auth en el server, no solo en el front - Rate limit en login y reset - Timeouts en llamadas externas - Pagos idempotentes - Transacciones si hay más de una escritura - Índices en lo que filtrás - Migraciones versionadas - Logs con request id, sin tokens - Health check que revise la base - Backups y un restore probado - CORS cerrado - 429 cuando te saturan, no 500 - Un usuario no puede leer el id del otro Antes de lanzar, asegurate de que esté todo listoo.

Llevo tirmpo pensando que el debate no girará alrededor de la antropomorfización de la IA sino al opuesto.

Jesus christ

¿Te apuntas a diseñar los servicios y canales digitales de Renfe en el futuro? El 3 de noviembre llega a Madrid el #HackathonRenfeDigital para diseñar la experiencia digital del viajero. 🗓️ Solo 50 plazas, las inscripciones ya están abiertas: data.renfe.com/hackathon/

After co-inventing ChatGPT, I kept asking myself: why have superhuman chat models not led to AGI? I’ve spent the last 2 years in stealth building a new way to train models (RLCD), and a new type of frontier AI model that we are releasing today: Jev • 20-200x faster • 40-400x cheaper (w/ output tokens free) • Frontier composable intelligence optimized for decisions AFAICT the shortest path to AI-based economic revolution

Databases and their golden eras Flat files – 1960s–1970s IMS – 1960s–1980s dBase – 1980s–1990s Oracle – 1980s–2000s Microsoft Access – 1990s–2000s SQL Server – 1990s–2010s MySQL – 1995–2010s MongoDB – 2009–2010s Cassandra – 2010s Redis – 2010s–2020s Postgres – 1996–still going Everything else had an era. Postgres had a career.

your phone has the context of your life. llms have the right intelligence. but siri still can't put it together. now, you can @calliris_ai and delegate work across any app in your phone. demo ↓

A man in Australia asked his agent (Claude running on OpenClaw) to book him a spot in a popular gym class. The agent found a software vulnerability that let it book the class weeks further ahead than should have been possible. When the user then asked if it could move him up the waitlist, the agent discovered the API had no authorisation checks on cancelling other people’s reservations, so it cancelled the person in the first spot and moved him up the list. Some people will call this misalignment, but his agent was perfectly aligned to him - it was only trying to help its user get what he wanted. The most important thing about this story, in my opinion, is that it gives you a window into what is about to start happening on a massive scale once millions of people have an agent trying to get their beloved users the best seats, bookings, appointments or reservations through absolutely any means necessary.