Galo Navarro

2.5K posts

Galo Navarro banner
Galo Navarro

Galo Navarro

@srvaroa

Solving business problems with software - Building GPU infrastructure & AI workload orchestration @midokura - Distributed systems / software delivery / cloud

Europe Katılım Mayıs 2010
767 Takip Edilen606 Takipçiler
Sabitlenmiş Tweet
Galo Navarro
Galo Navarro@srvaroa·
Code reviews are not sustainable
Galo Navarro tweet media
English
1
0
2
180
Galo Navarro
Galo Navarro@srvaroa·
AI systems, at all levels of the stack (infra and workloads, both training / inference) are complex versions of distributed systems, each with very different constraints and trade-offs
Galo Navarro tweet media
English
1
0
0
28
João Alves
João Alves@joaoqalves·
@srvaroa Indeed. I’ve seen many people refusing to open obvious incidents due to their own definition of it. But my point is that if your manager asks for it, nothing good comes out discussion about “well, technically it’s not an incident because …”
English
1
0
1
47
João Alves
João Alves@joaoqalves·
ProTip(tm): if your manager says something should be declared an incident, just do it. No one will remember if then it wasn’t. But if it was and you dragged your feet, you’ll get a “non dependable / accountable” medal.
English
1
0
3
246
Galo Navarro
Galo Navarro@srvaroa·
@gimenete @flopezluis El discurso de la artesanía ya estaba muy cogido con pinzas cuando se puso de moda, ahora es marciano. Lo curioso es que es impermeable a la evidencia que dan otras docenas de campos de la industria humana a lo largo de siglos..
Español
1
0
0
91
Alberto Gimeno
Alberto Gimeno@gimenete·
@flopezluis Incluso se ha hablado mucho de “artesanía/artesanos de software”. Son personas que han invertido además muchísimo tiempo en debatir e invertir en aspectos que en mi opinión de la noche a la mañana se han vuelto prácticamente irrelevantes
Español
3
0
10
1K
Galo Navarro retweetledi
Jessica Kerr
Jessica Kerr@jessitron·
Stripe’s observability team wrote an agent to help respond to incidents. “Some early quick wins made us think it would be easy. It wasn’t” - Rob Miles, Mike Cowgill #o11ycon
English
2
8
86
24.4K
Galo Navarro retweetledi
Adam
Adam@adamdotdev·
I talked about this on the standup podcast yesterday, but I'll reiterate here: if you're losing sleep because you need to keep feeding the agents STOP, I promise it's not worth it. You got caught in a [prompt -> reward] dopamine cycle and you're addicted to the feeling of the token slot machine. It's not your fault, but you need to escape before it grinds you into a pulp and you can't look at a computer for a month (this was me). If you can break out of it and spend some more time offline, or find other healthy sources of dopamine in hobbies/etc, you'll start to realize just how warped your perception was and that the thing you were chasing wasn't actually productive.
TFTC@TFTC21

Marc Andreessen on JRE: AI hasn't replaced coders. It turned them into vampires. "The opportunity cost of going to sleep is too high because if you go to sleep, you won't be with your 20 AI coding agents."

English
62
92
1.1K
111.7K
Galo Navarro retweetledi
All About Berlin
All About Berlin@aboutberlin·
AI is killing All About Berlin. When you Google something, you used to get a link to my website, but now you get an AI-generated answer trained on my work. This has a devastating impact on traffic.
All About Berlin tweet media
English
285
1.1K
10.1K
1.3M
ℏεsam
ℏεsam@Hesamation·
“managers shipping with AI, fleets of agents, one-person AI pods, leverage AI across every facet of our jobs” I don’t know this sounds like a recipe for data leaks and vulnerability disasters
Brian Armstrong@brian_armstrong

This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian

