Luis Pablo

Software engineer and technology advocate

[Santi Torres @SantiTorAI]

Linus Torvalds acaba de dejar claro que Linux no va a convertirse en un basurero de código generado por IA.

Después de meses de debate interno, la comunidad Linux publicó sus reglas oficiales sobre el uso de herramientas como GitHub Copilot.

El veredicto: se puede usar IA para programar, pero el "slop" ese código de baja calidad escupido sin pensar, no pasa el filtro.

La frase que lo resume todo: "Los humanos asumen los errores."

Puedes apoyarte en Copilot, en Claude, en lo que quieras. Pero si ese código entra al kernel de Linux, tú eres el responsable.
Tú lo verificas. Tú corriges los fallos. Tú garantizas que cumple los estándares.

Es la postura más madura que he visto en el ecosistema open source frente a la IA. Ni histeria, ni adopción ciega. Solo responsabilidad clara.
El kernel tiene 30 años de historia.

No lo van a arruinar por ahorrar 20 minutos con un autocomplete.

[Luis Pablo @luispablo]

@consumerxai farming

[An Nayal @consumerxai]

ok fk it, I’m giving this away.

over the last 4 weeks, we built a system to take any product from raw research → production-ready ad system.

inside, I’m sharing how we create:

• avatar sheets
• offer briefs
• necessary belief docs
• project instructions
• claude project setup
• hooks
• scripts
• storyboards
• primary text
• static ad prompts
• kling / seedance video prompts

all built on foundational marketing principles:

-> Agora lineage
-> Eugene Schwartz’s 5 levels of awareness
-> Schwartz’s 5 stages of market sophistication
-> The Tina Effect

FOR FREE‼️

because we’re still early to ads, still testing, still learning, and I’d rather share the art while it’s raw.

once we perfect it, it goes behind a paywall 🫡

comment “farming” + RT and I’ll send you the playbook

lfg 🔥

[Luis Pablo @luispablo]

@manulpz4 ¿Y no sería más fácil usar envbee, y olvidarte de las env variables…? https://t.co/EWJ1LrJavY

[Luis Pablo @luispablo]

@IntCyberDigest Better use envbee! — https://t.co/EWJ1LrJavY

[Luis Pablo @luispablo]

@igus_ai Deberían usar https://t.co/EWJ1LrJavY !!

[envbee @envbee_dev]

Is your production held together by a .env file and a prayer? 🕯️

Config drift and "copy-paste culture" are the silent killers of R&D velocity.

https://t.co/eX4PDThZ7V

#DevOps #Backend #SoftwareArchitecture #buildinpublic

[Peter Girnus 🦅 @gothburz]

My company rolled out AI tools 11 months ago. Since then, every task I do takes longer.

I am not allowed to say this out loud.

Not because there is a policy. There is no policy. There is something worse than a policy. There is enthusiasm.

There is a Slack channel called #ai-wins where people post screenshots of AI outputs with captions like "this just saved me an hour." There is a VP who opens every all-hands with "the companies that adopt fastest win." There is a Director who renamed his team from Operations to Intelligent Operations. There is a peer review question that now asks: "How have you leveraged AI tools to enhance your workflow this quarter?"

If the answer is "I haven't, because I was faster before," that is a career decision.

So I leverage.

Emails.

Before the tools, I wrote emails. This took the amount of time it takes to write an email. I did not measure it. Nobody measured it. The email got written and sent and it was fine.

Now I write the email. Then I highlight the text and click "Enhance with AI." The AI rewrites my email. It replaces "Can we meet Thursday?" with "I'd love to explore the possibility of finding a mutually convenient time to align on this." I read the rewrite. I delete the rewrite. I send my original email.

This takes 4 minutes instead of 2. The 2 extra minutes are the enhancement. I do this 11 times a day. That is 22 minutes I spend each day rejecting improvements to sentences that were already finished.

In #ai-wins I posted a screenshot of the rewrite. I did not post the part where I deleted it. 23 people reacted with the rocket emoji.

That is adoption.

Meetings.

We have an AI notetaker in every meeting now. It joins automatically. It records. It transcribes. It summarizes. After each meeting I receive a 3-paragraph summary of the meeting I just attended.

I read the summary. This takes 3 minutes. I was in the meeting. I know what happened. I am reading a machine's account of something I experienced firsthand. Sometimes the account is wrong. Last Tuesday it attributed a comment about Q3 revenue to me. My manager made that comment. I spent 4 minutes correcting the transcript.

Before the notetaker, I did not spend 7 minutes after each meeting correcting a robot's memory of something I personally witnessed. I attend 11 meetings a week. That is 77 minutes per week supervising a transcription nobody requested.

I mentioned this once. My manager said "think about the people who weren't in the meeting." The people who weren't in the meeting do not read the summaries. I checked. The read receipts show single-digit opens. The summaries exist not because they are useful but because they are there. I read them for the same reason.

Documents.

I write a weekly status update. Before the tools, this took 10 minutes. I typed what happened. I sent it. My manager skimmed it. The system worked.

