This week is my last one at @MongoDB. 4.5 years ago I joined as a Senior Developer Advocate with one clear mission: 👉 help developers understand MongoDB through video tutorials. I wanted to make complex database concepts actually make sense. That mission turned into hundreds of videos reaching millions of views, from the OG Jumpstart series debunking NoSQL myths to lounging on the beach showing off the MongoDB MCP server. Every video was a chance to break down another wall between developers and the tools they needed. But some of the best teaching happened face to face. I traveled all over the world giving talks—some to small rooms, some to auditoriums with over 1000 people. The scale didn't matter. What mattered was talking to developers after the session, understanding what they were building, what problems they were stuck on, and how I could actually help. Those conversations shaped every piece of content I created. The best part of this job was the partnerships. Working with teams at @vercel, @prisma, @mastra, @langchain, @DeepLearningAI, and many others taught me that great developer experiences happen when companies actually talk to each other. These collaborations pushed me to think bigger about what teaching could look like. Notifications! **And this is going to be one of those awkward award speech moments where I just keep listing names**: @RitaMRDevIT, Lieke Boon, Pedro Machado, @nraboy, @anaiyaraisin, Tim Kelly, @LuceCarter1, @MeganGrant333, Ricardo Mello, @richmondalake, Apoorva Joshi, Pavel Duchovny, @BazeleyMikiko, Michael Lynn, Toni Bird, Dave Gruchacz, @mjasay, Dorothy McClelland, and so many others—you made every video better, every livestream less stressful, every event run smoothly, and every planning session actually fun. This team showed me what it looks like when people genuinely care about helping developers succeed. Moving from Senior to Staff Developer Advocate meant getting to think more strategically about how we teach, who we partner with, and what content actually moves the needle for developers. That shift changed how I approach creating anything. Friday is my last day. I'm taking everything I learned about teaching, community building, and developer advocacy into whatever comes next. Now comes the worst part! I have to send back my laptop along with the stickers I've accumulated. 😩 I guess a clean slate is good. Send stickers please!! 😅 Thank you to everyone who watched a video, came to a talk, or spent five minutes at a MongoDB booth telling me about what you're building. That's why any of this mattered!!

I made a modified version of this called /improve-solo which uses all of the Solo orchestration features like todos, scratchpads, subagents, etc instead of local files. Give it a try: npx skills add codeSTACKr/improve-solo What do you think @aarondfrancis ?

I'm so sorry for my bad french..

agi

watching two very smart people argue about whether agents should write 100 percent of the code or 99 percent, when the percentage was never the interesting part. nobody's losing sleep over an agent building an internal dashboard. the fear is it ships something that takes down prod at 2am. so sort the work by how much it can hurt you. hand the agent the whole keyboard on the cheap, reversible stuff. stay in the loop where a bad diff actually costs you. stop counting what percent is AI-written. ask what breaks if it's wrong. that's the job.

Everyone's mad about Copilot's usage-based pricing. I think the meter is the best thing to happen to how people use these agents. Completions are still free. What burns credits is firehosing 200k tokens of your repo at a frontier model and hoping. The runaway bills aren't a pricing problem, they're a discipline problem. If you don't want a surprise bill, work tighter. Hand the agent the two or three files the task actually touches instead of the whole repo. Keep a cheap model as your default and only reach for a frontier one when the work needs it. Start a new chat for each task so you're not paying to drag an hour of history into every reply. And spend a little longer on the prompt before you fire it off. You lose the predictable runway, sure. But a meter that makes you think before you spray context is a habit worth paying for.

Look ma, I made it!! So humbled to be among these amazing speakers. I’ll be giving a 3 hour workshop on building open source voice AI agents for production at @AllThingsOpen.

Returning to the scene of the crime. Check out the MongoDB x LiveKit demo 👇

Who will I see at #msbuild this week?!?

Will I get to meet Cassidy next week?!?

Honored to be included in @Redpoint’s 2026 InfraRed 100 list alongside the most promising private companies in AI infrastructure. What we’ve built is a reflection of the customers we get to work with, from SAP and OpenAI to thousands of teams shipping voice agents every day. redpoint.com/infrared/100/

I've been using Solo for over a month now for free and it's worth paying for! Take my 💰 @aarondfrancis! soloterm.com

👀

Runway is 🐐 for video generation. And now they have realtime avatars!!

Add a voice widget to any website easily! 👇

Already built a @LangChain agent? You don't have to rebuild it for voice. With the LangChain plugin for LiveKit Agents, you can connect it to a realtime voice pipeline, complete with speech-to-text, text-to-speech, and the infrastructure to deploy it at scale.

Oh! Want to see how I did it?? 👀

What if you could call Solo on an actual phone number or use it on your mobile while away from your computer?? @aarondfrancis