Diego Sapriza

12.2K posts

Diego Sapriza banner
Diego Sapriza

Diego Sapriza

@AV4TAr

Husband and father of 4. SVP Engineering @playbypoint, ex-Director of Engineering @WeWork, XOPS, former XOPS, @WeWork, @case_inc Optimizing for collaboration.

CA, USA Katılım Kasım 2008
449 Takip Edilen935 Takipçiler
Diego Sapriza retweetledi
Gaston Milano Millan
Gaston Milano Millan@GMilano·
Ayer estuve conversando con estudiantes avanzados de ingeniería y licenciatura en sistemas de UDELAR y ORT. Fue una de esas charlas que, más que responder preguntas, te obliga a repensar qué es lo importante decir. No porque falte información sino porque estamos en un momento donde es fácil confundirse sobre qué significa realmente “estar preparado”. Vi talento, curiosidad, ganas de salir a hacer. Y al mismo tiempo, una sensación muy presente: ¿ya debería estar trabajando?, ¿qué debería estar aprendiendo?, ¿en qué enfocarme en medio de tanto cambio? Ahí fue donde me salió una reflexión casi inevitable. No desde la teoría, sino desde contraste. Porque cuando yo estudié, el mundo era radicalmente distinto. No había internet, no había web, no había celulares, no había SaaS. Ni siquiera había una GUI usable como la de hoy. Hasta cuarto de facultad no tuve computadora propia. Programaba en papel. Literal. Llené cuadernos enteros antes de poder ejecutar una línea. Y sin embargo, o quizás por eso, aprendimos algo más importante que cualquier tecnología: aprendimos a aprender. La universidad, en su esencia, no está para enseñarte herramientas. Está para darte estructuras mentales. Matemática. Probabilidad. Arquitectura. Sistemas operativos. Cómo escribir código, sí —pero como forma de pensar, no como fin. Ahora, para los que sienten que ya están listos para trabajar: Tienen razón… pero ojo con interpretar mal qué significa eso. La industria cada vez va a necesitar menos “coders” (entendidos como personas que traducen requerimientos a código). Pero ingeniería nunca fue eso. Entonces, ¿qué hacer? Primero: entiendan que el mundo está lleno de problemas. Y en lo digital, está lleno de problemas mal resueltos. Segundo: acérquense a esos problemas. Hablen con la gente. Escuchen. Entiendan el contexto real. Con gente que quizás tienen más cerca de lo que piensan. Tercero: incorporen lo nuevo, pero con criterio: •entiendan lo básico de Generative AI •construyan su primer agente •comprendan sistemas distribuidos •lean algo de robótica •aprendan UX (arquitectura, interacción, visual) Cuarto: salgan de su burbuja. Hablen con gente de otras facultades. Los problemas reales no vienen separados por carreras. Y quizás lo más importante: No se enamoren de herramientas. El ecosistema cambia. Siempre. Enamórense de problemas. Después de uno. Después de otro. Tienen algo que muchos perdemos con el tiempo: tiempo para explorar. Úsenlo. Porque si realmente aprenden a aprender, esta no va a ser “la revolución de su carrera”. Va a ser la primera de muchas. Si llegaste hasta acá , gracias , realmente lo escribí yo y lo formateo y acomodo ChatGPT , espero les sirva. By the way en la Charla si usamos varias cosas de moda Claude, Gemini, OpenAi , SeeDance, Sumo y Eleven, Clawds y otras, pero nada de eso fue la esencia .
Español
6
21
126
10K
Diego Sapriza retweetledi
boris
boris@boristane·
I'm back nominal.dev
English
97
72
979
194.7K
Bryan Migliorisi
Bryan Migliorisi@BryanMigliorisi·
Not sure why I've never seen this before but having Claude Code desktop app run an embedded chrome browser, control it, take screen shots is an incredible feature that helps it debug things even more quickly.
English
2
0
0
35
Diego Sapriza retweetledi
Jared Friedman
Jared Friedman@snowmaker·
Software engineering changed more in the last 3 months than the preceeding 30 years. Everything about running a software company needs to be rethought from first principles.
English
355
714
6.8K
540.2K
Diego Sapriza
Diego Sapriza@AV4TAr·
@BryanMigliorisi Yeah, it's very useful for testing/validation. It can record GIFs, too, if you ask for it.
English
1
0
0
16
Diego Sapriza
Diego Sapriza@AV4TAr·
@Minucha01 @frascafrasca Lo que yo recomiendo a los gurises es arrancar urgente a usar IA para armar cualquier proyecto. Es una herramienta como cualquier otra y este es el momento de aprender (está verde). El ecosistema de AI es muy complejo: hablar con chatgpt para hacer algo es la punta del iceberg.
Español
0
0
3
70
Minu
Minu@Minucha01·
@frascafrasca Y ahora que hace mi hijo programador junior que busca trabajo ? Terminó hace poco y realmente le gusta 🥺
Español
4
0
0
1.5K
Gonzalo Frasca
Gonzalo Frasca@frascafrasca·
Desde hace un año que tengo varios proyectos de software que intento realizar usando IA. Invariablemente, la IA encontraba un problema que no podía solucionar. Entonces, esperaba unos meses a que saliera un mejor modelo y avanzaba un poco más. Esta semana, luego de un año de
Español
9
15
88
26.3K
Diego Sapriza retweetledi
Vadim
Vadim@VadimStrizheus·
POV: February 2026
Vadim tweet media
Slovenščina
111
659
5.1K
153.1K
Diego Sapriza
Diego Sapriza@AV4TAr·
Learning: Do your agent stuff in a tmux session to prevent your terminal from closing and losing your work. #auch
English
0
0
0
22
Guillermo Rauch
Guillermo Rauch@rauchg·
The new engineering is building the agents that "take your job", but now do it at 100x the scale. Agents give developers horizontal scalability. The simple version of this is Ghostty splits and tabs, 𝚝𝚖𝚞𝚡 sessions and the like, running CLI agents in parallel. Skills and MCPs help you direct the behavior of these agents. Sandboxes give the ultimate leverage: ~infinite parallelism, run while you sleep, on PRs, when an incident is filed, a customer reports an issue… Automating the full product development loop is now your job, and your edge.
Guillermo Rauch tweet media
Naval@naval

