developer at @every • aging skateboarder • piano enthusiast • writer

SoCal
Joined February 2022
I think this is my best work yet. I hope y'all like it lorenstew.art/blog/agentic-a…
4
2
14
19,170
"The native-first guidance was deliberate, an attempt to convince AI to reach for the platform before abstracting." Yes, because more abstractions means more complexity, more mess, and more tokens. Great take 👏 castastrophe.blog/blog/on-wr…
1
2
16
737
Watch me talk about what I’m doing on @every’s frontier team (and get a peek of my tabless browser)
keeping up with AI is a full-time job. that's why every company needs a frontier team: the frontier team's job is to keep up as models change. everyone else's job is to use what they learn we made one @Every and it's completely changed how we work: 0:00 Introduction: Why every company needs a frontier team 2:42 Why the best frontier teams have pirates and architects 4:57 How Head of Evals @hammer_mt builds personal benchmarks 6:46 How Opus edited an explainer video using Slack messages and meeting notes 10:20 Working with AI means protecting other people’s attention 12:26 Why a frontier team needs a “wrangler” like Arielle Shipper 18:58 Why senior editor @jackcheng built a tabless browser 24:37 How resident writer @kplikethebird teaches her AI writing plugin who the reader is 30:51 Inside engineer @JannikJung’s personal AI orchestrator 35:41 Compound engineer @kieranklaassen uses AI to build power tools
3
1
10
2,382
I made a simple little toy version of the inner-outer skill optimization loop, to explain to my team how evals connect to business results. Then I asked Claude to make a Netflix-style documentary about it:
8
6
1
61
7,614
BREAKING: @AnthropicAI just launched Duet, its always-on personal agent. It’s the first personal agent I’d call a pro tool. We’ve been testing it for two weeks. I’ve gone from mostly using ChatGPT to roughly 50/50 between ChatGPT and Claude—the most time I’ve spent with Anthropic in close to a year. • It lives in its own app, separate from Claude, on iOS, Android, and the web. This makes it feel clean and easy to understand. • It has channels for specific areas of your work and life rather than just a single chat • It has a todo list so you never lose what you’re working on and you can always see statuses • It allows you to easily write and edit documents, slides, and more all through the app. • It’s not a chief of staff yet. It can see the Claude sessions on my computers but can’t direct them. Its email drafts are worse than dot’s, and voice is transcription only—you can’t have a spoken conversation with it. My verdict: the vibes are good, and I’m opening Duet every day. It’s worth trying. Check out our agent comparison page: every.to/personal-agents-com… Full Vibe Check coming soon on @every
102
39
12
773
80,932
In 2020 when I left the 50 person marketing agency I built, I spent a year researching memetics, the study of how ideas spread and evolve. I had only recently heard the term and instantly recognized I now had a name for the process I was doing manually that led to my agency's success. I decided to write and self-publish a book on the topic, that only 200 people read. Ironically the meme of memetics is not itself very viral. It's a niche, nerdy topic and it's hard to tell if the people that talk about it are geniuses or conspiracy theorists. In researching for the book I realized why – it was a useful analogy but not that useful in practice. Unlike with DNA there's no way to measure a meme, and without discrete units you can't run falsifiable experiments... so it never became a science. The time writing the book wasn't wasted, it made me a better writer, and got me into AI early as there was some overlap between the niche interests of AI and memetics. In a clue for what was to come, one research team had found a "Spiderman neuron", that fires for photos of people in Spider-Man costumes, comic and cartoon drawings of him, and even the written word “spider”. I'm not an AI researcher, I don't have a PHD, I've never written a scientific paper, I don't work for the labs, I own no GPUs, so instead of trying to get into mechanistic interpretability (the name of that field) I got into prompt engineering right when demand for that field exploded. The past few days have been a whirlwind because having tokens to burn as part of the frontier team at @every I decided I wasn't being ambitious enough, and wrote a scientific paper on memetics. The unlock was reading Nick Cammarata's inspirational "Neural Networks Are Already Clean" paper, and realizing if AI models do have interpretable neurons that fire for specific concepts, we could define a meme in terms of which neurons activate on that concept. I also recalled "Harnessing the Universal Geometry of Embeddings" by Jha et al which said that different models all seem to converge on the same vector embeddings, which implies there is some underlying consistent structure every model is learning independently. So I ran a few experiments where we (Claude and I) tested whether a single neuron inside an AI language model can stand in for a meme. We ran 80 years of Batman plot summaries through two AI models and looked for neurons that fire across nearly every Batman story (his core canon). Then we checked whether films carry the memes of the comics they adapt, and whether the two models, built by different companies, find the same memes. It seemed to work. Why does this matter? - you can decompose ideas into their parts and understand what makes them tick - you can find similarities across cultures and ideas, to identify things you should like but don't know about - you could trace the history of an idea to see who inspired who, even if they never disclosed their sources I'm not an academic and may very well be suffering from AI psychosis, but I sent this paper it to a few people smarter than me, and a few other AI models smarter than me too (Astra, Argon) and it seems to be legit. I'll keep working on this (it's all open source, link below) and see if I can make it more robust. Putting this out there so people can tell me if I'm being dumb, and to inspire others to look into AI neurons as meme units is useful experimentally.
11
5
3
61
5,830
By boss @bigwilliestyle wrote an excellent article on replacing personal agents with a team agent at @every Please like and repost. I think if I get 5,000 likes or 100 reposts, I can make him give me a bonus 💰🤑 every.to/p/why-we-replaced-p…
1
59
notes on using AI productively: - you can separate most work into two buckets: AI-verifiable and not. how you should work depends on which bucket your work falls into - "verifiable" boils down to whether AI can independently tell (verify) if work that it completes is good or not. - if your work is verifiable, design a verifier or system of verifiers and "let 'er rip." use as much AI as you can and get out of the way. you're not the bottleneck anymore, so no marginal attention is required as tasks scale. - if it might be verifiable, you can try building an AI judge. but you need evals to test the judge's competence. @hammer_mt is my go-to on how to do this well. if you can get your judge good enough, you have verifiable work. back to throwing as much ai at your work as you can - sometimes a good judge is easy to build, sometimes it's so hard that you may as well not bother. - if your work can't be verified by an AI, that leaves you or someone else as the judge. treat it like the olden days but with AI help. one or two tasks at a time, avoid context switching, protect your focus - sometimes, there are verifiable sub-tasks within larger pieces of work. The same process re: judgment and eval-building applies to these sub-tasks. The more you can automate these away, the more you can focus on the pieces that you're uniquely suited for.
14
27
3
320
33,334
Didn’t realize Paulie was chill like that
58
265
28
2,482
180,715
at show and tell today @leeknowlton demoing how he turned my Codex piece into a visual novel:
9
3
4
41
9,259
Loren retweeted
Learn about the future of Marko in our ViteConf talk! We're up next, live in 30 minutes 👀 viteconf.org/live
4
14
362
Ok, very cool @danshipper & @every! Here's what I told Codex: "Dan shipper is claiming that this piece/article is designed/created to be read with an agent - let's prove him right/wrong!: every.to/p/how-codex-happene…" At a minimum this is a cool experiment and possibly how I'd enjoy interacting with deep dive content, a mix of analysis/self directed digging and pure consumption. In the past this would occur as two separate steps.
we're dropping something heavy tomorrow @every it's the 8k word definitive history of Codex written from deep interviews with the team that did it including @gdb @thsottiaux @ajambrosino @embirico @mia_glaese @edbayes and more it'll also be agent-native so you and your agent can explore the full text of all the interviews in addition to reading the story :)
2
3
1
10
3,029
Get it while its hot
3
1
1
34
2,015
This is an excellent read - anyone using AI harnesses will find this history informative, and even better, fun! Dan's writing is great, and the designers did an excellent job with the illustrations and interactions. You get access to the interviews too. Use codex to read an article about codex!
Codex is one of the most important untold stories in the history of technology. A year ago, it was a scrappy effort in a quiet corner of @OpenAI. Its cloud product hadn’t found PMF, and the team was starting over from scratch. Less than 12 months later: - Codex swallowed the flagship ChatGPT desktop app from the inside (it literally runs as com.openai.codex on your Mac) - Codex and ChatGPT for Work hit 40M+ weekly users across engineering and knowledge work - Its leader @thsottiaux was elevated to run all of OpenAI’s core products, including ChatGPT, Codex, and the API How did they pull it off? They trained their own dedicated model line, separate from ChatGPT, with researchers and product builders sitting on the same team They built four different products in a single year (cloud → terminal → IDE sidebar → a desktop app with no code editor at all) as every model leap made a new form factor possible They used Codex to build Codex—so a handful of people could prove a new product in weeks instead of arguing for it in meetings I had a front-row seat to the whole arc—from their failed Cloud launch, to OpenAI’s offices the night before GPT-5 dropped, to the day Codex took over ChatGPT. And I spent months interviewing @gdb, @thsottiaux, @embirico, @mia_glaese, @aambrosino, and @edbayes to get inside how it all went down. Here is the full, behind-closed-doors story of the team that remade OpenAI: every.to/p/how-codex-happene… We’re pushing the boundaries of how stories like this are told. This piece is completely agent-native—designed to be read alongside your agent inside ChatGPT’s in-app browser: - Every interview transcript is included in full: Click any quote and you (or your agent) can see the exact conversation it came from. - Built for your agent to explore: Ask your agent to pull out product lessons for your team, cross-examine the transcripts, or find insights I missed when writing the piece. It’s a story about the future of software—built to be read with an agent: every.to/p/how-codex-happene…
3
2
9
1,745
Thanks to @lateinteraction for creating @DSPyOSS and encouraging me out of my imposter syndrome, and @dbreunig for convincing @OReillyMedia this topic was a good bet. Thanks @LakshyAAAgrawal for making GEPA the optimizer that has been dominating every prompt I try. Also @isaacbmiller1 the lead maintainer of DSPy, @jamesaphoenix12 coauthor of my last book, @Shashikant86 and Sriharsha Annamaneni for technical review. Thanks to my colleagues @danshipper and @kieranklaassen for reading and endorsing the book before it was published. Thanks also to the team at O'Reilly, Jeff, Nicole, Beth for making my writing fit to print. The wider DSPy community @MaximeRivest, @getpy, and @_rchaves_ and everyone who was patient enough to explain to a naive prompt engineer why we didn't need prompts anymore. Finally thanks to my wife and kids (who thankfully aren't on X), for giving me 9 months of evenings and weekends to get this done.
4
14
48
5,964
I got a fish this time 🐟
8
13
3
117
15,545
A melhor invenção da humanidade:
724
24,175
1,256
305,002
3,755,605
we're dropping something heavy tomorrow @every it's the 8k word definitive history of Codex written from deep interviews with the team that did it including @gdb @thsottiaux @ajambrosino @embirico @mia_glaese @edbayes and more it'll also be agent-native so you and your agent can explore the full text of all the interviews in addition to reading the story :)
27
21
9
226
24,734
Look who showed up in @frontendfocus this morning! @JLarky
1
4
207