Juanma

Más ingeniero que artesano. No soy fanático de ninguna tecnología, intento hacer las cosas bien, ser práctico y aplicar el sentido común.

[Juanma @gulnor]

Y con sólo un interface, una factoría, un contenedor de inversión de control, inyección de dependencias y una pizca de reflection te puedes evitar ese IF que hace tu código tan difícil de mantener.

[Rick @rickasaurus]

If only we had some kind of system that knew about the shapes of the values and functions in a codebase.

[Edu Ferro (eferro) @eferro]

Hoy publico mi primer libro: «Menos software, más impacto». Da un poco de vértigo.
La tesis: tu equipo no va lento por escribir mal código. Va lento porque escribe código de más. 🧵

[Julio César Pérez @jcesarperez]

Edu es todo un referente en Lean, Agile y XP.

Tenemos la suerte de que ha escrito un libro con su propuesta sobre cómo desarrollar software de forma efectiva y en español.

Un libro realmente muy bueno que yo he tenido el honor de leer durante la edición

[Juanma @gulnor]

"En la era de la IA, el canal de venta/distribución pesa más que el producto".

En realidad, siempre ha sido así, pero como crear producto* en la era de la IA es más accesible, hay más gente consciente de esto.

--
* Ahora producto es una maqueta.

[Juanma @gulnor]

"Si una IA se rompe, la pongo en otra máquina y funciona igual. Si mato a un humano no puedo ponerle en otro cuerpo y que sea igual".

- Mi hija de 9 años haciéndome pensar.

[Juanma @gulnor]

@Rafael_Casuso Estoy contigo, me genera rechazo.

Incluso un email que han pasado por la IA para "revisar el tono y la gramática" me resulta desagradable y prefiero el original con sus defectos.

[Juanma @gulnor]

@__josejuan__ Lo de la cerveza me ha recordado al Ballmer Peak 😅

[Daniel Martín González @danimart1991]

Con todo este movimiento de producir con IA a niveles nunca vistos, este artículo de @gulnor del 2012: "Razones para cuidar la calidad: tu" ha envejecido como el buen vino. La IA debería servir para producir mejor, NO para producir más.

https://t.co/zO0Z1PfSPz

[Mitchell Hashimoto @mitchellh]

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.

I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).

It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.

The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.

We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.

I worry.

[Juanma @gulnor]

Buena visión.

Pensar que tienes controlado el código escrito por IA porque está bien cubierto por tests es absurdo. Yo he escrito código perfectamente testeado que era un infierno mantener y que aportaba poco a nivel de negocio.

El código importa, pero el contexto más.

[Mitchell Hashimoto @mitchellh]

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.

I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).

It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.

The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.

We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.

I worry.

[Juanma @gulnor]

@jm_alarcon Había leído WinAmp CLI y me había hecho más ilusión.

[Juanma @gulnor]

@DaveRosa82 Sí, esas que siguen contratando las administraciones públicas.

[Juanma @gulnor]

Cl@ve Móvil fallando, errores internos mostrados al usuario (con el potencial riesgo de seguridad)...

Nada que sorprenda de la administración pública, la verdad.

[José M. Alarcón Aguín 🌐 @jm_alarcon]

Este genio de Michigan sentó las bases de la era digital. Sin sus descubrimientos sobre el álgebra booleana y los circuitos, no tendrías un ordenador en tus manos ahora mismo y tu IA favorita se llamaría "Darío" y no "Claude": https://t.co/VInyI55Ys9

[Juanma @gulnor]

"Su arquitectura elegante y poderosa [del PDP 10] de los años 60 no podía adaptarse de forma natural a los grandes espacios de direccionamiento característicos de los años 80".

[Juanma @gulnor]

@Montyclt @Rafael_Casuso Sin duda. Pero los que las rescatan son políticos.

Y eso nos lleva al inicio de la conversación y al sistema de incentivos perversos que decía Rafa.

[Juanma @gulnor]

@Rafael_Casuso @Montyclt En toda organización es difícil vencer la inercia, y cuanto mayor es la organización, más difícil es cambiar los sistemas de incentivos.

En empresas, llega un punto en que no son capaces de adaptarse, quiebran, y son reemplazadas por otras.

Que no es por ser agorero, pero...

[Dustin @r0ck3t23]

Mark Cuban just described the largest wealth transfer of the AI era.

Almost nobody understood what he said.

Cuban: “There are 33 million companies in this country. Aren’t going to have AI budgets. Aren’t going to have AI experts.”

Not tech startups.

The shoe store. The regional trucking outfit. The accounting firm with 12 employees.

The businesses that actually run the physical economy.

They know AI is coming. They have no idea what to do with it.

Cuban: “You’ve got the head of Microsoft saying software is dead because everything’s going to be customized to your unique utilization.”

Software is dead.

The SaaS era ran on one rule. Build a generic product. Force millions of companies to bend their workflows around it. Charge rent forever.

AI ends the contract.

The business stops bending to the software. The intelligence bends to the business.

But customized by whom.

The third-generation manufacturer cannot tell Claude from Gemini. The county hospital is staring at a reactor asking where the light switch is.

Cuban: “Who’s going to do it for them?”

That question is worth more than the frontier models themselves.

Hundreds of billions are being burned to build the foundation. The smartest engineers alive are locked in a bloodbath over who owns the base layer.

Let them fight.

Let them burn the capital. Let them drive the cost of raw intelligence toward zero.

Because the wealth does not collect where the brain is built.

It collects where the brain meets the business.

Every ambitious kid in college right now thinks survival means a seat at OpenAI or Anthropic.

Cuban is staring at the other 99 percent of the economy.

Learn the models. Then learn the messy, unglamorous reality of how a 50-person company actually operates.

Walk through the door. Understand their problems. Wire the intelligence directly into their revenue.

That is not a job title. That is an entire economic class being born.

You do not need to build the brain. You need to build the nervous system.

The biggest winners of the electricity era were not the engineers who built the generators. They were the ones who walked into dark factories and showed the owners where to plug in.

33 million companies are standing in the dark right now.

Silicon Valley is racing to build the god. The fortunes will belong to whoever teaches him a trade.

[Felix ❤️‍🔥 @pilgoth]

I hate, hate, hate being forced to watch a video to learn something when I could read at 10x the speed. Videos are for cattle.

"Hey guys, today we'll be talking about X -- X is a fascinating topic, and a lot of you have been requesting I talk about X, so..." - Shut up, Shut up!

[Pablo R. (Root Rat) @root_rat]

https://t.co/CD2XdPVeb0