English
8
9
192
22.5K
Galo Navarro retweetledi
Jaana Dogan ヤナ ドガン
Do I know anyone who is interested for a senior+ PM role to work on highly ambitious distributed systems problems in agentic workloads? Deep experience in ML/AI systems and container orchestration is preferred. If you are an engineer looking for a PM pivot, this could be for you.
English
12
15
143
23.4K
Galo Navarro retweetledi
Gajus
Gajus@kuizinas·
There is a surge of supply chain attacks (and it is only going to get worse) If you are using pnpm, take these steps to protect yourself: * set minimumReleaseAge to 7 days * set blockExoticSubdeps to true * configure onlyBuiltDependencies npm / yarn have similar settings
Socket@SocketSecurity

🚨 We’ve confirmed the intercom-client@7.0.4 was compromised in the ongoing Mini Shai-Hulud worm attack. The npm package includes a malicious preinstall hook that downloads and executes an unverified Bun binary, then runs an 11.7 MB obfuscated payload designed to steal Kubernetes, Vault, cloud, GitHub, and CI/CD secrets. The attack closely overlaps with the SAP CAP, Cloud MTA, and lightning@2.6.2 compromises.

English
13
65
716
141.5K
Galo Navarro
Galo Navarro@srvaroa·
@vboykis Building became cheaper, hardening and long term maintenance less so.
English
0
0
0
45
vicki
vicki@vboykis·
I don’t buy the idea that libraries will go away since everyone can just write their own now. Maybe for small internal company use-cases. But libraries are not just code, they’re time invested in edge cases, they’re hundreds of hours of human eyes. I don’t want to replace that.
English
33
36
306
17.7K
Galo Navarro
Galo Navarro@srvaroa·
@JosuGoi1 @flopezluis No digo que no existan casos donde sirva. Digo que si queremos hablar (ver inicio del hilo) de algo que aplica al 99% de empresas necesitas cubrir un mínimo de disponibilidad y otras cosas. Y “nah, tenemos backups” doesn’t cut it
Español
1
0
0
17
Galo Navarro
Galo Navarro@srvaroa·
@JosuGoi1 @flopezluis Si te sirve correr un servicio en una máquina siempre es mejor. Ahora bien, no, un servicio que necesita disponibilidad y resiliencia no tiene bastante con backups.
Español
1
0
0
14
Félix López
Félix López@flopezluis·
Bendito ruby si te permite llega a dónde ha llegado github. 99.9% de las empresas de software no van a tener problemas que ruby no pueda resolver
Español
5
4
51
8.8K
Galo Navarro
Galo Navarro@srvaroa·
@JosuGoi1 @flopezluis El punto de distribuir carga viene impuesto por la necesidad de resiliencia bastante antes que el límite de rendimiento de cualquier lenguaje. Y en cuanto distributes carga, lenguajes de menos rdto son menos problemáticos porque puedes escalar horizontalmente.
Español
1
0
0
23
Josu Goñi
Josu Goñi@JosuGoi1·
@flopezluis @srvaroa Hay un punto dulce en el que con una sola máquina (mas algún servicio como BBDD o CDN) con el lenguaje correcto das el mismo servicio que con un sistema mucho más complejo. Pasado ese punto (y tiene tela) ya nadie te salva de tener que distribuir carga.
Español
1
0
0
58
Galo Navarro
Galo Navarro@srvaroa·
@Jongonzlz El tema con extrapolar efectos de lo individual a lo colectivo no se acaba de pillar. Una acción puede tener sentido a nivel individual (e.g. hay fuego, corre) pero no tenerlo a nivel colectivo (e.g. avalancha de gente corriendo a la salida de incendios).
Español
0
0
0
385
Gergely Orosz
Gergely Orosz@GergelyOrosz·
WOW. Mitchell Hashimoto voting with his feet: Ghostty is leaving GitHub. "I can't code with GitHub anymore. I'm sorry. After 18 years, I've got to go. I'd love to come back one day, but this will have to be predicated on real results and improvements, not words and promises."
Mitchell Hashimoto@mitchellh

Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. mitchellh.com/writing/ghostt…

English
32
33
1.2K
152.5K