Vibe coding is the new product management. Training and tuning models is the new coding.

English
105
108
1.9K
174.2K
Diego Sapriza
Diego Sapriza@AV4TAr·
Having ADD while running multiple agents feels like hosting 7 meetings in your own brain. Everyone needs something. Nobody waits for their turn. I opened Slack and forgot why. #vibecoding #agents #fun #add
English
0
0
0
30
Diego Sapriza retweetledi
@marty
@marty@marty·
every tech guy you know working on their @openclaw "productivity" system right now
English
83
274
2.7K
204.4K
Thiago Ghisi
Thiago Ghisi@thiagoghisi·
After 3 months of intense Claude Code usage on Obsidian putting all my second brains across all my areas of life together into a single MD repo, I just officially pulled the trigger on @openclaw.
Thiago Ghisi tweet media
English
3
0
11
2.7K
Diego Sapriza retweetledi
Thiago Ghisi
Thiago Ghisi@thiagoghisi·
What are the Recurring Expectations for Achieving Staff-Plus Level Across Tech Companies, and Where do Senior Engineers Most Often Fall Short? These are the 3 things I found that, if you do consistency, will make you golden as a Staff-Plus Engineer at pretty much any company. These are also the 3 most common expectations I have seen across the board for Staff Engineers. And by coincidence or not, these are also the 3 things I've seeing struggling Senior Engineers completely neglecting or being completely unaware of. Here is my answer based on my last 8 years of experience on the Management track both as an EM and as a Director. 1️⃣ Blast radius: There is this idea that you need to have a wide impact. As a staff, the impact should go beyond a single group or beyond a single project. There is, on the other side, this idea that you should be technically excellent. You should go deep, and you're the person that knows the most about the topic. (Side-note: @alexewerlof wrote a fantastic article on this called "Beyond Staff Engineer") I actually believe the mistake a lot of people make is that they go so deep on the technical expertise that they forget the organizational surface expectation, or what I call the blast radius of impact of what they are doing. In my view, yes, technical depth is important. We're going to see on part two of my talk, on the behaviors on why that's important. But, where I see a lot of people dropping the ball is on the blast radius, in terms of impacting the broad organization. The reason why I chose blast radius, and not only like high impact, is because there are different shapes of blast radius. You can have an impact on something that's deep, something that almost changes how a product line works. Or, you can create a new platform, a new library or something that is going to make everybody else more productive, all the engineers are going to know who you are or the tool, the innovation you made. Blast radius is the thing that you have to keep in mind in this expectation for staff-plus. If you are working on a project that's only affecting a single repo, and not everybody is or will be knowing about that thing soon, is usually a red flag. On High-Blast Radius, I honestly don't care how technical you are; I care about the blast radius impact of what you work on. It can be a blast radius that is super wide and affects the whole company, or it can be super deep in one area that almost revolutionizes how the product or the product line operates and has profound implications on that particular business area. On both angles, that impacted the company as a whole if you were able to fundamentally change how things were done in a product or product line; although your impact can be considered contained in that area, it impacted the revenue or the cost structure or the customer experience of the whole company. So keep that in mind; even small but deep blast radii are high-blast radii if you look from business eyes into that. ...continue... 🧵
Thiago Ghisi tweet mediaThiago Ghisi tweet mediaThiago Ghisi tweet mediaThiago Ghisi tweet media
English
2
9
46
5K
Diego Sapriza retweetledi
Joseph Jude
Joseph Jude@jjude·
> The question is no longer ‘Can I ship this?’. It’s ‘Should I?’, and ‘What else could I build?’ Agree with @thiagoghisi on this. This is what I'm been thinking after developing 3 personal software with cursor / antigravity x.com/thiagoghisi/st…
Thiago Ghisi@thiagoghisi

Wrote a short essay about my experience using Claude Code pretty much full time over the last 90 days: thiagoghisi.substack.com/p/the-big-cons…

English
0
2
3
546