Agustin Gomes

Me after watching FP2 today: 🤔🫩🫣🤬🫤 Also me setting my alarm at 06:50am on a Saturday to watch F1 qualy:

@dani_juncadella Same mate, same 🥲

if your data is stored in a database that a company can freely read and access (i.e. not end-to-end encrypted), the company will eventually update their ToS so they can use your data for AI training — the incentives are too strong to resist

@thestanduppod Straight to r/LinkedInLunatics 😂

LinkedIn Translator

@asmah2107 @anuraggoel We still do, though. Unless the plan is to make the agents accountable for decisions. Would love to see how that ends up going.

@anuraggoel The entire ceremony of modern software development was scaffolding for human cognitive limits. Are we saying agents don't have those limits ?

AI is quietly deprecating GitHub. Agents do not need branches, PRs, or CI/CD rituals. They want to ship code straight to the cloud. The rsync renaissance is here. High availability. Zero bloat. Faster loops.

@anibal @antirez Chamath pretendiendo dar lecciones sobre software development 😂

Team @antirez aquí, y el detalle es clave: "at the current state", eventualmente (y estamos cerca, whatever that means) los modelos/coding assistants/coding systems van a llegar a un punto donde la diferencia desaparece; pero aún no estamos ahí.

Eduard Bazardo. Firmó su primer contrato profesional en 2014 por apenas 8.000 dólares. Un número que para muchos no decía nada… pero el talento no siempre viene con etiqueta de precio. Porque no, no tienes que firmar por millones para convertirte en un gran pelotero. Bazardo se abrió camino con trabajo. Debutó en Grandes Ligas el 14 de abril de 2021 con los Red Sox, y en Venezuela lo hizo en 2022 con Magallanes. Paso a paso. Sin ruido. Sin atajos. Hasta que llegó su gran oportunidad. En 2025, con Seattle, tuvo la mejor temporada de su carrera: 5-0, 2.52 de efectividad, 82 ponches en 78.2 innings, 1.8 de WAR, un dominio absoluto desde el bullpen Ese nivel lo llevó directo a representar a Venezuela en el Clásico Mundial. ¿Y respondió? 2.70 ERA 5 juegos 3.1 innings 2 hits 1 carrera 2 ponches 0 boletos Simplemente, cumplió. Eduard Bazardo es la prueba de algo que muchos olvidan: el bono no hace al pelotero. Lo hacen el trabajo diario, la constancia, la resiliencia… y una mentalidad que no entiende de límites.

"Díganlo muy alto y con enorme orgullo. Que retumbe en todos los rincones del país: Venezuela es el campeón del Mundial de Béisbol 2026". Para quienes crecimos viendo nuestra pelota con @arreazaortega narrándola, este es el relato de nuestras vidas:

Living his best life 😭🇻🇪

@sondraa Venezuela

Who is winning - USA vs DR Italy vs Venezuela

@edul3on Vamos coño!!!

ohtani quien te conoce

@kunchenguid @GergelyOrosz This is one of the things I missed from the time I used HipChat. Good times.

@GergelyOrosz We use “+++” in slack to give each other karma as a way to recognize/celebrate. The replies are just a bot confirming the karma is received.

My question, looking at this screenshot, is: 1. What is "Atlassian Karma" 2. Why is it replying to every single message? 3. What is Buzzkill Mode??

@GergelyOrosz HipChat used to have something like that. Funny to see something similar in Slack

@anime_ This episode is peak comedy

Gintama is a top tier comedy anime 😭

From my inbox Wrong: Most AI coding output is not mediocre because the tool was not well co figured: It’s mediocre because most code out in the open IS mediocre, and (most importantly) most devs don’t know how to write high quality code. And this was true even before AI!!

JUST IN: Study finds AI use at work leading to "cognitive overload" and burnout.

@thdxr AWS is full enterprise enshittification. Completely unusable for normal people nowadays, they've dropped the ball.

@HedgieMarkets You know what? Serves them right as a lesson. AI sure can be valuable, but it also has exacerbated the bottleneck: lack of how the underlying systems work.

🦔 Amazon is holding an engineering meeting Tuesday for a "deep dive" into a spate of outages, including incidents tied to AI coding tools. An internal memo seen by the Financial Times cited a "trend of incidents" with "high blast radius" and "Gen-AI assisted changes" among contributing factors, along with "novel GenAI usage for which best practices and safeguards are not yet fully established." Junior and mid-level engineers will now require senior sign-off on any AI-assisted changes. This follows Amazon's website going down for nearly six hours earlier this month, and at least two AWS incidents linked to AI coding assistants, including the December outage where the Kiro AI tool decided to "delete and recreate the environment" during a fix attempt. My Take Amazon has been aggressively rolling out AI coding tools while cutting 16,000 corporate jobs in January, and now they're requiring senior engineers to review AI-assisted changes, which raises an obvious question about who's left to do that reviewing after the layoffs. Multiple engineers have reportedly said their teams are dealing with more "Sev2" incidents requiring rapid response since the cuts. Amazon disputed that headcount reductions caused the outages, but someone has to understand the systems well enough to catch AI mistakes before they take down the site for six hours, and that institutional knowledge walks out the door with every layoff. I wrote about the AWS Kiro incident back in December when Amazon called it "user error" because the engineer gave the agent broader permissions than intended. But someone always has to decide what permissions to grant, and if AI behaves unexpectedly within those permissions, blaming humans doesn't prevent it from happening again. Now we're seeing the same dynamic play out across Amazon's retail infrastructure, and the solution is more human oversight of the AI tools that were supposed to reduce the need for humans. Hedgie🤗

Amazon had four Sev-1 outages (their highest severity level) in a single week. Internal memos say AI-assisted code changes were a contributing factor. The timeline here is wild. In October 2025, Amazon laid off 14,000 corporate employees. In January 2026, another 16,000. That’s about 30,000 people in five months, roughly 10% of the corporate workforce. CEO Andy Jassy said the cuts were about culture, not AI. During those same months, Amazon set a target: 80% of developers using AI coding tools at least once a week. They tracked adoption closely and blocked rival tools like OpenAI’s Codex. Even so, 30% of developers still hadn’t touched Amazon’s in-house tool Kiro by January. In December 2025, Kiro caused a 13-hour AWS outage. The AI tool had production-level permissions and decided the best fix for a bug was to delete and recreate an entire live environment. A second incident involved Amazon Q Developer, another AI tool. Amazon blamed both on “user error, not AI.” But quietly added mandatory peer review for all production access afterward. Then March 5: Amazon’s retail site went down for about six hours. Over 22,000 users reported checkout failures, missing prices, and app crashes. Amazon called it a “software code deployment” error. Five days later, SVP Dave Treadwell made the normally optional weekly engineering meeting mandatory. His memo acknowledged “GenAI tools supplementing or accelerating production change instructions, leading to unsafe practices.” These problems trace back to Q3 2025. Amazon’s own assessment: their GenAI safeguards “are not yet fully established.” The new rule: junior and mid-level engineers now need senior sign-off on any AI-assisted production changes. Treadwell also announced “controlled friction” for the most critical parts of the retail experience. For context, Google’s 2025 DORA report found 90% of developers use AI for coding but only 24% trust it “a lot.” An Uplevel study of 800 developers found Copilot users introduced 41% more bugs with no improvement in output. Amazon is finding out what those numbers look like at the scale of a $500 Billion revenue company, with 30,000 fewer people on staff to catch the mistakes.