


Co-founder, CTO @buildkite, Dad, Llama Aficionado (not the model). Previously @GroqInc @cashapp @99designs.


@cjpedregal thoughts?

You work your ass off solving really hard problems day after day for decades, and this is what you get: anyone could have done it. As an investor, I can tell you the limiting factor isn't investment. It's founder ability.

This is sad, Matt. You don't have to agree with everything Musk says or does to recognize his completely unique ability to deliver incredible entrepreneurial benefits to the world. From SpaceX to Neuralink to Tesla to Grok. There are a million "capital allocators", only one Musk.

Very reasonable take. It’s so easy to optimize for the things that are easy to measure
Every team I've ever worked with is overly focused on the wall clock time of open PR -> CI green. Tickets waste in the backlog for months, wait for human review for 3 weeks, and everybody gets fucking pissed when CI takes 15 minutes instead of 5.

The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage. I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care. But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently. For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios. But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.

there is no replacing a founder like Jensen. There never has been, and there can never be, a true succession for a founder like him. Nvidia ends today, and is replaced with a thing cosplaying nvidia. It will be run by custodians trying and failing to preserve the flame he ignited

VC: this deal would go much more smoothly if you used our preferred lawyer First time founder: yeah of course, let’s not rock the boat here. Grateful to have you aboard VC: this deal would go much more smoothly if you - 2nd time founder: *unholstering gun*

signal is a great word for it. Recently I encouraged folks to stop thinking in terms of "loops" and more in terms of: "forward pressure" - what causes work to start (crashes, bugs reports, performance issues, +100 things) and "backpressure" - how does an agent hill climb against an outcome (linters, tests, ai review/risk judge, canaries, feature flags, +100 things) looping these toward a desired state rather than an outcome / artifact is a powerful mental model - forward pressure increases autonomy in what gets attention, backpressure increases autonomy in getting to a super high-quality solution 9 months ago, loops like ralph were primarily used to go from point A to point B in terms of functionality, but this is just one degenerate case of a more generic control loop: - read desired state (e.g. no open bugs, or DB perf above X metric, OR "feature Y shipped", OR "all linter warnings resolved or explicity ignored") - read state of the world (query systems, run linters, etc) - decide if anything needs to be done (compare to policy / desired state) (optional: approve decision) - do the thing (code change, infra change, docs change, process change) (optional: approval action) - repeat shouts out @0xblacklight for the original framing here at AIE back in june. same logic works for evolving the control loop itself

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.

Leaving Conductor? You can bring your chats to Amp. 1. Update Amp 2. Run this in your terminal: `amp threads import conductor --all` Using the Amp Mac app? Open Settings, go to Imports, and click Import. Chats in Conductor Cloud: move them to your Mac first (right-click → Transfer to local) before Nov 20. Once you're imported, use the following code to get 3 months Megawatt plan on us: ampcode.com/code/AMP-VW9Y-LI…
I am very excited to share that Conductor is joining Meta! We have some big, crazy plans for the next interface. If you liked Conductor, you’re gonna love what’s coming. We’re super excited to work with @natfriedman and @alexandr_wang at MSL to build it. They’ve been on an absolute tear, and I’m convinced MSL has the highest talent density of all the labs. A huge thank you to our earliest believers @aaron_epstein, @ilyasu, and @nabeel. And to everyone here who tried Conductor, sent us feedback, and prompt requests - you made this so much fun. Thank you ❤️🚂 Choo choo!


When I first told @MParakhin that we were planning to move to a monorepo he said wisely: Moving to a Monorepo is an idea that every engineer absolutely hates, and that once its there, no engineer would ever want to work at a company that doesn't use one. We will definitely do it.
moving to monorepo has been a boon for agents at shopify. definitely requires some thoughtful tooling, and has some downsides that take a bunch of effort to mitigate… but man I wouldn’t go back

with current token prices i wouldn't really say "cost of software is going to zero" our token cost is double our payroll which means even though we're 25 it's like we're 75 and i feel like our output is similar to a team of 75 pre-ai. we're just able to do it without all the downsides of a larger team this is still a good thing. we couldn't hire 50 more people. so much overhead and impossible to retain a high bar

We’re working with Cursor on this incident, but it wasn’t a compromise of Anthropic’s systems or employee laptops. A malicious actor used access to Cursor’s marketplace to publish a tampered copy of the Claude Code extension, which we didn’t build or publish. The versions on our official channels are not affected and this only impacts Cursor users.
We identified a security incident affecting a modified Claude Code VS Code extension accessed through our Cursor IDE extension marketplace, impacting at most 5,000 users. This malicious version of the extension was not developed by Anthropic. It does not impact other extensions downloaded from the cursor.com/marketplace, Grok Bot, Grok or our other SpaceXSI products. In response, we took down our extension marketplace this afternoon, worked with relevant providers to neutralize the malware, and have reinstated the marketplace after confirming there is no further risk. If affected, please review instructions in this blog post to understand how to find the malicious package and establish a path to mitigate any potential impact. We are asking all customers update to Claude Code for VS Code version 2.1.314: cursor.com/blog/claude-code-…

Reminder to check your kids’ Halloween candy for improperly disclosed CVEs this year.