andreabalducci (@andreabalducci) header
andreabalducci (@andreabalducci) profile picture

CTO & co-founder https://teapaw.org/t.co/HbnRuha320🚀 | master of AI https://teapaw.org/t.co/0rjJ9fDRhN | sup + snowboard + mtb addicted | surfer wannabe | nikon lover |

Here
Joined September 2008
Photo by andreabalducci (@andreabalducci)Photo by andreabalducci (@andreabalducci)Photo by andreabalducci (@andreabalducci)Photo by andreabalducci (@andreabalducci)Photo by andreabalducci (@andreabalducci)Photo by andreabalducci (@andreabalducci)Photo by andreabalducci (@andreabalducci)Photo by andreabalducci (@andreabalducci)Photo by andreabalducci (@andreabalducci)Photo by andreabalducci (@andreabalducci)
andreabalducci retweeted
Microsoft Distinguished eng on why he doesn't read the code and what he does instead Stephen Toub (Microsoft Distinguished Eng): I did not read every line. That would be impossible. And if I did, it would also be a waste. There's no, me reading every line would not prevent bugs. In fact, agents reading every line is a lot more effective, not just faster, but more effective in quality than me doing so. I absolutely looked at the code for every PR that I put up, but I was focusing more on big picture stuff, right? Is the direction of this correct? Is the architecture of this correct? Or is the componentization of this correct? Is the approach, are the algorithms that are being used appropriate? Is there anything fishy about, if I, a lot of it is squinting at a 30,000-foot level and looking at the two codebases and does anything look off, right? And then relying on the agents to focus on the line-by-line details. And in many situations, I would sort of do a quick scroll through all the changes to just see if anything popped out. And I might notice a few things here and there, but for the most part, a really good agentic reviewer is going to be way better at sort of the line-level details than certainly me, and I would argue most humans.
In the year 2000, Joel Spolsky (founder of Stack Overflow) wrote a famous article titled “Things You Should Never Do, Part I.” In it, he talks about how rewriting your code from scratch is the single worst strategic mistake any software company can make. However, times have changed. The cost of writing software is dropping exponentially and that has changed the math entirely on if it is worth rewriting your codebase. For instance, this year Anthropic’s Jarred Sumner ( @jarredsumner ) rewrote Bun in Rust in 11 days leading to many performance and correctness benefits. Likewise, Stephen Toub (Distinguished Engineer at Microsoft, @stephentoub ) rewrote the GitHub Copilot runtime (400,000-line codebase) in Rust by himself. I thought it’d be interesting to lay out everything he learned in the process. So I interviewed him about how and why he did it. In this episode: • Why he choose Rust of all languages • Rollout strategies (incremental vs all at once) • How he prevented regressions • Steering agents and which models he used • Career lessons and engineering advice Where to watch: • YouTube - youtube.com/watch?v=PLMOVlZC… • Spotify - open.spotify.com/episode/4zt… • Apple Podcasts - podcasts.apple.com/us/podcas… • Transcript - developing.dev/p/e073-stephe… Thank you to the sponsor of this episode for supporting my work: • WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at workos.com/ Chapters: 00:00 Intro 01:06 Why the Copilot runtime needed a Rust port 05:38 Why he chose Rust 11:28 Discussing rollout strategies 21:57 How he caught regressions 32:08 Guiding the agents 42:11 Catching regressions before prod 45:16 Which models he used 50:03 The end benefit and costs 01:03:24 When to do a full rewrite 01:06:40 Career learnings on the way to Distinguished 01:16:00 Top technical book recommendation 01:17:49 Advice for young engineers 01:21:00 Outro
10
36
5
419
46,018
andreabalducci retweeted
Over the past week, I’ve been overwhelmed by the love and support of friends, industry colleagues, and people I've never met. Thank you to everyone who has shown kindness to my family and me. It means the world to me. I came to the United States 53 years ago, and becoming an American citizen is one of the greatest gifts and proudest moments of my life. NVIDIA has been my life’s work. Building it into the company it is today alongside my colleagues has been a privilege and an honor. Nowhere but in America could a company like NVIDIA be possible. I love our country, and I love NVIDIA. I did not live up to the standards expected of everyone at NVIDIA, and I have made serious mistakes in my personal life. I created problems for the Board that I deeply regret. I own my mistakes completely, and I am committed to cooperating with the Board’s independent investigation. Since my departure, I’ve seen an outpouring of calls from NVIDIA’s employees, investors, business partners, and customers for me to return as CEO. Many continue to reach out to me directly as the company navigates complex technology, market, competitive, and geopolitical dynamics. NVIDIA is a once-in-a-generation company. If the Board of Directors decides that my return is in the best interest of our shareholders, our employees, the company, and America, I would be honored to answer these calls and return as CEO. Thank you again to everyone who has shared their good wishes. I am profoundly humbled by your support. To my family: I love you, and I will spend the rest of my life being worthy of yours. Jensen
59,844
120,932
24,340
1,162,280
56,168,543
andreabalducci retweeted
Satya Nadella was asked if Microsoft's voluntary retirement offers are a prelude to layoffs because of AI. Satya Nadella "It's a very important question. Let's acknowledge that there is going to be plenty of opportunity going forward. The shape of that opportunity may be different." "The shape of what this new thing looks like is going to be different than what it was before: team sizes and team workflows. It's not that we don't want the 200,000 people at Microsoft flourishing, all of them, and growing even. But the 200,000 people at Microsoft and growing will have to be configured in different ways." "This voluntary thing was mostly about letting everybody have more agency to get themselves into places that make sense for their economic opportunity long term. That's, I think, the key thing." "I don't want to be stuck in a team that's not transforming, even inside of Microsoft. Let's face it. It's not like I can sit here and say every part of Microsoft has really got the memo." "If you're in a team where you feel stuck professionally, you can vote with your feet. I don't want you to, because quite frankly there are many places you can go inside of Microsoft itself." "I wish I could just sit here and say it'll all be the same. I cannot. And this is one of those places where I want to be as transparent about the change."
31
16
11
310
215,774
andreabalducci retweeted
Did you know that running your Mac for more than 50 days without a reboot will fuck with your internet connection? Yes, really. There is a 32-bit integer timing your TCP connections and if you let it overflow MacOS will run into all kinds of fucky issues with its TCP stack. For example I was unable to upload things bigger than 4MB. I was wondering why my Claude sessions started to hang seemingly at random. The fix? Literally just reboot your machine. That's it. What the fuck photon.codes/blog/we-found-a…
Readers added context they thought people might want to know
The TCP issues after ~50 days uptime were a kernel bug only in early macOS 26 Tahoe versions, fixed by Apple starting in 26.4; current systems are unaffected. nevyn.dev/blog/20261030-… photon.codes/blog/we-found-… portal.greenmini.host/help/macos-tah…
112
103
61
1,293
121,068
Il cielo su Torino.
1
2
96
andreabalducci retweeted
I had no accesso to Mythos / Fable 5.2 before tonight, but I wanted to check if a system recently checked by expert humans and updated had still issues. 20 minutes later there were two severe bugs uncovered. I'll not tell which project it is, it does not matter. Mythos is good.
25
18
689
42,646
andreabalducci retweeted
I really don't understand why people are still fighting against an incredible productivity boost like this. Digital Divide will become impossible to fix.
I already see clear signs that who is refusing AI assistance for programming it is starting to lag behind in a significant way, where this means: they are living in a bubble where losing work will happen faster compared to the other folks.
9
1
2
61
6,245
Current status – at Assago, Lombardia
1
1
127
andreabalducci retweeted
A huge amount of the Anti-AI code sentiment massively overestimates the quality of human code outside of a very small set of open source and high quality company codebases. Human Slop is everywhere and can trivially be improved on by any opus level model.
476
898
299
11,468
1,054,153
Current status: the new Jarvis.cloud site is being pushed while we travel toward Milan. Vibes..
3
143
Time to fly back home with new stuff ready for SMAU.
1
80
andreabalducci retweeted
Anthropic rewrote its Messages API in Rust. Zero Rust devs on the team. Claude wrote the code. Humans wrote the plan and checked old vs new matched on real traffic. CPU dropped 40-50%. Pretty sure "never do the big rewrite" is dead advice. @katelyn_lesse on @latentspacepod
107
233
137
2,999
750,066
andreabalducci retweeted
One of the things I appreciate about LLM-driven coding: it obsoletes the useless "blameless review" culture that made conversations about why proposed code / architecture is bad extremely expensive to have. Developers aren't emotionally attached to LLM-authored code the way they were to stuff they themselves wrote. We're all much more outcome-oriented and not output-oriented, which is how it always should have been. We can just agree the code sucks now and redo it
If you think there’s anything wrong with what Bart is saying here you are absolutely deep fried cooked. This is like “level 1” AI adoption.
2
3
1
29
1,337
AI now finds bugs that survived decades of human review, and writes code that looks right but isn’t. Tests can’t keep up. LeanCIL: formal verification for .NET Proofs about compiled C# and F# (any dotnet lang), for every input, checked by @leanprover github.com/NethermindEth/Lea…
6
28
3
129
8,141
Breakfast coding session in Vienna.
79