Me escribió @juansotoivars: «Te llamo y comentamos». Y yo me pensé que sería un telefonazo breve para preparar la entrevista y grabarla otro día, con tiempo. Pero no; Juan quería improvisar. «A calzón quitado», me dijo.
Casi, casi reculo, pero decidí confiar y nuestro improvisado diálogo ya va más de 200 000 vistas en 24 horas.
Leo en los comentarios del canal que está gustando mucho. Cuánto me alegra. ☺️❤️👇
https://t.co/bCsmxUaPZY
the most import skill in 2026 is still being able to tell your agents "wtf is this crap, no, not like this"
if you stop doing that, you're basically fucked, despite what some devfluencers would like you to think.
Background subagents in Claude Code now use less of your usage limit.
A running subagent updates its status line every 30 seconds, and each update used to re-read its whole conversation. Now Haiku 5.5 writes it from short notes instead, so each update costs about 99% less.
¡Qué sorpresa, estimado Juan! Mil gracias por la invitación.
Hay mucha gente encantada con la idea, y yo también. Además de interesante, sería un rato muy divertido. Llevaré mi enciclopedia de tecnodispendios y ciberñapas. 😂
¡Y propuestas! Que España tiene solución. Somos el país de Elcano, Pérez del Pulgar y Aller Ulloa, «el milagro de Lalín». 💪
Te he escrito en privado. ¿Nos ponemos en marcha? 🥳
Sugerencia @oscar_puente_ saca una especificación para un proyecto OpenSource, lo tienes en 1 mes y nos ahorramos todos los 3M que le vais a dar a Indra...
Yes. AI agents work best with clean code. That is a given. Either you know how to do it, or you will suffer (and pay way way more tokens than you should for suboptimal results, and you will think it's a matter of changing LLMs)
Full explanation on Clean Code for AI:
https://t.co/iEwe3U0PJb
Experience gives perspective. Programming is not dead, and never will be.
It's late September 2026. Sometime in September 1976, just after I entered college, I wrote and ran my first serious program. I have now been a programmer for literally 50 years.
And man, I have seen it *all*. Punched cards to glass ttys on minicomputers to workstations to the earliest micros. I've written business software, communication programs, development tools, games, language implementations, kernel device drivers, graphics libraries, a few critical pieces of infrastructure, and all manner of odd programs for which there is no taxonomy. Coded in a score of languages some of which are now forgotten. I've run over 70 open-source projects and contributed to at least as many more.
Along the way I noticed a few things, and wrote about them, and that made me famous. But I'm not here to write about that today. I'm here to write about what it means to be a programmer and a technologist with the Singularity upon us.
I have lost count of the number of times I have been told "programming is over". You kids may think this is a new claim that came into the world with LLMs. Hah! There's been that kind of talk at every step function in the quality of our programming tools. I first heard it when compilers were replacing hand-hacked assembler in the early 1980s, and I wouldn't be a bit surprised if somebody said it earlier when in-memory code replaced plugboards.
One constant amidst all this change is that the intentions in a user's head do not magically turn into executable instructions that a computer can run. Another constant is the mindset of the people who specialize in bridging the gap between wish and algorithm. A programmer is a programmer is a programmer - the tools are secondary.
"But it's different this time!" some people will say, "AIs are superhuman now!" So? What did you think the optimization stage of a compiler was, chopped liver? We've been relying on tools that exceeded human capabilities all along - we built them precisely because our meatbrains could not otherwise keep up with the demands of the job.
It's been a hell of a ride, that 50 years. I've succeeded and failed and succeeded again. Done a lot of work I'm proud of. Built at least a few things that look like they're going to last. None of that goes away because, hypothetically, an AI might have made me faster.
The work is never done, even if the tools can talk to us now. Because intentions still have to be communicated; people who specialize in that and develop right mindset to do it still have a major advantage over people who don't.
If you're feeling depressed because you spent years or decades developing hand-coding skills that are obsolete now? Buck up. You still have the most important asset - a mind that knows how to think that way.
I'm facing the winds of the Singularity with a smile. Because 50 years and I'm still standing - still shipping code that people can use, still learning, still refusing to be paralyzed by the pace of change.
The best therapy for your uncertainty? Get to work on something.
There's nothing kind about letting good people live in a fantasy world that no longer exists. You have to tell them, even if it hurts. Because the sooner they accept reality, the sooner they can adapt to the future.
The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage.
I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care.
But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently.
For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios.
But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.
Your job may be surviving on inertia. Your resentment won’t extend the runway. What do you actually want to do with the intelligence now at your disposal? https://t.co/vikawjCmZD
I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.
We're adding support for AGENTS.md to Claude Code.
Starting today in version 2.1.277, if there is no CLAUDE.md in a folder, Claude will check for and use AGENTS.md.
You can toggle this behavior in /config.
A crucial skill when developing with AI is to know which "bugs" to tackle or ignore.
Because AI models will *always* find "bugs". You can run 10 cycles of code reviews, they will still find something.
That includes false positives BUT also *a lot* of esoteric, niche issues that will likely never matter for what you're building.
For example, I find that Astra loves to find weird pretty made up racing conditions like "if you bulk import emails and after the first 10 records were written, an email address changes, it will silently overwrite it". Stuff like that.
Which may never matter for what you're building.
If you just let AI review + blindly accept its findings and let it fix those findings, you'll just start adding layers of complexity and turn your codebase into a mess.
Don't let that happen. Use your brain, use your understanding of what you're building - don't outsource your thinking.