Now I open the AI writing assistant. I give it my bullet points. It produces a draft. The draft says "Significant progress was achieved across multiple workstreams." I did not achieve significant progress across multiple workstreams. I updated a spreadsheet and sent 4 emails.

I rewrite the draft to say what actually happened. Then I run my rewrite through the grammar tool. It suggests I change "done" to "completed" and "next week" to "in the forthcoming period." I click Ignore 9 times. Then I send the version I would have written in 10 minutes. The process now takes 30.

I have been doing this every week for 11 months. I have added 20 minutes to a task that did not need 20 more minutes. I call this efficiency. I have been calling it efficiency for 11 months. That is what efficiency means now. It means the additional time you spend to arrive at the same outcome through a longer process. Nobody has questioned this definition. I have not offered it for review.

I kept a log once. 2 weeks. Every task, timed. Before-AI and after-AI. The after number was larger in every case. Every single one. Not by a little. The range was 40 to 200 percent.

I deleted the log.

I deleted it because it was a document that said, in plain numbers, that the AI tools make me slower. And a document like that has no place in a company where AI adoption is a strategic priority. I could not send it to my manager. He championed the rollout. I could not post it in #ai-wins. I could not raise it in a meeting because the notetaker would transcribe it and the summary would read "[Name] expressed concerns about AI tool efficacy" and that summary would be the first one anyone actually reads.

So I do what everyone does.

I use the tools. I spend the extra time. I post in #ai-wins. I write "leveraged AI to streamline weekly reporting" in my review and my manager gives me a 4 out of 5 for innovation. I have innovated nothing. I have added steps to processes that were already finished. I have made simple things longer and labeled the difference with words that used to mean something.

Every week in #ai-wins someone posts a screenshot. And 20 people react with the rocket emoji. And nobody posts the part where they deleted the output and did the task themselves. Nobody posts the revert. Nobody posts the before-and-after timer. Nobody will. Because "I was better at my job before the AI tools" is a sentence that cannot be said out loud in any company that has decided AI is the future.

Every company has decided AI is the future.

So we leverage. Quietly. Adding steps. Calling them optimization. Getting slightly less done, slightly more slowly, with slightly more steps, and reporting it as progress.

My yearly review is next month. There is a new section this year. "AI Impact Assessment." It asks me to quantify the hours saved by AI tools per week.

I will write a number. The number will be positive. It will not be true.

But the AI writing assistant will help me phrase it convincingly. That is the one thing it does well.

[Luis Pablo @luispablo]

I just published Moving Beyond Static Environment Variables: The Case for Dynamic, Typed Configuration https://t.co/UHG2Tw0lYv

[Luis Pablo @luispablo]

@envbee_dev We strongly believe in treating software configuration as a first-class citizen!

[envbee @envbee_dev]

Most production outages aren't caused by bad code.

They're caused by bad configuration.

.env files don't scale in modern systems.

Here's why 👇
https://t.co/QQFmmuARGy

[SCORE Mentors @SCOREMentors]

FEBRUARY WEBINAR SCHEDULE — Swipe through to learn more about this month's sessions. 👉

We hope you enjoy this month’s line up and look forward to seeing you at an upcoming event!

[Luis Pablo @luispablo]

Don't ever use @fedex for international purchases in Argentina. It's been the worst experience ever.

[Luis Pablo @luispablo]

El tránsito es una pesadilla gracias al “boom” de gente que vino. Los lunes por la mañana la ruta va a paso de hombre.

[Luis Pablo @luispablo]

¡Por favor no compren las mentiras de las notas pagas de este diario! Vivo acá hace 8 años y es una pesadilla, no veo la hora de irme. https://t.co/5h6E50Ke9n

[Luis Pablo @luispablo]

Las pocas calles asfaltadas que hay están destruidas. Cuando llueve si no tenés una camioneta se limita mucho donde podés acceder.

[Alan Daitch @AlanDaitch]

Apple acaba de publicar un paper con un título demoledor: *The Illusion of Thinking*. Y no es metáfora. Lo que demuestra es que los modelos de IA que usamos todos los días —sí, tipo ChatGPT— no piensan. Ni un poco. Solo imitan que lo hacen.

Te explico: 🧵👇

[Luis Pablo @luispablo]

@KagiHQ Assitant is now available to all users! -- https://t.co/m1M7WJNgdk 🥳🥳

[Nicolás Morás @nicolasmorasok]

Desmonetizaron mi hermoso documental sobre el Milagro paraguayo y el plan maestro para convertirse en potencia.
No duró ni 24 hs monetizado. De todas formas, por primera vez en años no pienso retirarlo. Hice este trabajo a pérdida, por amor y gratitud al país que más felicidad me ha dado.
Es mi aporte para el proyecto de la despenalización, que es una oportunidad histórica única para resolver los principales problemas que todavía existen allí en forma definitiva.
Me sorprendió ver a tantas personas que manifiestan
en los comentarios su voluntad de mudarse e invertir en Py gracias a este informe.
Me doy por pagado si me ayudan a difundirlo lo más posible. ¡Dale RT!
https://t.co/gy1OgZFRH8