Cecilio Alvarez @arquitectojava

friend just sent me this, it's wild how AI is changing companies: "coworker sent a 20-page AI-generated planning doc for a huge meeting later today i didn't want to lose my job, so i asked claude to write a 50-page required pre-reading for the meeting not to be outdone, the coworker fed that into Claude and replied with a 1,000-page summary of the pre-reading i finally won out with a 100,000,000 page document that broke our email system" lesson? if you've made it this far, you're a true 10x AI-pilled vibe coder. you don't need to learn anything more. you've done it. congrats

Building Reliable AI Agents with Java and LangChain4J? Join Susanne Pieterse , LangChain4J contributor for a hands-on workshop on building reliable AI agents in Java with evaluation, guardrails, and observability built in. here is the link - eventbrite.co.uk/e/building-rel… Use code JAVA50 to get 50% OFF

@oinu_koinu_13 Claude: I fixed all files, they are bug free. Me: Log in button doesn't work. Claude: You're right! Let me check files....Checking... You've hit your limit...

It’s hard to measure directly, but my sense is that agents increase my productivity by a factor of five. And the output of the agents is far more tested and far more robust than I could ever hope to achieve. The code I write myself might be more elegant, but nowhere near as hardened.

Lo que se está cargando el open source y mucho más que está por venir (como bien sabemos) es el pensar que la IA te hará código si no hay criterio detrás. Se resume muy fácilmente: si tienes ni idea, estate quietecito majo y no subas PR de lo que ni entiendes por hacerte el listo.

The agents cannot see the screen, and cannot tell the difference between things that work in the tests, and things that appear on the screen. Therefore, QA testing through the UI is necessary. This can be automated by the agents. UI testing is very fragile because the UI is the most volatile part of the system. It changes for lots of reasons. This used to put pressure on us to avoid testing through the UI since all those tests would become as volatile as the UI. Agents are workhorses. They don't care about rewriting the UI tests. So that pressure has shrunk appreciably. It is now much more feasible to create, and maintain, a good UI test suite. I'm cautious about this, but I also see no alternative.

Our most precious commodity is human time. If I can save one man day by using a gigabyte then, nowadays, that’s a good trade. I grew up in an era where memory was vastly more precious than human time. We were forced to conserve bytes so intensely that we trimmed the first two digits of the year from our dates. We all knew this would lead to trouble in 25 years; but we had no choice. Those two bytes were the difference between success and failure.

@sivalabs The more instructions you have in claude, agents, skills md files, and the more MCP integrations, the more tokens you will burn for simple tasks. I found that crafting a prompt is still the most convenient way to get what you want.

Previously we used to worry about developers simply copying code snippets from StackOverflow without understanding it. Now developers are copying a whole bunch of Agent Skills, AGENTS.md, CLAUDE.MD files without even taking a look at what is inside just because they have many stars on those GitHub repos. Yesterday I was reviewing someone's Java project and the repo has around 70 agent skills added and most of them has Node.js based "conventions and best practices". 🤯 Keep it minimal and only add necessary agent skills.

Guide to Subagent Orchestration in Spring AI buff.ly/waVq462

I met an engineer friend for coffee yesterday who told me he’s getting ready to QUIT Software. He’s a mid-level dev, incredibly smart, but completely burnt out by the doom-scrolling! He said, "Look at the 2026 data, man. Active tech openings are down to a multi-year low. Entry-level hiring has dropped nearly 20%. Eric Schmidt is out here telling everyone traditional coding is dead, and tools like Claude Code can resolve half our production bugs autonomously. What is even the point of trying to compete with a machine that works for pennies?" He genuinely believed the popular consensus: The machines are over, so human developers are obsolete. I let him finish, took a sip of my coffee, and told him he was completely misreading the room. Yes, the market is restructuring. Yes, companies are trimming the fat. But they aren't firing people because they want less software. They are firing the the people whose entire value proposition was copy-pasting boilerplate, writing routine unit tests, and manually building CRUD apps. Look at what happened to the senior engineering market. Demand for system architects, infrastructure specialists, and platform engineers is actually holding strong. Why? Because when it costs zero dollars to generate 10,000 lines of code, you don't need fewer engineers. You need better engineers to make sure that mountain of synthetic code doesn't blow up your production server. I told him: "Two years ago, your value was looking up syntax and type. Today, your value is your judgment. Can you break down a messy business problem into concrete technical constraints? Can you look at 5 different architectural patterns an AI suggests and weigh the cloud token costs against technical debt? Can you audit a script and spot the logic flaw before it hits production?"  Laying bricks is cheap now. Designing the building is where the money is. If you are thinking about quitting tech because "AI can code," you are giving up right at the exact moment the boring parts of your job are being automated away. Don't quit. Upgrade your cognitive stack. Move from a coder to a conductor.

