dad, brew, cook and make ml go brrr

Someplace, World
Joined September 2011
Sebastián Pérez Saaibi retweeted
These are all of the orgs being impacted by the cuts. Screenshot provided by the same Sr. Director.
25
65
33
797
342,838
Sebastián Pérez Saaibi retweeted
Many of you don't understand how serious this is, so let me break it down. In computer science there is a famous kind of puzzle called 3-SAT. You are given a long list of yes-or-no switches and a set of rules about how they must be arranged, and you have to find a combination that satisfies every rule. The obvious way to solve it is to try every combination, but each new switch doubles the number of possibilities, so a puzzle with a few hundred switches would take longer than the age of the universe to brute force. For decades, the smartest people in the field found clever tricks that made this a little faster, but every trick still hit the same wall: the time required kept exploding as the puzzle grew. About 25 years ago, two computer scientists, Russell Impagliazzo and Ramamohan Paturi, working with Francis Zane, turned that wall into a formal idea. They proposed the Exponential Time Hypothesis, which says this explosion is not a failure of human cleverness but a law of nature. No algorithm, however brilliant, will ever solve 3-SAT without the time blowing up exponentially. Nobody could prove it, but almost everyone believed it, and it became one of the foundations of modern computer science. Researchers used it as a measuring stick. If you could show that solving some other problem quickly would also crack 3-SAT quickly, you had shown that problem was hopelessly hard too. Hundreds of papers, across scheduling, graphs, logic and much more, rest on this one assumption. Now an internal AI model at OpenAI claims to have broken it. It says it found an algorithm that solves these puzzles meaningfully faster than the hypothesis allows, and it has checked the proof in a computer verification system called Lean. And here is the remarkable part: the very people who proposed the hypothesis, Impagliazzo and Paturi, along with MIT's Ryan Williams, are now leading the public review of whether a machine has disproved their own idea. So what happens next? If the disproof holds, a large part of theoretical computer science has to be revisited. Every result that said "this problem cannot be solved faster, assuming ETH" loses its foundation, and researchers will have to work out which of those walls were real and which were simply where we stopped looking. It does not mean everything becomes easy. The new algorithm is still slow in absolute terms and this is not the famous P versus NP problem being solved. But it means our map of what is possible was wrong in a place we were very confident about, and it was an AI that redrew it. If the disproof fails, the hypothesis survives and the field breathes out, but we will still have watched an AI produce serious, checkable work on one of the deepest questions in the discipline, closely enough that the founders of the idea had to take it seriously. Either way, something has shifted.
An internal model at OpenAI has produced a claimed refutation of ETH! Russell Impagliazzo, Mohan Paturi, and I have been asked to help organize an open and independent examination of this claim. 1/4
292
1,366
190
14,619
1,192,045
Sebastián Pérez Saaibi retweeted
Folks, I left Microsoft three months ago to start my own company. Two weeks after I left, my whole team in Australia was let go. I see the hurt it’s causing my ex-colleagues, their families and their kids. Layoffs, forced relocations, PIPs. It’s brutal and I don’t want to brush past that. But here’s my honest take. Microsoft needs fewer people. I’ve been on the inside. I’ve seen how things get built. Lots of small orgs. Layers on layers. Silos everywhere. Here’s a real example. The Entra team shipped managed identities back in 2017. No more secrets in code. A clear security win. Then they tried to get the rest of Microsoft to adopt it. Very few teams did, and the ones that did moved at a snail’s pace. Every org had its own priorities and its own decision makers. It took Microsoft getting hacked, and the Secure Future Initiative that followed, before things really moved. Today almost every Microsoft app and service supports managed identity. Six years, and a major breach, to get there. In a world with agents and fewer people, that rollout would be possible across Microsoft in months, not years. Microsoft already has everything else. The customers. The infrastructure. The scale. What it needs is fewer people, leaning hard into agentic work. Right now OpenAI and Anthropic are shipping at a pace Microsoft can’t match. Microsoft has to change to survive.
BREAKING: Microsoft, $MSFT, is offering buyouts to 60,000 workers as part of the company’s efforts to cut costs amid AI adoption, per Bloomberg. Personnel on select teams in the US, Canada, India, and the UK at a vice president level and below will be eligible. This reflects ~27% of Microsoft's total workforce.
192
342
65
4,072
746,275
Sebastián Pérez Saaibi retweeted
En la campaña presidencial colombiana, el presidente Lula apoyó abiertamente a Iván Cepeda y gané yo. En la campaña brasileña, apoyé a Bolsonaro y ganó Lula. Ni Lula decide por los colombianos ni yo decido por los brasileños. ¡DECIDE LA GENTE! Y cuando el pueblo se pronuncia en las urnas, su voluntad se respeta porque es sagrada. ¡En eso consiste la democracia! El presidente Lula y yo tenemos grandes y profundas diferencias políticas e ideológicas, pero coincidimos en algo fundamental: Brasil y Colombia se necesitan mutuamente. Ninguna consideración puede estar por encima de los intereses de nuestras naciones. Colombia y Brasil son países hermanos, con enormes desafíos y oportunidades compartidas. Tenemos mucho por hacer y trabajar en beneficio de nuestros pueblos. El respeto mutuo, la soberanía y la cooperación deben marcar nuestras relaciones, así como la lucha contra el narcoterrorismo y la minería ilegal, la protección de la Amazonía y el bienestar de nuestros ciudadanos. ¡Firme por la Patria! ¡Que viva Cristo Rey! (A.D.L.E) 🇨🇴 🐅
3,125
5,414
1,239
53,862
3,163,352
Sebastián Pérez Saaibi retweeted
despite the unfortunate timing, we take disclosures seriously at @typesafeai at approximately 6:49PM this Friday evening, we became aware of a massive unauthorized leak of ALL customer noul outputs in effort to maximize transparency, here is the link: gist.github.com/diogo149/810…
448
315
260
6,156
1,191,395
If you have the chance, just go to eth zürich
48
Sebastián Pérez Saaibi retweeted
Really looking forward to this -- I have always loved my conversations with Gergely, and this will be a fun venue and format. Join us!
The Pragmatic Engineer Unplugged, live, with @bcantrill & @CompleteSkeptic: 4 Nov, SFJazz Center in SF. RSVP here, you won't want to miss it: luma.com/pragmatic-engineer-…. Thanks to friends at @WorkOS for helping make this happen!
3
4
39
6,474
Sebastián Pérez Saaibi retweeted
I read this and I'm terrified, the situation seems intractable. In the python ecosystem alone every cpython install, venv, UV is at risk. Don't get my started on npm, pnpm, yarn, go, rust. My current 2026 security posture: stay home and only connect to the internet from a trusted ISP. The winter is coming. discuss.python.org/t/informa…
73
374
68
3,277
400,733
It’s performative bullshit all the way down
Are we ready to acknowledge that the RTO mandates ca. 2024 were performative bullshit?
1
59
Sebastián Pérez Saaibi retweeted
This might be heresy but: 1. Code reviews are a massive productivity tax with tiny quality benefits 2. They should not be mandated 3. The author should feel free to request a review if they want it 4. If you don't trust your engineers, invest more in CI, or hire better ones
197
126
141
1,819
659,114
Sebastián Pérez Saaibi retweeted
Love getting to chat with Gergely! Ty @GergelyOrosz 🙏
What’s changed in “the unwritten rules” of engineering management since the 2010s, why are hands-on managers “back”, and what has it done to the engineer-to-CTO career path? With Will Larson (@Lethain). Timestamps: 00:00 Intro 08:20 Stories from Yahoo! 12:47 Digg’s v4 rewrite: the insider story 26:02 Will’s path to eng leadership 30:03 Uber, Stripe, Carta, and Calm 35:11 What does a CTO do? 38:09 Will’s role at Imprint 42:48 How engineering management has evolved 51:08 ZIRP’s impact on tech 57:21 Career ladders 1:01:03 Eng 1 vs Eng 2 1:06:58 How software engineering roles are changing 1:16:25 Revised rules of engineering leadership 1:21:57 The risks of becoming a bureaucrat as an EM 1:25:57 How to become a CTO? 1:31:33 Middle management vs. line management 1:41:36 Will’s writing 1:52:13 Book recommendations Brought to you by: • @turbopuffer – vector and full-text search built on object storage: fast, 10x cheaper, and extremely scalable. turbopuffer.com/v3 • @EntireHQ – Git hosting, rebuilt for the agentic era. Entire hosts your code in-region, and is up to 89x faster than any other competitor. entire.io/pragmatic • What if you only needed a single test to harden your system? Get a free introduction to property-based testing: through a live, online webinar hosted by Hillel Wayne, author of Logic for Programmers and Developer Educator at @AntithesisHQ. RSVP here: pages.antithesis.com/webinar… Two sage observations from Will on how engineering management changed: 1. ZIRP shaped engineering management practices in the 2010s, Will believes. As he put it: “Back then, your ability to hire and close and retain became the differentiator between successful companies. The less successful ones simply couldn’t retain great people. [This dynamic on hiring and retaining] pulled leverage back into the engineer’s hands and created a very different environment. So, companies were pitching themselves as a more relaxed environment, more focused on you, and offering more career development. And I think in ways that I think were often kind of self-defeating.” 2. Blunt message for middle managers: retire or re-skill. Will left a team of 250 at Carta to head up 25 tech people at Imprint. He purposely took a “step back” in his leadership career because he believes things are changing so radically that the engineering leadership profession that we know will not exist in three years. Amid all this, Will says that line management can be a lot more engaging for executives these days because the tools for line management and the tools for writing software are really good. Plus, the tech industry has always been volatile: during the 2010s most of us simply forgot about this!
2
4
73
8,791
Sebastián Pérez Saaibi retweeted
With respect, this is terrible advice. You need to prove -- to yourself more so than to investors -- that intelligence is more valuable inside your product, than on top. If tokens *aren't* worth 4X inside your product, what are you even doing? You're just reselling the labs. 1/
Christina Cacioppo on why Vanta is eating its token costs: "If you try to charge people based on tokens, they are very quick to say, 'Oh, you've just marked up a Claude token 4X. Are you 4X as good as Claude?' You actually put yourselves in a competitive position against the models that probably no application really wants to do. We're eating the token cost right now. We're taking lower margin. This is a usage phase and a deployment phase of this technology, and just go nail that, and you can figure out commercialization after."
68
47
28
1,049
288,581
Sebastián Pérez Saaibi retweeted
gotta catch em all
28
7
198
10,344
Two sides: - people that build - people that talk about building (at conferences) These rarely intersect
39
Sebastián Pérez Saaibi retweeted
Maybe unpopular but yet to see any startup fail b/c architecture choices. I’ve seen a lot fail because of not being able to get users/customers; no real focus on what to build; not finding any traction. When traction hits, even terrible tech choices scale and can be fixed later.
it’s hard to explain the 2010s microservices fever dream to anyone who wasn’t there every day on HN, we'd wake up to an article from a new startup about how they split their app into 300 services so they could infinitely scale (never mind that they only had 100 MAUs today) so many companies never recovered from this it turns out, replacing simple function calls with network calls that could randomly fail isn't great for shipping velocity
181
49
26
1,189
73,020
Sebastián Pérez Saaibi retweeted
Code review is now risk mitigation. The goal should be to reduce the risk of hitting "merge" without reading each diff line-by-line. Close PR review will become progressively less needed.
We made a skill for assessing the risk of merging a PR: /merge-risk This addresses the code review bottleneck by helping devs trust the agent for lower risk changes. It grades risk across 5 categories: alignment, impact, verification, rollback cost, and error detection. - Alignment: does code follow the PR description and related tickets? - Impact: what is the blast radius, and does it touch sensitive code paths? - Verification: does the change include end-to-end verification? This means computer use, screen recordings, before/after screenshots... going beyond unit test coverage. - Rollback cost: once it's shipped, how trivial is it to revert? @mattpocockuk calls this a "two-way door" vs. a "one-way door." - Error detection: are errors reported, logged, or simply swallowed? Try it out: > npx skills add warpdotdev/common-skills --skill merge-risk
19
7
232
39,855
Ni a @yoresongo se le ocurriría salir con lo de eMudhra. Grande India 🇮🇳
1
94
Tired: Agentic Shopping Wired: Agentic Mopping
40