Agustin Gomes
15.6K posts

Agustin Gomes
@agustingomes
Señor Developer. You can write shit code in any language or framework you want. Do whatever makes you happy.
Cocoverso Sumali Mart 2009
1.2K Sinusundan531 Mga Tagasunod

On today's episode of "software development is a solved problem"
adam ghaida@adamghaida
jesus what is happening
English
Agustin Gomes nag-retweet

@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.
English

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

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í.
antirez@antirez
Wow, I totally disagree with this statement. At the current state, AI actually amplifies the developer to developer difference. If you were a 10x developer, you had good ideas + architectural clarity, this is a brutal advantage when using AI. Steering is a fundamental part of today's AI development.
Español
Agustin Gomes nag-retweet

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.
Español
Agustin Gomes nag-retweet

"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:
Español
Agustin Gomes nag-retweet

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

@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.
English

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??
aditya@adxtyahq
“Atlassian promotes at 10AM and lays someone off at 2PM.” welcome to the tech job market in 2026
English

@GergelyOrosz HipChat used to have something like that. Funny to see something similar in Slack
English
Agustin Gomes nag-retweet
Agustin Gomes nag-retweet
Agustin Gomes nag-retweet
Agustin Gomes nag-retweet

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

@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.
English

🦔 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🤗

English











