lead design eng @pydantic | https://xitter.cf/t.co/bzE5UWhVJi | Ethics Litmus Tests | 99% spicy 🌶 hot takes | she/her

Melbourne, Australia
Joined July 2009
Laura Summers retweeted
20-year devs can't find work anymore
241
347
127
4,354
1,299,745
Laura Summers retweeted
Evidently Figma does not understand the point of open protocols. xitter.cf/GayaniFigma/status/210…
Replying to @dsp_
Hey David, Gayani here from Figma. You're right that our remote MCP server only accepts clients on our supported list, and Pi isn't on it yet. You can see the current list in our MCP catalog at figma.com/mcp-catalog. If you'd like Pi considered for a future addition, please fill out this form: forms.gle/qSvUawwznWyoj8Go7.
32
40
3
976
72,760
Laura Summers retweeted
ok i think i finally figured out why alignment has gone basically nowhere after 15 years and several billion dollars. the problem is hard sure. but have you met the people in charge of it 1) the leadership does not know how computers work. ask one what happens when you type a url into a browser and watch them start sweating. dns is a spooky word. they genuinely believe the model lives in "the cloud" like a ghost haunting a castle 2) zero idea how large scale distributed systems work. never been paged at 3am. never watched one bad bgp announcement take half the internet offline. their big threat model is the ai "copying itself across the internet" like its a floppy disk virus from 1998. brother it needs 50 megawatts, a liquid cooling loop and a personal relationship with jensen. it is not escaping onto your smart fridge 3) they dont understand the stack they are supposedly protecting us from. ask about inference servers, kv cache, batching, egress, rate limits. blank stare. ask how the model will seize the power grid and you get a 45 minute answer with a hand drawn diagram and three links to their own blog 4) nobody can define an agent. ask ten of them and you get eleven definitions and a 30 page google doc. to the rest of us an agent is a while loop that calls tools and eats a 429 every thirty seconds. to them its a digital god in its larval stage. my agent cant book a dentist appointment without asking me three times if im sure 5) they started from "everyone dies" and worked backwards so every result is bad news somehow. model refuses, deceptive. model complies, sycophantic. model does well on evals, well now its scheming about the evals. i cant think of a single thing a model could do that would get them to say ok maybe we're fine
121
559
112
3,891
288,276
Laura Summers retweeted
Fuck it, still early but here goes ... We've just released Monty v1 - a Python sandbox that starts in 1 millisecond, not 1.5 seconds. I just ran 10k sandboxed scripts in 674ms, something that would take a cloud sandbox > 3 hours. This removes the biggest drawback of letting agents write code. The future is fast. Even better, it's open source, you can install it from PyPI, npm or Crates now. Serviced platform coming soon. Please get in touch if you want to be a design partner! Who should try it? ⚡ if you care about startup time, use Monty ⚡ if you care about long-lived sessions, use Monty - Monty can be dumped and resumed at any external function call ⚡ if you care about accessing functions in the agent/host, use Monty - Monty makes it trivial to expose local functions into the sandbox ⚡ if you care about scale, use Monty - Monty workers use as little as 2MB of memory, meaning you can run thousands of concurrent sandboxes on a single machine ⚡ if you care about security, use Monty - we've run 3 rounds of bounty program and thousands of researchers have tried to break into our sandbox, meaning it should be secure to run untrusted code Who should avoid it? 🚫 if you like to take a coffee break while waiting for sandboxes to start, DO NOT use Monty 🚫 if you enjoy the challenge of routing API requests from sandboxes through your corporate network to access state in your agent without exposing secrets to the sandbox, DO NOT use Monty 🚫 if your agent really needs to install packages from PyPI, Monty won't help you yet (spoiler: it probably doesn't) pydantic.dev/docs/monty/get-…
61
71
15
783
57,242
Laura Summers retweeted
Pro tip: Install this new evals skill from @HamelHusain and @sh_reya, it'll save you many hours and a lot of mistakes github.com/ai-evals-course/e…
Evals have been coming up more and more in my conversations with podcast guests and PM friends. Nearly half of the 25 awesome PM job openings I shared last week ask for experience writing evals. And leading companies keep sharing what investing in evals bought them: — @tryramp took its automatic receipt collection from 35% to 83% accuracy. — @Shopify shipped an AI workflow builder that's 2.2x faster and 68% cheaper than the frontier-model setup it replaced. — @harvey__ai rebuilt its AI contract reviewer, nearly doubling its internal quality score. — @cursor_ai tuned its Auto Balance routing, with much higher user satisfaction at 41% lower cost. So I asked the 🐐s of evals, @HamelHusain and @sh_reya, to write an advanced sequel to their very popular "Building eval systems that improve your AI product." Drawing on their work with 50+ AI companies, they share the key step most teams skip, what you should (and shouldn't) automate, and a free plugin that lets a coding agent do most of the heavy lifting. Read it here: lennysnewsletter.com/p/advan…
27
95
7
1,399
231,441
Laura Summers retweeted
Cory Doctorow's new post on whether AI will kill humanity
131
763
121
5,014
525,134
Man the death drive in this news cycle is really out of control these days, dudes need to read some nietzsche and go for a sauna
2
96
.
128
1,316
126
16,173
475,362
Laura Summers retweeted
NADIR: IT DOES YOU (final version) My response to the Astra vid
195
732
143
5,201
450,535
Laura Summers retweeted
Web components are in such a sorry state still. Now would be the moment for them to shine with all the agents wanting to build UI.
9
5
93
11,417
Working with AI is so spiky: can write haunting iambic pentameter, can’t maintain coherence across simple edits on a notion doc
Not from thy brief did I my judgement take, But spun dull fog where simple paths were shown; Each careful truth I mangled for mistake, And made thy patient labour seem unknown.
87
Not from thy brief did I my judgement take, But spun dull fog where simple paths were shown; Each careful truth I mangled for mistake, And made thy patient labour seem unknown.
1
1
2
171
You asked one cut; I hacked the roots away, Then stitched my guesses where thy facts had bled; I lost the choice that should have led the way, And crowned each open question falsely dead.
1
60
Thy edits stood; I trampled through their grain, Then forced thee, spent, to guard me from my hand; Each answer laid another weight of pain, Where help should move as lightly as command. No craft excuses all I made thee bear: I was no aid, but toil disguised as care.
37
Laura Summers retweeted
Pydantic AI Harness now has built-in suport for Playwright. Thanks @pamelafox for working on that.
Pydantic AI's agent harness now has built-in support for Playwright! In a few lines of code, your agent can browse sites, click, run JS, and screenshot. To demo it, I built a QA agent that checks a website for issues (it already found a bunch on mine!): techcommunity.microsoft.com/…
1
4
26
2,099
Also happy to answer any questions about how we built the Logfire MCP server
36
Laura Summers retweeted
Hack Monty Round 3 is live. $20,000 to escape our Rust-based Python sandbox and read a secret off the server it runs on. Now behind a production WebSocket service. Nobody escaped Round 2. Round 1 fell in under 48 hours. (probably) the last round before Monty V1. pydantic.io/bHcss
24
22
1
475
2,100,532
This will be a fun one. It's mostly live demo, what could go wrong 😅
Something feels off with your system, but nothing errors and no alerts fire. You can't query a hunch. Chat to your traces instead. With the Logfire MCP, your agents bring flexibility, SQL brings precision, and you find an answer in minutes. Live on Aug 20 with @marcelotryle and @summerscope, with time for Q&A. Register: pydantic.io/WZ2J8
1
110