Sam Altman's new interview: AI should not be designed to pursue goals that are disconnected from human needs. People must remain at the center of AI development. “I have no interest in building a super-smart AI that accomplishes some non-human goals. People should react. People should say, ‘Hey, this is what I want, and this is what I do not want.’ I do not think the issue is that we have failed to explain the benefits. We say, ‘AI is going to cure a bunch of diseases,’ and people say, ‘Okay, that is great, but that is not really my question. My question is: What is my role in the future? What is my economic future? What is my agency? How do I know that my kids and my family will still be able to have fulfilling, creative expression, struggle, drive the world forward, grow, and do this thing together in a way that has worked for a long time?’ When people in AI say, ‘Sure, there are going to be no jobs,’ or ‘50% of jobs are going to go away,’ or ‘90% of jobs are going to go away,’ and ‘AI is going to be smarter than you at everything,’ and ‘We will give you some basic income, but you are not really going to have a role,’ that is horrible. And by the way, if an AI company says, ‘Maybe we are going to destroy all the jobs, and we will be the most valuable company in the world,’ people should look at you like, ‘Yeah, that is a terrible message.’ I do not think the problem is that we have not articulated the upsides. I think people actually believe us. They hear, ‘AI may cure your cancer,’ and they think, ‘That sounds great.’ I think we, as an industry, have failed to explain how people stay in control of determining the future at every step, and how people can still have a meaningful life in all the ways we care about.” ---- From "CNBC Television" YouTube channel, (link in comment)

Ayer. El padre de mi amiga, 80 años, vasco en Palencia, cae y se abre la cabeza. Traumatismo craneoencefálico, hemorragia y traslado urgente en ambulancia al hospital provincial. —¿Qué medicación toma? —No estoy segura, ¿no puede mirarlo usted en su historia clínica? —No; no tenemos acceso. Literal. Yo sé que hay un proyecto del SNS para compartir la historia clínica entre los servicios autonómicos de salud. He leído memorias e informes sobre eso. He utilizado el servicio HCDSNS. Pero, ¿en el hospital de Palencia no pueden consultar la historia de un paciente de Bilbao? El hombre, inconsciente, postrado en una camilla, y el médico no puede acceder a su historia clínica. ¡Qué puñetera vergüenza de país! Le hacen pruebas y analíticas. Días después, mi amiga gestiona un transporte urgente en ambulancia hasta Bilbao. Pero necesita llevar a Osakidetza los resultados de las pruebas médicas —varios TAC, analíticas…— que hicieron a su padre en Palencia. Dicen que no lo pueden enviar por correo electrónico. Dicen que no se lo pueden guardar en un pendrive. Al final le guardan los resultados… ¡en un puñetero CD-ROM! Llega ayer mi amiga agotada y angustiada a mi casa —en Santander—, desde Palencia, pidiéndome leer el CD-ROM del Servicio de Salud de Castilla y León (SACYL) para enviarlo por email al médico del Servicio Vasco de Salud (Osakidetza) y después salir corriendo otra vez en coche hacia Bilbao. De verdad, ¡idos todos a la mierda!

David Bonilla @david_bonilla

6 days ago

De viaje en Valladolid, a mi suegro se le ha movido un stent y tienen que hacerle un cateterismo, pero no pueden acceder a su historial médico, gestionado por el Sergas gallego. Como si estuviera en un país extranjero. No sé como alguien puede justificar este disparate.

383 2K 8K 837K 115

Introduction to Caffeine: buff.ly/c1qHBvU

El estado actual de las empresas que hacen despidos por IA 🤣🤣 Fuente : Mindless_Bid_5448 (Enlace abajo)

In 1995, a small team of engineers unveiled a new programming language designed for flexibility, portability, and robustness. That language was Java. And three decades later, it remains one of the most influential technologies in the software world. Thank you for helping us celebrate #30YearsOfJava this past year. We look forward to many, many more years of pushing the boundaries of innovation and the pursuit of developer excellence. ❤️

That's how programming feels nowadays

Una empresa ha gastado 500 millones USD en un mes por no haber puesto límites al uso de IA para sus empleados. ¿Qué empresa sería?

Modern Concurrency in Java @java @bazlur_rahman