Podcasts about debug

Google's Debug program is releasing 64 million Wolbachia-infected sterile male mosquitoes into parts of Florida and California over four years to combat disease-spreading mosquitoes.The Sterile Insect Technique works by having these males mate with wild females, causing their eggs to fail to hatch (via cytoplasmic incompatibility), which gradually crashes the local mosquito population over generations.The approach has shown strong results in past trials (90 percent+ reductions), but it carries risks such as imperfect male/female sorting by AI and potential ecological disruptions if mosquitoes are fully eliminated from an area.Let's go through the details together.

Der US-Präsident droht, seine WM-Sause zu vergeigen. Putin spürt die Kriegsmüdigkeit seiner Landsleute. Und Google stört Mücken bei der Fortpflanzung. Das ist die Lage am Donnerstagabend. Die Artikel zum Nachlesen: Fußball: Trumps Turnier Ausbleibende Erfolge: Kostspieliger Krieg – in Putins Russland wagen die Ersten offene Kritik Projekt »Debug«: Google will Mücken mit 64 Millionen Mücken bekämpfen. Wie geht das? +++ Alle Infos zu unseren Werbepartnern finden Sie hier. Die SPIEGEL-Gruppe ist nicht für den Inhalt dieser Seite verantwortlich. +++ Mehr Hintergründe zum Thema erhalten Sie mit SPIEGEL+. Entdecken Sie die digitale Welt des SPIEGEL, unter spiegel.de/abonnieren finden Sie das passende Angebot. Alle SPIEGEL Podcasts finden Sie hier. Den SPIEGEL-WhatsApp-Kanal finden Sie hier. Hier geht es zu unserem SPIEGEL Shop. Alle Newsletter vom SPIEGEL finden Sie hier. Hier geht es zur SPIEGEL Akademie. Sie möchten den SPIEGEL mitgestalten? Registrieren Sie sich bei SPIEGEL Perspektiven. Informationen zu unserer Datenschutzerklärung.

Run enterprise Postgres workloads on Azure HorizonDB with around 3x the throughput of self-managed deployments — zone-resilient by default, no architectural trade-offs. Call AI models directly from SQL, build durable vector pipelines inside the database, and deliver high-accuracy similarity search at massive scale with DiskANN and AI re-ranking, all without leaving PostgreSQL. Debug and optimize queries faster with the Azure HorizonDB VS Code extension. Visualize execution plans, let Copilot generate fixes, and clone production data to test environments in seconds. Charles Feddersen, PostgreSQL Partner Director PM, shares how to put all of it to work on Azure. ► QUICK LINKS:  00:00 - Azure HorizonDB features 00:57 - Open-source PostgreSQL 02:24 - How it works 03:37 - Performance 04:51 - Enterprise-ready security 05:34 - Memory & storage work together 06:29 - AI Model Management + AI Functions 08:24 - AI Pipelines 09:50 - DiskANN + AI Re-ranking 10:50 - VS Code Extension + Data Cloning 12:31 - Wrap up ► Link References Check out our blog at https://aka.ms/azurepostgresblog ► Unfamiliar with Microsoft Mechanics? As Microsoft's official video series for IT, you can watch and share valuable content and demos of current and upcoming tech from the people who build it at Microsoft. • Subscribe to our YouTube: https://www.youtube.com/c/MicrosoftMechanicsSeries • Talk with other IT Pros, join us on the Microsoft Tech Community: https://techcommunity.microsoft.com/t5/microsoft-mechanics-blog/bg-p/MicrosoftMechanicsBlog • Watch or listen from anywhere, subscribe to our podcast: https://microsoftmechanics.libsyn.com/podcast ► Keep getting this insider knowledge, join us on social: • Follow us on Twitter: https://twitter.com/MSFTMechanics • Share knowledge on LinkedIn: https://www.linkedin.com/company/microsoft-mechanics/ • Enjoy us on Instagram: https://www.instagram.com/msftmechanics/ • Loosen up with us on TikTok: https://www.tiktok.com/@msftmechanics

The church attended by Texas Democratic Senate Candidate James Talarico comes under scrutiny for the various progressive and controversial causes it stands behind. Google parent company Alphabet seeks federal approval to release up to 32 million mosquitoes in Florida and California as part of its “Debug” program. President Trump says “he couldn't care less” if negotiations with Iran fall flat, as talks come to a screeching halt and questions remain about a call between Israeli Prime Minister Netanyahu and Mr. Trump. The remains of a missing scientist linked to Los Alamos National Laboratory are found in New Mexico.   SimpliSafe: Visit https://simplisafe.com/MEGYNto claim 50% off any new system!   Birch Gold: Text MK to 989898 and get your free info kit on gold Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Table of Contents: Google's Debug project plans to release 64 million bacteria-infected GMO mosquitoes—Pray against this Medical Doctor Says That The U.S. Government Dropped Radioactive Ticks on Americans as Bioweapons! Listener Comments: USA Tick Updates–The ticks here in PA are insane–I know several people whose kids had ticks on them and sent the tick for testing and came back Positive for Lyme! Listener Comment: Tick Wise Spray–GERANIUM OIL!!!! Is great & found most effective & beware of the ultra-tiny ‘seed ticks' Permadrought: 75 Percent Of The Global Population Lives In A Country That Is Being Affected By “The Great Drying” WEF's next target: YOUR TAP WATER–After failing to force everyone to get vaccinated, the unelected globalists are now coming for your water — pushing to limit consumption, control supply, and even floating the idea of adding vaccines to it! Proactive Solutions: Tag from “Life Done Free” EXPOSES How Small Towns Can DEFEAT Data Center Encroachment PDF: Emergency Freedom Alerts 6-1-26 Click Here To Play The Part 2 Audio Source

The AgNet News Hour featured California gubernatorial candidate Steve Hilton in a wide-ranging interview focused on agriculture, water policy, energy costs, regulations, and the future direction of the state ahead of the upcoming jungle primary. Hosts Nick Papagni and Josh McGill opened the program by noting frustration that recent gubernatorial debates largely ignored agriculture despite California's massive farming economy. Hilton said agriculture has been “strangled and throttled” by state leadership and promised major changes if elected governor. “You're never going to have a stronger champion for farming and agriculture than me when I'm governor,” Hilton said. Hilton repeatedly criticized California's current water management system, arguing that environmental policies and regulatory decisions have limited water deliveries to growers while hurting rural communities. “We can increase deliveries within our current water infrastructure,” he said while discussing the State Water Resources Control Board and water allocation policies. Energy policy was another major topic throughout the interview. Hilton blamed California's high diesel, electricity, and fuel costs on climate regulations, restrictions on oil production, and state environmental mandates that he argued increase costs for farmers and consumers alike. “Energy costs go into everything,” Hilton explained, pointing to fuel, transportation, processing, and irrigation expenses impacting agriculture across the state. Hilton also criticized California's push toward solar development on farmland and accused state leadership of neglecting agriculture in favor of environmental ideology. “They are happy to see farmland ripped out and replaced by solar farms,” Hilton said. The interview also focused heavily on regulations and labor costs. Hilton discussed concerns over PAGA lawsuits, overtime rules, Air Resources Board regulations, and the cost of complying with state mandates. “We've got to deal with the lawsuits that are crippling so many industries,” he said. Hilton said his administration would work closely with the federal government on agriculture, transportation, and water projects rather than maintaining ongoing political conflict with Washington. “I know Brooke Rollins very well,” Hilton said, referencing the U.S. Secretary of Agriculture. “We're going to be working together well.” Transportation infrastructure and taxes also became part of the discussion. Hilton criticized California's gas tax, vehicle registration fees, and the state's ongoing high-speed rail project, arguing taxpayers are not seeing results from the money being spent. “We put in the highest taxes in the country and get the worst results,” Hilton said. Throughout the conversation, Hilton framed the election as a choice between continuing current policies or pursuing major reforms focused on affordability, water reliability, lower energy costs, and regulatory relief. “We've got everything we need in California,” Hilton said. “We just need common sense leadership.” The broadcast also featured a Growing Edge segment with Valent USA discussing organic pest management tools, including PyGanic and the Debug product line, along with challenges facing organic growers dealing with thrips, aphids, navel orangeworm, and spotted wing drosophila. Listen to the full interview below or on your favorite podcast app.

Mesmo 25 anos após a saída da SEGA do mercado de consoles, ainda existem aqueles que sonham com o Dreamcast 2. Mas será que ele um dia vai existir? Com a criação de hardware cada ver mais cada e difícil, optar por lançar um console é viável ou burrice? Nesse episódio, que é uma homenagem a um dos eps mais antigos do Debug, analisamos um pouco da história do Dreamcast, assim como as lendas e mitos envolvendo o seu sucessor e tentamos entender se um dia a SEGA irá voltar para a guerra dos consoles. Confira!

As we're getting close to rounding out the Beta period of the 2.0 editor, we're trying to close out any bugs we find or users report quickly. They could be browser-support related, network conditions related, account capability related, or just bugs in how the 2.0 editor and technology behind it works. It's complicated enough that the best way to debug things is to see exactly what the user sees when they have trouble. A very cool side effect to having built the 2.0 editor with Apollo is that we have a nearly complete look at what is happening in the editor by virtue of the Apollo Cache (we talked about what that is here). We built a tool that can export that as JSON data, and we can load it locally to see exactly what the user sees. It's a bit fancier than that, doing things like saving browser console error logs and stuff, but that's the gist of it. Time Jumps

In #379 Sendung wurde Ingos USV zur Dramaqueen, während Schüler am Zukunftstag Linux entdeckten und vermutlich nie wieder „nur Windows“ sagen können. Microsoft begräbt die Telefonaktivierung, Meta das Metaverse – und irgendwo bootet trotzdem ein frisches OS auf dem Z80. KI gab's natürlich auch: Tokens statt Gehalt, geleakter Code und Sandboxes für alle, die ihre LLMs lieber im Käfig halten. Dazu Open Source, Deutschland-Stack, Polizeibesuch wegen Zero-Day und jede Menge 3D-Druck-Kram zum Anfassen, Fummeln und Löten.

For a limited time, Latent Spacenauts can skip the waitline to join Dreamer and also compete for a $10,000 cash prize for most useful tools for Dreamer! Thanks @dps!In 2024, David Singleton left Stripe and joined forces with Hugo Barra for a buzzy stealth startup named /dev/agents. This month they emerged out as Dreamer, a consumer-first platform to discover, build, and use AI agents and agentic apps, centered on a personal “Sidekick” that helps users customize experiences via natural language. Sidekick is nothing less than an “agent that builds agents”, with all the complexity that that entails:You've seen many many website builder, app builder, and even agent builder startups by now, but our favorite detail is the sheer amount of work that has gone into the “full stack” nature of the platform, including shipping their own SDK, logging, database, prompt management, serverless functions, and so on. Most platforms restrict the tech stack you can use just to get off the ground — Dreamer does it “right” by letting you push whatever arbitrary code you want to their VMs.Paying the BuildersOf course former leaders of Stripe and Android would not stop at just building the tools, but also building the ecosystem. Dreamer is deeply aware of the 4 sided network effect it has going on and is ready to fund all of it - from hiring Builders in Residence to awarding $10,000 cash prizes to the best tool builders for the Dreamer ecosystem.It's time to Dream!Full Video Episodeon youtube.Transcript[00:00:00] Meet Dreamer Purple[00:00:00] swyx: Okay, we're here in the studio with David Singleton. Welcome.[00:00:08] David Singleton: Hey, Wix. It's great to be here.[00:00:09] swyx: It's great to have you. Uh, we have very sympa that your company color is the same as Lean Spaces color.[00:00:15] David Singleton: That's right. Dreamer Purple.[00:00:17] swyx: It used to be Devrel agents, which I thought was very cool. It's like you call back to Devrel Payments.[00:00:22] David Singleton: Yeah.[00:00:22] swyx: And you were obviously CTO Stripe. And talk to me about just the origin or thinking process behind Dreamer. Yeah. And maybe, maybe start with like, what, what is Dreamer?[00:00:31] David Singleton: Yeah.[00:00:31] What Is Dreamer[00:00:31] David Singleton: So Dreamer is a new product, uh, which everyone can come and play with today. Um, it's a place where everyone, literally, everyone can discover, build, and enjoy and use AI agents and agenda apps.[00:00:45] And we really did design it for consumers, for folks who are not necessarily. Uh, have any kind of technical background. It's really aimed at everyone. I think often of my sister, she's very smart. She's not in the slightest bit technical. She has lots of problems in her life that [00:01:00] she would like to be able to have great software and intelligent software to solve.[00:01:04] But you know, even with the rise of tools like Cloud Code and so forth, she's got no way to get started. And Dreamer is a place where she can come in, grab some intelligent apps that other people in the community have built, start using them right away, and solve real problems in her life.[00:01:19] Sidekick And Waitlist[00:01:19] David Singleton: And at the core, we have a personal agent called the Sidekick.[00:01:24] Um, you can give your sidekick a name, you can give it its own personality, and it really helps you across your entire day, your life. It helps you use all of the agents on the platform, and it also helps you build anything you want. And we've been working in this for a little while. We recently launched in beta.[00:01:41] So anyone can go to dreamer.com, join the wait list. Um, and we have many, many, many people in the community now who are building really fun, really powerful, really useful. Agents and the agentic apps for themselves.[00:01:54] swyx: I think we're gonna go right into a demo. Yeah. I just wanna make an observation that, uh, you, you, [00:02:00] you put discover first before build.[00:02:02] Mm-hmm. But actually, at least for the engineers in the audience. ‘cause we are primarily engineers and you're primarily targeting consumers, right?[00:02:08] David Singleton: Yeah.[00:02:08] swyx: For engineers. Like, there's a huge full stack of stuff, which we're gonna dive into. Let's write. It's so impressive. I'm like, holy s**t, this, this is what I've always wanted.[00:02:16] Cool. Uh, so, so I think that's really good and I've, in some ways, I think given your background given, uh, Hugo's, is it Hugo? Hugo.[00:02:24] David Singleton: Hugo. Hugo Bar. Yeah.[00:02:25] swyx: Hugo, it's not surprising that you can basically kind of build an app store Yeah. For agents.[00:02:30] David Singleton: Yeah. So Hugo was my co-founder. Yeah. Um, Hugo and I met with our other co-founder Nicholas Checkoff in the very early days of Android at Google, where we were building Google's first mobile apps.[00:02:41] Uh, we then contributed to very core pieces of Android itself. And you're right, we were really excited about building two things. One, solving a bunch of problems. That this breakthrough technology here I'm talking about mobile needed to have solved in order to make it work for real people at scale. And then secondly, building this ecosystem, um, [00:03:00] of third party developers using the Play Store, um, and able to deliver way more value on the platform than we could have delivered on our own.[00:03:08] And we think about Dreamer in exactly the same way. So I was working at Stripe, as you mentioned, and we had the opportunity to put some of the very first AI agent systems in the world into production. And from the moment we did the first of those, I was just struck with a strong sense of conviction that this is breakthrough technology that's gonna change how all of us work with computers and phones and so forth, all of the, the technology in our lives, but.[00:03:34] There's a lot of problems to be solved, for real people to be able to make this approachable. Um, and it really is kind of a direct analog for what we were solving back in the early days of mobile apps at Google and, and Android. So it's, it's been fun to bring that to life.[00:03:47] swyx: Yeah. Uh, let's look at it.[00:03:48] David Singleton: Yeah, let's take a look.[00:03:49] Dashboard And Daily Briefing[00:03:49] David Singleton: So, uh, dreamer.com, this is our homepage. This is where you can come and, uh, watch some videos about what is here and sign up for the wait list. Once[00:03:57] swyx: you, I, I just wanna say for those listening, ‘cause we have a lot, you [00:04:00] know, switch to YouTube, look at the animations. So much care.[00:04:03] David Singleton: We, we really care about, uh, this product being fun.[00:04:07] Uh, and, and interesting to use. Obviously a lot of people are using it to do real important stuff. You can do real work, uh, here, uh, but also you can build fun things too. Once you get off of our wait list, you'll come into the product. The first thing that happens is you'll have a conversation with your side cake, which is this little friendly, uh, character here.[00:04:27] And psychic will seek to get to know you and understand you. What do you care about? And will help you discover and build your first AI agents or agentic apps. After that, you're, you're gonna have a dashboard. This is my dashboard. Everyone's is different. Um, you can see I have a few things here. I have a feed.[00:04:42] So a lot of our agents do things in the background when you're not looking and the feed is how they let you know what they've been up to. I have, uh, some widgets, uh, from apps that I have built. Uh, this one is called Calendar Hero. Uh, this is something that I installed from the gallery. Uh, so built by someone in our community.[00:04:59] It's a [00:05:00] really powerful calendar app because for each of my meetings, if it's with someone I don't already know, well it'll actually go off and research it, um, and give me both a history of my interactions with those people and also a bunch of, you know, public useful information to, to get started. One of the things I love about this particular app is that every day it generates a podcast, um, a daily briefing.[00:05:24] And one of the things that we've done with the platform is we've made it possible for all the things that agents do to show up in places that you care about. So if you look over here, this is the screen in my phone, and if I go ahead and open my Apple Podcasts, you can see right here. Your Daily briefing podcast is ready.[00:05:39] This was produced by an agent running in my Dreamer account, and it was very easy by scanning a QR code to connect it to my Apple podcast. That's what I listened to in the car now every morning. Yeah. On my way to work.[00:05:50] swyx: It, it[00:05:50] David Singleton: preps me for, for my day.[00:05:52] swyx: So one additional bit of context. I asked you immediately after seeing this was like, what, what about, I wanna talk back to my agent and you said you actually started with voice and then you went to [00:06:00] podcasts.[00:06:00] ‘cause it's nice to have it pre downloaded[00:06:02] David Singleton: that, right? That's right. Um, yeah, we, you, you can talk to your sidekick. So, you know, on mobile we have, uh, a dreamer app and you can talk to the sidekick right here. Um, but we've actually found that making things, uh, show up in the other apps that you already use in your life is incredibly powerful.[00:06:19] So let's take a look at what's kind of under the hood here.[00:06:21] Gallery Tools And Payouts[00:06:21] David Singleton: So I already mentioned that we have a gallery, so this is where you'll find a lot of agents from our community. Uh, there's. Many at this point, hundreds. And they are solving all kinds of, uh, use cases. I'd say the the top use cases are on personal productivity, but also a lot of information management that can range from personal information like docs and so forth, managing your emails.[00:06:42] It also ranges out to public information that you might be interested in, but you need something to help manage the, the kind of fire hose of stuff that's coming at you. For instance, I have, um, an agent which looks at all the AI news, um, all the time. There's a lot of it and it finds the stuff that I would actually be [00:07:00] interested in, um, and I find it incredibly useful.[00:07:03] So these are agents that you can install that other people have built. Anything that you install on Dreamer, you can actually just say, I wanna start making some changes, and we'll look at that in a second. But in natural language, with the sidekicks help, you can change any of these experiences to work just the way you want them.[00:07:18] But the base layer of the system are tools. So you know, as well as anyone swyx, that any AI system is only as good as the quality of data that it can pull in and the quality of action it can take. So before we launched our beta, we worked very hard to make sure that we seeded our tools with a bunch of very high quality and powerful integrations.[00:07:39] So, you know, for instance, this is real Google search, this is actual Gmail. Um, and you can do very useful things with those. But also this is a platform for everyone. And as we got started talking to people in our alpha community, a whole bunch of sports use cases popped out and we realized if you want to build something cool for sports with ai, you need really high quality live data.[00:07:58] So look at these [00:08:00] Formula one M-L-B-N-F-L, uh, these are tools, uh, that we've built. We've done a, these are not data scraped off the web. This is a, a direct data feed integration. And because it's live and ‘cause it's high quality, you can build really powerful stuff. But tools is not something that we are just going to kind of control ourselves.[00:08:19] The platform is open for tool Builders to contribute tools that anyone on Dreamer can use. So, um, this is actually the place in the platform where I think software engineers, um, well number one, would love for you to come and play with it. Uh, but software engineers are really gonna build, um, a lot of powerful stuff into the system.[00:08:38] And we are actually sharing something for the first time on this podcast, which there is, uh, tool builders on Dreamer get paid. So if you publish a tool to the platform and a lot of agents use it, you'll actually get paid, uh, in proportion to their usage. And we'd love for folks to come and give this a try.[00:08:54] We've got good docs that help you get started and you can build things that, you know, scratch your own itch. For instance, someone built this [00:09:00] Ski Bum tool, which provides live snow conditions for a bunch of, uh, ski resorts. I'd love to show you how I've used that in a second. And also we have some tools, partners where the tools themselves are paper use.[00:09:12] So for instance, parallel web systems is a premium tool. Uh, you can do really cool stuff with it. Um, it's a a, an agentic web research tool. And that one, because it's expensive to operate, is paid on a, on a per usage basis. But if you're coming in to build agents on the platform, even the premium tools, you get a free trial.[00:09:29] So you get a chance to actually try them out, make sure that the use case is good for you before you decide to, to to sign up. So that's tools. So we have the gallery, we have tools, and then the sidekick helps us put all of this together to build agents. We do that in the agents studio. You can also do this on your phone, but if I open up Agent Studio here on Desktop psychic's, just gonna start a conversation about what you want to build together.[00:09:51] I'd love to show you one that I made recently.[00:09:53] swyx: Let's do[00:09:53] David Singleton: it.[00:09:53] Building A Conference App[00:09:53] David Singleton: Um, let's look at something that hopefully is kind of near and dear to your heart. So one of the things I love about Dreamer and this kind of moment in technology is that if you think about it. There are all these things in your life where, have you ever gone to a conference?[00:10:09] I know you have. Right? And, uh, big conferences have apps. Um, and these apps are usually built by agencies and they're, they're usually actually quite expensive to build. I've been involved in running some of these myself. And how many conferences have you been to where the app was good? Zero. Honestly.[00:10:23] swyx: Exactly. Zero,[00:10:24] David Singleton: maybe one. I, I've, I've been to one conference. That was pretty good. Wait, wait session sessions. Um, but, but the point is, they're rarely great pieces of software. Right. And they're also expensive to build, but they're, they're interesting ‘cause they're episodic, they last for this one thing. Um, and then they're, they're not relevant anymore.[00:10:43] Um,[00:10:43] swyx: and so it's the worst feeling to invest in them because, you know, it's like, it's got a limited. Date?[00:10:48] David Singleton: Absolutely. So I decided to build, uh, a conference app for your AI engineer conference. Amazing. Uh, on Dreamer. One of the things that Swix has done, uh, which I [00:11:00] thought was very forward-looking, is actually put a whole bunch of data about the conference on the webpage in an LLM readable way.[00:11:06] There's an LLMs txt file, there's a feed of all of the sessions in js, ON. So I used the data from your conference last year and built this intelligent app, uh, just by talking to our sidekick, uh, in Dreamer. So just to give you a quick tour, this is my Dream Conference app. What I always wanna do for conferences is I wanna be able to search for speakers.[00:11:28] I'm usually there because, uh, there, uh, is a speaker I care about. So, you know, SWIX, you're the speaker I care about. I can actually see here who you're on stage with. So here's, here's Greg Brockman. You've read even ai, uh, and this is his session. And look Greg and Swix for the speaker. So let's add that to my schedule.[00:11:45] Great. And then maybe there's a couple others I might see here. Like on day two, I remember there were some keynotes. So, uh, building the open agenda web, that sounds fun. So I add that to my schedule.[00:11:55] swyx: She's now CEO of Xbox.[00:11:56] David Singleton: Awesome.[00:11:57] swyx: Which is interesting. So cool. So,[00:11:59] David Singleton: so I've [00:12:00] gone through and picked out a couple of sessions that I cared about.[00:12:03] That's as far as I usually get with any conference app. But of course you've got the whole of the rest of the conference to figure out what to do. So here is where the native intelligence of, of these things you build on Dreamer can come in. So I'm gonna click guide me. So Dreamers sidekick actually parsed out the whole schedule and figured out what some of the themes are and I can choose what I'm interested in here.[00:12:23] I'm definitely interested in agents. Uh, I'm definitely interested in code generation and also reasoning in rl. So now I'm gonna say build my schedule. So what this is doing is. It's going across every time slot for the conference. And it's choosing among the things I could go to, which one it thinks is best for me based on my interests.[00:12:41] It also uses its own memory of me that's part of Dreamer, uh, to understand what I might like best. And you know, there's an LLM prompt running for each one of these time slots. So this is, it's not super fast, but it'll be done in about 30 or 40 seconds. And I'm gonna have a special custom schedule for the conference.[00:12:57] This, like I said, is my [00:13:00] dream conference app is exactly what I've always wanted and I was able to build this yesterday morning. Um, I did it between some meetings. I think I spent a total of 25 minutes of wall clock time on it. I did it over the course of a couple of hours. And, uh, here is my schedule for the conference.[00:13:15] I can see it in a calendar view. This is what I should do on Tuesday, this is what I should do on Wednesday. Oof, no conflicts, but, you know, I may not go to every single thing. And there you have it built in, you know, dreamer. So let's take a look at what the building experience actually looks like. So this is the, the actual account that I made it on.[00:13:32] Oh, of course I should say anything you build on Dreamer also works on your phone. So, uh, here is my AI engineer conference app right here on my phone. Got all the same functionality, and of course this is the best place to jump into my schedule.[00:13:46] swyx: Yeah.[00:13:46] David Singleton: Um,[00:13:46] swyx: so you could generate a podcast about it just completely multimodal, absolute thing, right?[00:13:51] To me, I mean, this is why I outsource, I mean, well, I, I posted the L-M-T-X-T, the JSON because you cannot run an engineer conference in 2025 [00:14:00] and not let engineers. Do whatever they want.[00:14:02] David Singleton: Yeah.[00:14:03] swyx: And since all conference apps suck, I'm just gonna put up a ba minimum viable app and just let people do whatever they want.[00:14:09] David Singleton: Totally. And the cool thing about this on Bremer is I published this to the gallery and you can use it so you've got one that's built to my taste of conference apps. I think it's pretty cool. But you might want something different. Yeah. In which case you just start telling the sidekick how to change it.[00:14:23] So let's just very quickly look[00:14:24] swyx: at our, what sports grid is also, you can fork it, right? That I can publish. That's right. I can publish your one and go, this is the base starter. It's, it's got good defaults, but go customize, whatever.[00:14:32] David Singleton: That's right. That's right.[00:14:33] swyx: Yeah.[00:14:33] Agent Studio Under The Hood[00:14:33] David Singleton: So let's take a look at how I actually built this.[00:14:34] This is real. So I'm gonna say make changes. This experience we're looking at now is our, uh, agent development studio. Um, like I said, you can do this on your phone as well. And in fact, this one I started out on desktop. Let's look at my actual prompts. I said, let's make an agent called AI Engineer Schedule Planner should be a custom schedule planner for the AI engineer conference.[00:14:53] I'm not gonna read this all up. You get, you get the point and it told it where to get the data from. So that was the first prompt. And actually after I gave it that [00:15:00] prompt, I actually had a simple version of this app working, um, after the sidekick took one turn. So the Sidekick is a, like a professional software engineer, and we've worked very hard to make this work and build functional apps for folks that might not have any engineering experience whatsoever.[00:15:14] So, you know, done here we have build logs that are technical, but you can hide those away. And sidekick, as it is building, will actually translate everything that is coming out of, uh, of the, the harness into English that you can actually read. And by the way, this English is in the personality of your sidekick, which is fun.[00:15:32] Um. And the way that we build agents and agent apps, it's a little different to what you might have seen in some other platforms for a couple of reasons. One, just the build process. The very first thing that Sidekick does, it understands all the agents you've got set up. It understands all the tools and it will come up with a plan for how to realize your goal, how to make sure it actually has the data and the capabilities to complete it.[00:15:54] It will occasionally refuse. If it can't do what you're asking, it will tell you I can't do that. It needs another tool. And that's a good [00:16:00] jumping off point for any of the tool builders out there to build a new tool. So it'll fi first figure out how, then it will build it, and then it will actually test it.[00:16:07] So it will actually make sure that the thing that it has generated is realizing your goal. And you probably know as well as anybody that anytime you can get any. Modern state-of-the-art coding model into a loop where it can make changes and perceive its own output and then fix bugs. Magic happens. So these builds, the first build will often take 10 to 15 minutes on Dreamer, which is a little bit longer than you might've seen on some other platforms.[00:16:31] But the first thing that it creates will work most of the time. And then of course, as you start making smaller changes, you can like ask it to tweak the UI in any way that you like. Those are much faster. And just to give you a sense, uh, for this one, here's something I asked. Put a logo, I gave it a logo file in static files.[00:16:48] Use that as the title. So for folks that actually really want to dig, uh, into a bit more detail, we've provided a powerful IDE here. So I can actually see here's the code that was generated and some pieces of the [00:17:00] code are more accessible than others, like the prompts. So this is the prompt that's used by a powerful LLM in order to do that schedule picking.[00:17:08] And I can actually read it here directly. I can edit it without having to ask the sidekick if I want to do that.[00:17:12] swyx: So this is very nice.[00:17:13] David Singleton: This is for the more, the more, uh, sophisticated users.[00:17:16] swyx: Yeah. This is other people's entire startup is prop management.[00:17:21] David Singleton: This is true. The other thing that is different about Dreamer is once you've built something here, it's ready to go.[00:17:28] We host it. So you don't have to worry about getting a database from a database provider signing up, getting API keys. You don't have to worry about your LLM provider tokens. All of that is hosted on the platform. And you can use it yourself. You can share it to the gallery for other people to, to riff on it.[00:17:46] You can also share it with your friends and coworkers to use your instance of the agent or agentic app. And we're seeing that happen a lot in our community. We've seen a whole bunch of folks who built little applications for their personal life [00:18:00] and shared them with their significant other. We've seen people who are building little productivity apps for their team at work and sharing it, uh, among them.[00:18:07] And we actually do this a lot inside of the company. So at this point we, we pretty much run the company on Dreamer agents for all kinds of important things. Uh, maybe a good example of that is, um, our wait list. People are signing up every time someone signs up for our wait list. A dreamer agent will actually research, uh, that person.[00:18:25] And we're looking for folks who are builders, not super technical to build agents and come in, uh, and give us a lot of feedback and we're prioritized bringing those people off of the wait list First,[00:18:35] swyx: just a quick question on that one is there's, it may not come up again. Do you find enrichment APIs to be useful like the ZoomInfo?[00:18:42] Uh, clear bit[00:18:43] David Singleton: enrichment is a very, uh, common use case. Um, on dreamer. Any application on Dreamer can kick off a sub-agent to do a particular task. Um, so this actually is a powerful agentic harness that runs inside of its own [00:19:00] vm. Uh, we call them sidekick tasks ‘cause they actually run in the context of the sidekick.[00:19:04] I'll talk more about Sidekick in a second and. Enrichment is a very common use case. And the cool thing about a sidekick task is that it has access to all the tools on the platform, but also public data as well. And so very frequently enrichment on our platform happens using public data that it can be found in the web.[00:19:24] There are some tools for getting people data, uh, from, uh, from various bespoke systems. And so that works pretty well. But actually, you'd be surprised. I mean, we would love if someone out there would like to build a ZoomInfo tool, we don't have one today. We'd love to see that on the platform, and I'm sure it'll be very powerful.[00:19:39] But we're also seeing that this powerful agent harness can pull a lot of data in on that note of tools that make experiences better, we're constantly adding more tools because people in the community are building them and publishing them. We review the tools carefully and then they go live for everybody.[00:19:54] Yesterday we added granola. And that was pretty cool. So I was talking to actually, uh, Sarah on my team was [00:20:00] talking to, uh, someone building on the platform this morning and they actually, they have an agentic app that they built, which is a kind of magic to-do list. So they put stuff on their to-do list and for each thing it kicks off one of these, uh, sidekick tasks to figure out how to move the ball forward thing.[00:20:14] Sometimes it'll complete it[00:20:15] swyx: entirely. Yeah.[00:20:16] David Singleton: Often by calling another agent on the platform and sometimes it just kind of researches it and helps ‘em take the first step.[00:20:21] swyx: Yeah. Do you know, this is Sam Altman's number one, ask for an AI app. It's the self-completing to-do list.[00:20:26] David Singleton: Yeah. The self-completing to-do list is something that a lot of people have built on Dreamer and are getting a lot of use out of.[00:20:32] Yeah. And, and finding it actually genuinely I shouldn't, I should, I should try that. Mm-hmm. Please do. And you'll even find some in the gallery that you can remix. So he was saying this morning that he's, he built this self completing to-do list, uh, on Dreamer already. But he connected the granola tool yesterday and now something really magical happens, which is when he says in meetings that he's gonna do a thing, it magically shows up on his to-do list and then it can magically get completed.[00:20:56] And then, as I mentioned, all the agents, all the [00:21:00] apps on Dreamer can actually work together. So our coding agent, as it builds them, does something very special where it exposes the internals of each of the experiences to the system. And then Sidekick can manipulate those to get stuff done. So he has built another agent, which he uses for recruiting.[00:21:18] It kind of keeps track of candidates and also it's got a kinda mini CRM function, so he's able to introduce candidates to each other. He told us this morning that something he'd committed to do in a meeting that was recorded on granola yesterday showed up in his magic to-do list and his magic to-do list.[00:21:34] It was like introduce a person for recruiting, used his recruiting agent to get it done.[00:21:39] swyx: Ah,[00:21:39] David Singleton: um, and this is, this is the dream. This is why we started the company. It really is the case that you can build and use these very powerful, bespoke experiences that can automate your life by working together. And I'd love to talk a little bit about how they work together.[00:21:55] Ecosystem Trust And Monetization[00:21:55] David Singleton: So obviously it's really cool to have [00:22:00] software that will work on your behalf, but it's only useful if you can trust it, right? So privacy and security is very important to us making these things accessible and. While also being trustworthy is hard. So the model that we have, which is working very well, is that the sidekick is at the core of everything here.[00:22:22] So it is both your companion, your helper, but it's also the traffic cup in the system. So when, when one agent wants to work with another agent and dreamer, it doesn't do it directly, it does it via the sidekick, well ask the sidekick to do the thing. And the sidekick understands both everything, all the expectations that have been set with me as a user about what agents can do, which tools I've given them permission to use.[00:22:45] And it will make sure that whatever is is going on is actually aligned with my own interests. And you know, that's part of the background that I bring to this problem domain. I've. Worked for years, uh, keeping very important information, safe and secure. And [00:23:00] so as we started to think about this problem, we realized that we actually had to build something that's a bit like an operating system.[00:23:06] You know, the sidekicks, like the kernel, the agents and apps are like users. Yeah. Different rings. Exactly. Because if you try to pick off just one piece of this, you can't actually make it work for people at scale. Uh, because you could build little vibe coded apps, but they're gonna grab all your data willy-nilly.[00:23:23] They won't be able to work together. You actually have to invest in the fundamental core in order to make it work well for people. And that's what we've been doing and it's, uh, it's been a lot of fun. One other thing I wanted to mention is, um, I've obviously talked about two things, tools and agentic apps.[00:23:42] We really designed Dreamer to be an ecosystem and a platform, and one of my favorite quotes about platforms, I think it's from Bill Gates, is that you can only be a platform. If you create more value for the folks participating and using the platform than, than the platform itself creates. [00:24:00] And that's our goal here.[00:24:01] So we at every step have been thinking about how do we make sure that other people are deriving even more value from Dreamer than we are? So in that vein, I already mentioned tool builders get paid and people can build agents that solve their needs and share them with others, and we are already thinking about ways that they can actually monetize those as well.[00:24:24] Against that backdrop, one of the things that we are launching today is our Builders in Residence program. So there are tons of people building really cool stuff and contributing it to the gallery already, but we've been really inspired by programs we've seen at other companies where artists might be in residence, people that are very creative.[00:24:43] And might have ideas outside of what the, the folks at the company or in the ecosystem already have. And so we are looking for creative people who have fun ideas and, you know, want to really figure out how to apply their creativity at the cutting edge [00:25:00] of technology today to come and work with us. So, uh, if you go to dreamer.com/latent space, you'll find, ooh, well, we love Latent space.[00:25:09] Uh, you'll find a link both to, uh, our tool Builder information and our builder in residence program. And for builders and residents, we'll let you in off the wait list quickly, build an agent, and then for a small number of, of the most creative folks, we're going to pay you to build agents. Uh, you can work directly with our team.[00:25:29] You know, this is like building Legos. So, you know, we've got some of the basic blocks together already, but if you need a Ron steering wheel and we don't have one already, like we'll build it for you. Yeah. Um, we really want to be inspired by, by these, uh, these builders in residence.[00:25:43] swyx: This Legos thing is pretty common as an analogy.[00:25:46] And there's a, there's a thing I call the master builder. Uh, we, the actual Lego company has master builders that they employ Yeah. To inspire people and post on socials.[00:25:56] David Singleton: That is exactly what inspired us as well. Honestly, we talked about the Lego Master [00:26:00] Builder program, so that's our builder in residence program.[00:26:02] swyx: Yeah.[00:26:03] David Singleton: Um, and then, uh, finally back on, on tools. Like I said, anyone can come in and build tools today. If you follow the latent space link dreamer.com/latent space, again, we'll get you off. Directly off the wait list. So you can build right away, you can monetize by publishing onto the platform. That's for everyone, the very best tool that gets added to the platform by mid-April.[00:26:23] Uh, we have a $10,000 prize that we want to give out really, because we just want to seed the creativity of everyone out there. So we're excited to do that.[00:26:31] swyx: Yeah. And you know, uh, this is completely a flywheel, right? Like the more tools, the more builders, the more the third thing agents, you know, it just feeds into each other.[00:26:39] David Singleton: That's right.[00:26:39] swyx: Yeah. Just on the payments thing, because we probably won't touch on that again, but I have to ask the former CTO Stripe on payments as presumably you're using Stripe Connect.[00:26:48] David Singleton: Yeah.[00:26:48] swyx: Um. Any pain points that you're, people are very interested in agent commerce and micropayment and all these things.[00:26:55] Presumably stable coins get into a conversation at some point, but maybe not now.[00:26:58] David Singleton: Yeah, we are [00:27:00] really, really excited about e agent commerce. The first step we are taking is help people in the world who have never been able to build these kind of experiences and software before to build stuff that meets their passions, share it with the world and get paid.[00:27:14] So that's all commerce that happens on our platform, and so we don't need anything new to facilitate that. Stripe Connect has existed for quite a while and is the perfect solution for this kind of stuff, so, um, we we're excited about that. First and foremost, however. A lot of the things that people are already doing on Dreamer, we just talked about a self-completing to-do list.[00:27:34] A lot of the ways that you want to complete to-dos is by actually closing the loop in the real world, and that's going to involve the exchange of value. So we have some folks that are building tools already that actually do have money move in order to, to complete that, that loop. So far, we just want to be open and agnostic to all the protocols out there.[00:27:54] I honestly think this moment in time is a little bit like the early web. So I personally started coding as a kid [00:28:00] and I think I got access to the internet in about 19 95, 19 96. And back then, uh, the web existed, you know, HTTP was a protocol, but there were also other protocols I was using all the time, like Gopher and UUCP and uh, various others.[00:28:15] So the point is like the web, HTTP and HTML. Was just one among many protocols. And of course it became the winner and it's awesome. Yeah. Um, but the others were also kind of interesting and viable at the time as well. And I think the world of agentic commerce is like this right now. Also,[00:28:30] swyx: acp.[00:28:31] David Singleton: Acp, exactly.[00:28:32] All the, all the cps, you know, on Dreamer. We hope that folks will build tools that kinda make use of all of these things, but I'm sure that at a certain point. One or two will emerge as the winners, and then we'll be able to build like really deep support in,[00:28:44] swyx: yeah. This is like maybe a complete tangent, but I do think about how a lot of these companies in AI companies in particular have to switch from c based to usage based because of course, but then, then they end up, end up having to sort of [00:29:00] obscure the margins a little bit and then they inventing end up inventing their equivalent of rob robots.[00:29:04] David Singleton: Mm-hmm.[00:29:04] swyx: Uh, where they're like, well, okay, well every company should have their own currency. And it's, it's like very short lead to a token.[00:29:11] David Singleton: Yeah.[00:29:11] swyx: Or, and I'm like, okay, well where does this end? I can't really play out the next step as to like, is this chaos? Is this,[00:29:18] David Singleton: yeah.[00:29:18] swyx: Okay.[00:29:18] David Singleton: Well, I think it is kind of like the wild west.[00:29:21] I don't mean that in a completely, it's all completely disorganized way, but there's just so many things that could happen from here. The Overton window is very wide, right? Not far how this might land. And I'm just very excited to be building a platform that can take advantage of all of those opportunities and we're just gonna be there.[00:29:36] Uh, working for our users to make sure that things that emerge work,[00:29:39] swyx: you're gonna own the consumers, you're gonna be up the OS for the app store for everything.[00:29:43] David Singleton: So one of the ways to think about this is, um, dreamer actually uses all of the state-of-the-art models as a user. You don't have to think about should I be using, you know, Opus four six, or should I be using the five four model from [00:30:00] OpenAI?[00:30:00] We are continually doing evals and so forth to make sure that the best things are there for you. You can just build on the platform and know that as the world ships around, you're gonna get the right stuff for you. Um, and I think that's something that is needed to actually have folks take advantage of this technology at scale.[00:30:19] I'd love to show you another example of something I built.[00:30:21] swyx: Let's do it.[00:30:22] David Singleton: This is another example of software that just lasts for a certain moment in time. So recently I went on a ski trip with a bunch of friends,[00:30:31] ski[00:30:31] David Singleton: Bum. Uh, so it uses ski bum. Yes. I went on a ski trip to Big Sky. I'd never been there before.[00:30:38] And I made this little intelligent app for us. And you can see it says it's loading big sky conditions. So it's actually calling the Ski Bum tool that I just showed you, which is, uh, published in our, uh, in our gallery. So what is this? This is a little app that was just for our weekend trip. It shows the current status of all the lifts of Big Sky.[00:30:54] Using that tool from the ecosystem, it shows the forecast for the upcoming weekend. It shows our [00:31:00] accommodation. This is just like where my group was staying. This is just for us and also a bunch of dining information that one of our friends, uh, put together who, who's an expert on Big Sky. So I was able to take this app, share the link with my friends.[00:31:12] They weren't on Dreamer yet, just send it to them on iMessage and they get a version they can use on their phone. And of course, here's the real kicker. So I've been on ski trips before and other weekend adventures with my friends. Yeah, people pay for different things and at the end of the weekend it's always a pain to figure out who needs to pay, who to settle up.[00:31:29] So we use this during the weekend. We added all of our expenses in here. Uh, too close are it's drill data. It's only too closely. And then at the end of the trip, we press split. And we're, we settled up and we're done. So there's another dreamer. This was all through dreamer. So the, the actual payment? No, no.[00:31:47] We, it happened because, because we paid for stuff in the real world, it was like, okay, this person needs to pay that person 20 bucks. Right? Right. This person already paid in that. Right. So it just helped us all settle up. We didn't move the money on Dreamer. You could do that. And in fact, if you're a tool builder [00:32:00] thinking about this and getting excited, like come build a tool to do that stuff.[00:32:02] We really think of our tool builders as design partners.[00:32:05] swyx: Yeah. I got, I got the tool. Uh, what, like, I hate, I use Bank of America. I hate bank, I hate the app. Mm-hmm. I hate the web. All banking websites just horrible.[00:32:13] David Singleton: Yeah.[00:32:13] swyx: So just build me, like build a thing on top of Plaid.[00:32:15] David Singleton: Yeah. Right. And then just So[00:32:17] swyx: five code by banking app,[00:32:18] David Singleton: there's already a tool for that.[00:32:20] Oh. So, um, attain Finance is a tool, a builder in our community built. Okay. Um, and it uses a secure system like Plaid. To access your, uh, financial data and you can build powerful personal finance agents on Dreamer today using this tool. And like I said, we review tools carefully. So when bringing Attain Finance onto the platform, we did actually quite a detailed security review with that company to make sure that if folks build stuff with it, it's, it's gonna work well.[00:32:49] So yeah, check that out. I think, uh, I'm, I'm pretty certain it connects to Bank of America. So you'll be able to build the, the app that you wanted already?[00:32:55] swyx: Yeah. There's a couple of points I wanted to sort of dive in on, maybe highlight to folks, [00:33:00] because I, obviously, I spent more time with Dreamers. So we're making a point where you choose on behalf of your users because they're meant to be consumers.[00:33:07] So maybe less technical,[00:33:08] David Singleton: right?[00:33:08] swyx: But obviously people can, how users can override. If you read that's, but it's not just lms, it is also the, the transcription. It, it's like all, like there's, there's a first party curated set of here's the house opinion. That's right. On what?[00:33:21] David Singleton: That's[00:33:21] swyx: right. The thing is, that's right.[00:33:22] Is what's the list? Is there like,[00:33:24] David Singleton: yeah, so actually if you look in the tool gallery, the first party kind of curated set are all the ones that have these grayscale icons. So we have a built in tool for image understanding, for image generation, for RSS, exploration, text to speech and so forth.[00:33:38] swyx: Recipes.[00:33:39] David Singleton: Uh, we actually do have a built in recipes tool.[00:33:41] It turns out that a lot of people in our alpha wanted to do stuff for cooking. Yeah. Um, and you know, you can scrape the web to get good recipes, but we were able to quite quickly find a good repository of recipes. It works great here. Yeah.[00:33:55] Stable Tool Interfaces[00:33:55] David Singleton: So the point behind these though is that we'll keep the interfaces stable, so they'll always work.[00:34:00] But you know, the best translation model and, you know, there are people using this translation tool to translate Chinese podcasts into English. It's, it's pretty powerful. It can deal with very long text, but the best translation tool today might be different from the best translation tool sometime next year.[00:34:15] And we're just gonna make sure that that translation tool is always pretty close to state of the art. So you can build something and you know it's gonna continue to work well. Of course, some of our tools are branded. You may actually have a preferred way of buying groceries, like maybe you prefer Instacart and that's great.[00:34:29] You can use the Instacart tool specifically.[00:34:31] swyx: Yeah.[00:34:32] Partnerships And Ecosystem[00:34:32] swyx: Your partnerships, uh, I mean, I don't know if you ever hit of partnerships, but this is gonna be a bonanza for anyone on to do deals.[00:34:38] David Singleton: We have an amazing person who, uh, works on all of our partnerships. Um, and it's part of what you have to do to build a platform like this that's gonna work for people.[00:34:46] Like, we've gone and done that. Schlep has a lot of work, one talks lots of different companies, um, in order to make sure that you've got good tools at the core.[00:34:54] swyx: Yeah.[00:34:54] David Singleton: And then of course, because we're open to tool builders contributing to the platform, this is only gonna get better and better and [00:35:00] better.[00:35:00] swyx: Yeah.[00:35:01] Agent Lab Routing Layer[00:35:01] swyx: One observation I have this, this is gonna master a thesis I've been pursuing, which is, uh, what I've been calling an agent lab[00:35:05] David Singleton: mm-hmm.[00:35:06] swyx: Where you sort of different than a model lab in, in, in the sense that you never train your own models, but you are the router evaluation layer, ex subject domain expert for choosing between, uh, models.[00:35:18] David Singleton: Yeah.[00:35:18] swyx: And you're explicitly doing these things. And so like in my sort of construction, every agent lab does some version of this where like, here's the image understanding endpoint and we will route for you and don't worry about it. Yeah. Sally, I think it's kind of cool.[00:35:32] David Singleton: I, I think it makes total sense. Um, and again, to make this work for folks that don't follow the AI news every day, it's an actually, it's a, it's a really important thing to do.[00:35:42] Yeah. And it, it's been, it's been a real pleasure. I mean, I'm a, I'm personally a total geek for this stuff. I love it. And being able to go and dive into all those details in order to make it work well for other people. It's a true pleasure. I cannot imagine working at anything else right now. It's just so much fun.[00:35:56] swyx: The tricky part is multimodality when some of these things do [00:36:00] merge.[00:36:00] David Singleton: Mm-hmm.[00:36:01] swyx: And you are, you're sort of, this is your imposing structure on things that fundamentally don't want to be structured. And so sometimes that might work against you, but for 99% of these cases, this is fine.[00:36:10] David Singleton: Yeah. I mean, I think it's gonna be very interesting to see how the, the, the world matures because a lot of the power of dreamer is the ability to kick off these subagents, so these powerful agent harnesses, which can actually change how they work based on the data.[00:36:25] I actually think that we will be able to. Kind of keep up with and stay at the forefront of the changing landscape of how tools and systems work together. And that's, that's new. You know, software didn't used to work like this and now it does. Um, so even, even just figuring out how to design the right pri to make that possible has itself be a lot of fun.[00:36:44] Builders Can Publish Tools[00:36:44] swyx: This is, is a sort of maybe two part question that why can't streamer make its own tools? And then why don't you let you builders maybe stand up their own routing group? I call this a routing group, right? Like where it's like collect Yeah. Things.[00:36:58] David Singleton: So two things, to [00:37:00] some extent, dreamer does make its own tools in that agents appear to the system as tools.[00:37:05] So they can be, they can be used to accomplish things. So you can build an agent that is essentially a tool. Yeah. Um, and it it,[00:37:12] swyx: which is to me very useful for reuse.[00:37:14] David Singleton: Right.[00:37:14] swyx: Right. Exactly. ‘cause I, I like, this is the way I like it. Now my next five apps, I don't want to do this whole series of back and forth again.[00:37:20] David Singleton: Right.[00:37:21] swyx: Yeah.[00:37:21] David Singleton: Um. Then at the tool layer of the system, it's open to anyone. So it's actually quite powerful and flexible. So if you wanted to add a tool, which was, uh, imagine that you were training your own foundation model, Swyx. That might be fun. And imagine you wanted people to be able to play with, I don't know, maybe you make like, you know, nano chat or whatever and you want to Yeah.[00:37:42] Let people play with your own nano chat and see how I change themselves.[00:37:44] swyx: Now.[00:37:45] David Singleton: You could, you could publish a tool that is Nano Chat and it nano image generation behind a tool, and it could be your own writer if you wanted to. I see. And honestly, if that's the kind of thing that gets you excited as a builder, please come and do it.[00:37:57] Like we, we really are [00:38:00] believers in this idea that we aren't going to figure out every single detail ourselves. We're gonna make sure it's a safe and fun place to build this stuff, but we're really open to these ideas coming from other people. Um, and so I'd like nothing more than you come in and build a tool that does some of that cool stuff that you, that you have in mind.[00:38:15] swyx: Yeah. Awesome.[00:38:16] David Singleton: And just as a reminder, if you'd like to do that, the way to find the links is dreamer.com/latent space. Um, and for a limited time on that page, um, anyone who's listening to this podcast will also get directly off of our wait list. Uh, it's quite long right now. We are working hard to bring Zika.[00:38:32] Wait, so skip the wait list.[00:38:33] swyx: You know, I think, I think that's fantastic. I, I think it's, it is really sort of probuild way to do it. I wanted to jump back to the, the bar. Yeah. You know, you know, I get excited about this.[00:38:41] David Singleton: Yes. Okay. Let's set it back in there.[00:38:43] swyx: Like, let's, you know, this is the engineer podcast that's get[00:38:46] David Singleton: Yeah.[00:38:46] swyx: As technical as you can.[00:38:47] David Singleton: Yeah.[00:38:47] swyx: On everything you've built, like have a show off.[00:38:50] David Singleton: Yeah. Okay.[00:38:51] Under The Hood Debugging[00:38:51] David Singleton: So let's go wild in the aisles in the Asian studio. So as you can see, over on the left here is a conversation with the sidekick where you ask it what to do and it will explain in English that anyone can understand what's going on.[00:39:03] But, um, if you want to pull back the covers and look under the hood, um, if you're, uh, an engineer like me, then we have this, uh, this kind of debug drawer at the bottom. So you can see the full build logs here, but you can actually also dig in and see the files and prompts that have been generated. Uh, you can upload files from your computer in static files.[00:39:24] Um,[00:39:24] swyx: very important,[00:39:25] David Singleton: uh, indeed. You can actually read the prompts that have been generated for you. We intentionally put an example in here just that you can see what the format looks like. And then, you know, we already looked at this one that was generated for this particular, um, app, but if you actually want to bring the code out of Dreamer and work on your own local machine, you can.[00:39:45] So at the core of everything here is an SDK with a powerful command line interface and we built that first. It's actually possible to build agents on Dreamer without talking to the sidekick. You can write code with your fingers on a keyboard if you want to. I know that's very [00:40:00] antiquated, not, but actually this can be a lot of fun.[00:40:02] So if you wanna pull it out onto your laptop, you can use our, our CLI and, uh, you can edit it in cursor or in cloud code. You know, you don't have to use our sidekick. And the CLI actually has full access to the rest of the platform with you as the user. So, you know, obviously it is, uh, secure and privacy sensitive, and this is a way that, um, some of our most technical builders do build stuff on the platform.[00:40:24] The really cool thing is the side cake. When it's in coding mode, it uses exactly the same CLI. So the way it. Build stuff on Dreamer is using the same tools that you might as an engineer. Um, and that's actually a very powerful abstraction because it turns out that the right way to give a lot of context to agents to use CLIs is to write great documentation.[00:40:46] Make sure that all of the things that you could do are actually possible. And guess what? That makes it a delightful developer experience for real heroes as well.[00:40:53] swyx: Yeah. So that's pretty cool. We've been telling developers to do this and they ignore this until now they have to for content.[00:40:58] David Singleton: I, I've been saying this for a [00:41:00] long time.[00:41:00] Uh, we actually Stripe docs.[00:41:02] swyx: I mean, come on. Absolutely. Come on.[00:41:03] David Singleton: Absolutely. But actually, I was chatting with folks at Stripe last week and saying, Hey, you gotta make the Stripe CLI actually tell agents what they can do on Stripe because that way they're gonna use more stuff on Stripe. I think this is a real trend for the entire industry.[00:41:16] swyx: Yeah.[00:41:16] David Singleton: So we, we've been doing that.[00:41:17] swyx: To me, this, this download and, uh, GI push mm-hmm. Everything is complete confidence in that you're not hacking it. Right. Because there's other, let's call them AI builder platforms that impose their stack on you and if you, if you, and so therefore they don't allow you to do this because they cannot.[00:41:34] Right. ‘cause they, they impose some degrees of freedom, uh, restrictions so that they can get it to work. Yours is a fully general like VM running the full code. Correct. Do whatever you want. Correct. Any language you want. Correct. Yeah.[00:41:46] David Singleton: Correct. Well, in terms of language, if you use the SDK, you could build stuff in other languages.[00:41:51] We've actually found that TypeScript is the best language for building these experiences. Yes. Because it's strongly tight. So you find out at compile time if you've made mistakes [00:42:00] and there's nothing better than getting in. A coding agent in a loop where it can see its mistakes and ask them. So TypeScript is the language that everything gets built in by default here.[00:42:08] swyx: Did And did you see that TypeScript overtook Python? I did. I did. Yeah.[00:42:12] David Singleton: And for what it's worth, when we started the company, we started writing stuff in Python, and I love Python. Um, if I do, uh, a vendor code, I always write it in Python. It's my favorite language as a developer with my fingers on the keyboard.[00:42:23] Um, but TypeScript is an amazing language for AI because there's tons of training data in the models, um, and it's strongly tight. And actually at the company we built most of the stack in TypeScript, and we have this amazing property, which is, we have type safety all the way from the database to the front end.[00:42:40] And there's nothing better for working with coding agents than being able to have them check their correctness, compile time. So the same ideas behind building the company's code base, we've put into the agent SDK here as well.[00:42:51] swyx: Yeah. Do you know if you'd use one of those tools, like Prisma or whatever, or is it Tool Lab for you?[00:42:55] David Singleton: We, we actually have crafted most of our own tools. Um. For [00:43:00] instance, we had LLM Driven Code Review, uh, before the thing that got published from philanthropic this week. You know, we, we've been doing this stuff, uh, on our own bat[00:43:07] swyx: email, we'll pay $25 per review.[00:43:09] David Singleton: We, we pay a lot less than that. However, I hear that those reviews are excellent and possibly worth $25.[00:43:14] swyx: Yeah. You know, it's an option. Right. It's good, good to have it.[00:43:17] David Singleton: Just to give you a tour of some other stuff here. So, um, I can also see all the versions. Yeah. Um, this is not gi, this is not gi, this is built into dreamer. I can see all the versions that have been pushed before. Why is it[00:43:27] swyx: not gi?[00:43:28] David Singleton: It's not gi because we can make it work more efficiently than Git.[00:43:32] And we actually, we do some work behind the scenes to kind of understand what's in each of these versions. Yeah. Um,[00:43:37] swyx: so one of the things I'm pursuing, and I have a lot of thesis, right? Mm-hmm. One of the thesis is like, does GI go away? Does GitHub go away? And like, what, what is the active reinvent[00:43:46] David Singleton: you for, for what it's worth to some extent.[00:43:48] And anything you build, there's a lot of path dependency. If we started over, we might make this gi There's, uh, you know, within the company we use, uh. For our, you know, platform source code. And we like it and it [00:44:00] works well with coding agents as well. The very first versions of this, we wanted to be able to make it possible for the sidekick to manipulate it easily.[00:44:06] Um, and this, this was an expedient way to do it.[00:44:08] swyx: Yeah.[00:44:08] Workflows Logs And Databases[00:44:08] David Singleton: Um, you can also see all the activity that has happened in the workflows that you build. A lot of agents, you'll build on Dreamer, do things in the background, so they run on triggers. These are stimuli from the outside to kick them off, and this is a nice way to see all of the things that might have kicked off your agent.[00:44:24] You know, you can have an agent that kicks off on a webhook, so you can plug it into external systems. You can have an agent that runs when you receive certain emails that match filters, including LLM filters. And so here you can see, oh, when did it run? What did it do? You know, if I open up one of these guide me prompts or guide me, uh, events.[00:44:41] Oh my can see God. Well, I told you it was calling an LLM for every one of those time slots. Here's all of the LLM calls, here's the actual prompts.[00:44:49] swyx: And you don't mind exposing all of this, right?[00:44:51] David Singleton: No. We want builders to see what's going on under the hood. It's haiku to,[00:44:53] swyx: okay. Yeah. So,[00:44:54] David Singleton: okay. Right now that one was haiku.[00:44:56] Like I said, we work with all the models and sidekick will actually pick the best one [00:45:00] for the job. And you saw that was pretty high quality and pretty fast. So Haiku four five is the one that it picked for that job. Exactly. Uh, we also have logs, as I mentioned, there's a database spun up on demand for every, uh, agent.[00:45:12] You don't have to go and figure out how to do your own hosting. This is a SQL Light. This is a SQL Light database. Yeah. Um, it's a multi-user SQL light database. And then, uh, but, but each one is you, you get a database that is unique to this agent. But then if you share the agent with multiple people, we take care of like who are the owners in each row?[00:45:31] And all of that stuff is just there outta the box. Um,[00:45:34] swyx: and again, in-house?[00:45:35] David Singleton: In-house.[00:45:36] swyx: Oh my God.[00:45:37] David Singleton: Yeah. Um, well we do work with a bunch of infrastructure providers, but the technology for how to manipulate this is in-house. Fun fact. We actually did a lot of our own infrastructure development early on at the company and realized we need to spend our energy in the stuff that we're uniquely doing in the world.[00:45:53] So we're very delighted to partner with a bunch of great designer and some of this stuff. And then finally, um, I mentioned that agentic apps agents [00:46:00] expose all of their internals to the system so the psychic can manipulate them and use them just like a user can. So you can see how it's decided to break this problem up into functions.[00:46:09] Some of the functions, the ones with the little I here are exported. That means that there's probably the visible from outside. Exactly. And others are internal. And if you want to, you can dig right in here and call individual functions and see what happens. But mostly. You don't need to think about that at all.[00:46:24] Yeah. Uh, you can keep that little drawer closed and you can talk to your sidekick and build really powerful and enchanting experiences.[00:46:30] swyx: Yeah. I mean, to me, like showing this gives the engineer a complete mental model of what you've done and what you can do with it. Yeah. For example, the first thing I, I, I look for.[00:46:39] A mental checklist of things, right? Like is off in the database, off looks like it's not right. So that's a separate layer. That's probably me means it's hard to do multi-user apps on the same app, right?[00:46:50] David Singleton: So you actually, we've solved that. So, um, see, yes, the platform builds in off, so you as a user sign into the platform, if you're using an [00:47:00] agent that was published by someone else, then your identity is, is kind of taken care of by the system.[00:47:05] And when you query the database, you're gonna get the stuff that is for you. Unless the builder specifically said, this is public data that everyone should see. So they, they actually get a chance to think about that. And again, sidekick can guide you through building, uh, agents and apps that work that way.[00:47:19] So you're right, that's another thing that people have to think about when they're trying to figure out how to build software experiences on Dreamer. You, it's built in. You talk to the sidekick as if it were a human being about what you want and that's what you get. So, you know, my, my Big Sky app that I just showed you that was designed for multiple people to use it.[00:47:38] And of course the things that we were putting in as expenses were supposed to be visible to everybody, and I just told the sidekick that's the way I wanted it. Uh, but by default, if I built an app like that, the data from each user would not been visible to the others.[00:47:49] swyx: Yeah. Yeah. Uh, this is, I presume this is a mood question, but basically you've had to build your own coding agent, right?[00:47:55] Which is sidekick slash whatever is in Inside Psychic. Obviously there's a lot of [00:48:00] people with a lot of desire for cloud code and Code X and attachment to it. Mm-hmm. I know under the hood data basically reduced to a loop, but like, would you let people use cloud coding and Code X or is the harness too specialized?[00:48:12] David Singleton: Yeah. If you, if you want to use, um, cloud code and Code X, then you go down here. Yeah. Hit get the S St K. And we even say this right here, edits your heart's content Z cursor code.[00:48:22] swyx: Like people want to use it inside of Ick, right? Yeah. They want to switch the engine.[00:48:26] David Singleton: Yeah.[00:48:26] swyx: That's the coding engine.[00:48:27] David Singleton: Yeah. We are not doing that right now.[00:48:29] Um, you know, again, the goal really is abstract the complexity. Yeah. Um, because the real target for. Building agentic apps is folks who can't do this already today. I can't tell you how many users in our community I've spoken to who are like Dreamer has changed my life because I used to have all these ideas.[00:48:50] If only I could find an engineer to help me implement them, I'd be able to get them done. They're free, and now I can talk to my sidekick and, and get it built. I think that's like really how we think [00:49:00] about the people that should get a ton of value and fun, um, out of the platform. And so they're not asking to be able to plug in their their own, you know, coding agent.[00:49:11] And for those folks, the opportunity is massive. If you've never been able to do stuff in code, now you can build stuff for you, for your friends, for your family, for your coworkers. And also there's a huge opportunity for folks who do build stuff in code to actually contribute to this ecosystem. So that's how we think about it.[00:49:28] swyx: Yeah. Amazing.[00:49:28] Personalization And Memory[00:49:28] swyx: That's most of what I wanted to cover Dreamer wise. I think personalization and memory yeah. Is probably like the single most important job of, uh, of the os. Maybe we could talk about that and then I'll, I wanted to zoom out on company building stuff.[00:49:40] David Singleton: Yeah, yeah. Sounds good.[00:49:41] swyx: Yeah. So how do you handle memory?[00:49:43] What, yeah, what have you found? What have you tried and failed?[00:49:45] David Singleton: Yeah. Okay. So, uh, first of all, at the core of dreamer is the sidekick. The sidekick gets to know you and it builds up a memory about you over time, and that turns out to be very important. So Dreamer, that's

Проверяем знания кандидата на позицию Senior DevOps инженера в прямом эфире. В этом выпуске: архитектурные паттерны в AWS, вечный спор Terraform против CloudFormation, глубокое погружение в Kubernetes (Karpenter, скейлинг) и Live-траблшутинг сломанного Helm-чарта. О ЧЁМ ВЫПУСК: • Архитектура и облака: Как выбрать между EKS и ECS/Fargate и настроить безопасное хранение бэкапов в S3.  • IaC войны: Честное сравнение Terraform и CloudFormation — где заканчивается удобство и начинается боль.  • Kubernetes под капотом: Разбираем Control Plane, работу контроллеров и нюансы обновления on-prem кластеров.  • Live Debug: Реальная задача по починке упавшего пода (CrashLoopBackOff) — работа с пробами, портами и Helm.  • CI/CD стратегии: Строим идеальный пайплайн с GitHub Actions и ArgoCD. ГОСТЬ: Максим — DevOps-инженер (5 лет опыта DevOps, 10 лет SysAdmin). Стек: AWS, Terraform, Kubernetes, Ansible, Monitoring. ССЫЛКИ

Visit the Adafruit shop online - http://www.adafruit.com ----------------------------------------- LIVE CHAT IS HERE! http://adafru.it/discord Subscribe to Adafruit on YouTube: http://adafru.it/subscribe New tutorials on the Adafruit Learning System: http://learn.adafruit.com/ -----------------------------------------

Send us a textMost parenting advice is fluff. This episode is the engineering manual you actually need.We break down the newborn phase into a solvable system, stripping away the "perfect parent" myths to give you the tactical cheats, sleep hacks, and gear protocols that actually work. If you are drowning in contradictory advice, this is your clarity.Our guest for the show is The Nurse Zeina.In this episode:The "Debug" Protocol: A step-by-step checklist to identify exactly why your baby is crying (and how to fix it fast).Sleep Engineering: Why "drowsy but awake" is often a lie, and the specific noise/light settings to trick a newborn's biological clock.The 5 S's Mechanic: You're probably doing the swaddle wrong. We explain the physics of firm pressure vs. gentle wrapping.Gear Audit: The 2 things you absolutely need to buy, and the 5 things that are a total waste of money.The "Shift Work" Strategy: How to structure your night so both parents actually get REM sleep.Join the conversation: Are you Team Schedule or Team Go-With-The-Flow? Let us know in the comments if you treat parenting like a mission or a journey.Follow us on social media:- Instagram: @motivateme313 or @ozmedia313- Website: ozmedia313.com- Facebook: ozmedia313-TikTok: @ozmedia313-Apple Podcast: ozmedia-Spotify Podcast: ozmediaThis show was sponsored by:-The Family Doc https://thefamilydocmi.com/-Juice Box Juiceboxblend.com-Holy Bowly http://www.myholybowly.com-Wingfellas thewingfellas.com-Hanley International Academy https://www.hanleyacademy.com-Malek Al-Kabob malekalkabob.com-Bayt Al Mocha https://baytalmocha.com/-Chill Box https://www.chillboxstore.com/-Royal Kabob https://www.royalkabob.com/-GEE Preparatory Academy https://www.gee-edu.com/schools/geepreparatory/index#newbornhacks #sleeptraining #parentingtips #newdad #babyessentials #ferbermethod #newbornsleep #parentingadvice #ozmedia #dadlife

פרק מספר 510 של רברס עם פלטפורמה, שהוקלט ב-6 בינואר 2026. אורי ורן מקליטים בכרכור ומארחים את טל (מאזין ותיק!) מחברת Rhino Federated Computing לשיחה על עולם של חישוב מבוזר, פרטיות רפואית, הצפנות הומומורפיות ונוסטלגיה ל-SETI@home (ולא AI! טוב, גם…).

In this episode of the Snowpal podcast, Dr. Adam Link, founder of Fireweed Capital, shares his unique journey from software engineering to wealth management. He discusses common financial mistakes engineers make, the differences between active and passive investment strategies, and the importance of personality in financial decision-making. Dr. Link also highlights the tools and technologies used in wealth management and explores the future of trading in the context of AI and 24/7 markets. The conversation concludes with insights on how individuals should approach investing based on their personal circumstances.

In this episode, I'm chatting with Precious Kolawole, who moved from Nigeria to Canada through the Shopify Dev Degree program, and has also seen her TEDx talk “How coding can change your life-and the world” go viral.There's a trap that awaits most immigrants. It's subtle, and it sounds like self-awareness: Maybe they won't pick me because of my accent. Maybe I don't belong here. Maybe I should expect less.Precious knows this too well. She describes sitting before a performance review at Shopify, telling herself to calm down, preparing for disappointment despite knowing she'd worked harder than anyone. When her supervisors told her she'd earned the highest rating, she screamed on the call. They paused, confused. Why this reaction? Because she'd already decided she wouldn't get it. “It's very funny how we think,” she says. “We think too much. We're immigrants.”But what makes Precious different is how she reorients herself. She traces it back to coding, specifically, to debugging. When you debug code, errors are problems that always have a solution, that's if you're willing to keep looking.And that mindset has carried into how she approaches her immigration journey in Canada.Precious and I dig into:Leaving behind a medical degree, a Microsoft Nigeria offer, and communities she foundedHow her family stays connected across four countries through mandatory Sunday callsWhy Canada's talent visa puts power in employers' hands, and what that costs the countryThe Nobel Prize effect and the danger of letting success make you comfortable

On parle beaucoup de “crise de régime”, de “tensions politiques”, de “fin de cycle”…Mais qu'est-ce que tout cela veut dire, concrètement ? Et surtout : d'où vient cette crise ?

Tu connais ce moment où tu sens que tu replonges dans le triangle de Karpman (entre sauveur, victime et persécuteur) et que tu ne sais plus comment t'en sortir ?

Scott and Wes dive into Chrome's new MCP server; a dev tools API powered by Puppeteer that gives your scripts, editors, and AI agents full access to Chrome. They break down how it works, what it can (and can't) do, and how it might change debugging and automation for developers Show Notes 00:00 Welcome to Syntax! 01:15 Syntax San Francisco Meetup. 01:55 We need your Spooky Stories! 02:42 What is an MCP Server? 04:28 MCP servers are not only for code editors. 06:43 Brought to you by Sentry.io. 07:49 Dev Tools MCP is similar to Puppeteer. 09:20 Setting up an MCP Server. 11:36 Example of MCP with Dominos Pizza. 13:23 Accessing Dev tools from your editor. 14:23 In VS Code, you can “Open Link”. 15:22 Using the MCP server. 16:26 Chrome has Debug insights inside of chrome's dev tools. 18:38 Real world things the Chrome MCP server can do. 18:43 Analyzing performance. 19:55 Taking screenshots. 21:17 Performance fix feedback loop. 22:33 Remote connecting browsers. 24:54 Browser-use. 25:18 What are the limitations? Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Tu te demandes souvent si les problématiques que rencontrent tes bénéficiaires sont individuelles ou systémiques ?Tu oscillés entre “c'est dans leur vécu perso” et “c'est la société qui les met dedans”… et tu finis par te sentir un peu perdu·e.Dans cet épisode, je t'emmène dans un voyage philosophique et pratique pour te montrer pourquoi la réponse n'est pas ou/ou, mais et/et.On parle d'idéalisme, de matérialisme, de dualisme et de monisme, pour arriver au matérialisme dialectique : les problèmes sont à la fois individuels et systémiques.Et surtout, on voit pourquoi les contradictions que ça crée ne sont pas des obstacles, mais de véritables moteurs de transformation pour tes bénéficiaires, et pour toi en tant qu'accompagnant·e.Bonne écoute,Laura

Badger Punch Games — the duo of Ricki Sickenger and Henning Ludvigsen — have been creating games together since their Amiga demo scene days in the early '90s. Their breakout title Roguecraft first made waves on the Amiga in 2024, later winning the Debug award and quickly earning a devoted following. Now the game has been reimagined and released as Roguecraft DX on Evercade, bringing their retro-inspired roguelike adventure to a whole new audience. In this episode, Ricki and Henning join me to talk about their journey from humble beginnings in the demo scene, to building games as a side hustle, to becoming part of the Evercade family. We discuss the origins of Roguecraft, the challenges of bringing it to life on classic hardware, and the process of enhancing it for Evercade — from new features to the community support that helped make it happen. Along the way, they share insights into procedural generation, design choices like the lack of save states, and what they'd love to add in the future. As always, we wrap up with a trip to the Retro Rocket Museum, where Ricki and Henning pick their all-time favourite retro device and two games to preserve for future generations, and finish with a music pick to play us out. It's a must-listen for fans of Amiga, Evercade, and indie retro development.  

Elizabeth Figura is a Wine developer at Code Weavers. We discuss how Wine and Proton make it possible to run Windows applications on other operating systems. Related links WineHQ Proton Crossover Direct3D MoltenVK XAudio2 Mesa 3D Graphics Library Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Elizabeth Figuera. She's a wine developer at Code Weavers. And today we're gonna talk about what that is and, uh, all the work that goes into it. [00:00:09] Elizabeth: Thank you Jeremy. I'm glad to be here. What's Wine [00:00:13] Jeremy: I think the first thing we should talk about is maybe saying what Wine is because I think a lot of people aren't familiar with the project. [00:00:20] Elizabeth: So wine is a translation layer. in fact, I would say wine is a Windows emulator. That is what the name originally stood for. it re implements the entire windows. Or you say win 32 API. so that programs that make calls into the API, will then transfer that code to wine and and we allow that Windows programs to run on, things that are not windows. So Linux, Mac, os, other operating systems such as Solaris and BSD. it works not by emulating the CPU, but by re-implementing every API, basically from scratch and translating them to their equivalent or writing new code in case there is no, you know, equivalent. System Calls [00:01:06] Jeremy: I believe what you're doing is you're emulating system calls. Could you explain what those are and, and how that relates to the project? [00:01:15] Elizabeth: Yeah. so system call in general can be used, referred to a call into the operating system, to execute some functionality that's built into the operating system. often it's used in the context of talking to the kernel windows applications actually tend to talk at a much higher level, because there's so much, so much high level functionality built into Windows. When you think about, as opposed to other operating systems that we basically, we end up end implementing much higher level behavior than you would on Linux. [00:01:49] Jeremy: And can you give some examples of what some of those system calls would be and, I suppose how they may be higher level than some of the Linux ones. [00:01:57] Elizabeth: Sure. So of course you have like low level calls like interacting with a file system, you know, created file and read and write and such. you also have, uh, high level APIs who interact with a sound driver. [00:02:12] Elizabeth: There's, uh, one I was working on earlier today, called XAudio where you, actually, you know, build this bank of of sounds. It's meant to be, played in a game and then you can position them in various 3D space. And the, and the operating system in a sense will, take care of all of the math that goes into making that work. [00:02:36] Elizabeth: That's all running on your computer and. And then it'll send that audio data to the sound card once it's transformed it. So it sounds like it's coming from a certain space. a lot of other things like, you know, parsing XML is another big one. That there's a lot of things. The, there, the, the, the space is honestly huge [00:02:59] Jeremy: And yeah, I can sort of see how those might be things you might not expect to be done by the operating system. Like you gave the example of 3D audio and XML parsing and I think XML parsing in, in particular, you would've thought that that would be something that would be handled by the, the standard library of whatever language the person was writing their application as. [00:03:22] Jeremy: So that's interesting that it's built into the os. [00:03:25] Elizabeth: Yeah. Well, and languages like, see it's not, it isn't even part of the standard library. It's higher level than that. It's, you have specific libraries that are widespread but not. Codified in a standard, but in Windows you, in Windows, they are part of the operating system. And in fact, there's several different, XML parsers in the operating system. Microsoft likes to deprecate old APIs and make new ones that do the same thing very often. [00:03:53] Jeremy: And something I've heard about Windows is that they're typically very reluctant to break backwards compatibility. So you say they're deprecated, but do they typically keep all of them still in there? [00:04:04] Elizabeth: It all still It all still works. [00:04:07] Jeremy: And that's all things that wine has to implement as well to make sure that the software works as well. [00:04:14] Jeremy: Yeah. [00:04:14] Elizabeth: Yeah. And, and we also, you know, need to make it work. we also need to implement those things to make old, programs work because there is, uh, a lot of demand, at least from, at least from people using wine for making, for getting some really old programs, working from the. Early nineties even. What people run with Wine (Productivity, build systems, servers) [00:04:36] Jeremy: And that's probably a good, thing to talk about in terms of what, what are the types of software that, that people are trying to run with wine, and what operating system are they typically using? [00:04:46] Elizabeth: Oh, in terms of software, literally all kinds, any software you can imagine that runs on Windows, people will try to run it on wine. So we're talking games, office software productivity, software accounting. people will run, build systems on wine, build their, just run, uh, build their programs using, on visual studio, running on wine. people will run wine on servers, for example, like software as a service kind of things where you don't even know that it's running on wine. really super domain specific stuff. Like I've run astronomy, software, and wine. Design, computer assisted design, even hardware drivers can sometimes work unwind. There's a bit of a gray area. How games are different [00:05:29] Jeremy: Yeah, it's um, I think from. Maybe the general public, or at least from what I've seen, I think a lot of people's exposure to it is for playing games. is there something different about games versus all those other types of, productivity software and office software that, that makes supporting those different. [00:05:53] Elizabeth: Um, there's some things about it that are different. Games of course have gotten a lot of publicity lately because there's been a huge push, largely from valve, but also some other companies to get. A lot of huge, wide range of games working well under wine. And that's really panned out in the, in a way, I think, I think we've largely succeeded. [00:06:13] Elizabeth: We've made huge strides in the past several years. 5, 5, 10 years, I think. so when you talk about what makes games different, I think, one thing games tend to do is they have a very limited set of things they're working with and they often want to make things run fast, and so they're working very close to the me They're not, they're not gonna use an XML parser, for example. [00:06:44] Elizabeth: They're just gonna talk directly as, directly to the graphics driver as they can. Right. And, and probably going to do all their own sound design. You know, I did talk about that XAudio library, but a lot of games will just talk directly as, directly to the sound driver as Windows Let some, so this is a often a blessing, honestly, because it means there's less we have to implement to make them work. when you look at a lot of productivity applications, and especially, the other thing that makes some productivity applications harder is, Microsoft makes 'em, and They like to, make a library, for use in this one program like Microsoft Office and then say, well, you know, other programs might use this as well. Let's. Put it in the operating system and expose it and write an API for it and everything. And maybe some other programs use it. mostly it's just office, but it means that office relies on a lot of things from the operating system that we all have to reimplement. [00:07:44] Jeremy: Yeah, that's somewhat counterintuitive because when you think of games, you think of these really high performance things that that seem really complicated. But it sounds like from what you're saying, because they use the lower level primitives, they're actually easier in some ways to support. [00:08:01] Elizabeth: Yeah, certainly in some ways, they, yeah, they'll do things like re-implement the heap allocator because the built-in heap allocator isn't fast enough for them. That's another good example. What makes some applications hard to support (Some are hard, can't debug other people's apps) [00:08:16] Jeremy: You mentioned Microsoft's more modern, uh, office suites. I, I've noticed there's certain applications that, that aren't supported. Like, for example, I think the modern Adobe Creative Suite. What's the difference with software like that and does that also apply to the modern office suite, or is, or is that actually supported? [00:08:39] Elizabeth: Well, in one case you have, things like Microsoft using their own APIs that I mentioned with Adobe. That applies less, I suppose, but I think to some degree, I think to some degree the answer is that some applications are just hard and there's, and, and there's no way around it. And, and we can only spend so much time on a hard application. I. Debugging things. Debugging things can get very hard with wine. Let's, let me like explain that for a minute because, Because normally when you think about debugging an application, you say, oh, I'm gonna open up my debugger, pop it in, uh, break at this point, see what like all the variables are, or they're not what I expect. Or maybe wait for it to crash and then get a back trace and see where it crashed. And why you can't do that with wine, because you don't have the application, you don't have the symbols, you don't have your debugging symbols. You don't know anything about the code you're running unless you take the time to disassemble and decompile and read through it. And that's difficult every time. It's not only difficult, every time I've, I've looked at a program and been like, I really need to just. I'm gonna just try and figure out what the program is doing. [00:10:00] Elizabeth: It takes so much time and it is never worth it. And sometimes you have to, sometimes you have no other choice, but usually you end up, you ask to rely on seeing what calls it makes into the operating system and trying to guess which one of those is going wrong. Now, sometimes you'll get lucky and it'll crash in wine code, or sometimes it'll make a call into, a function that we don't implement yet, and we know, oh, we need to implement that function. But sometimes it does something, more obscure and we have to figure out, well, like all of these millions of calls it made, which one of them is, which one of them are we implementing incorrectly? So it's returning the wrong result or not doing something that it should. And, then you add onto that the. You know, all these sort of harder to debug things like memory errors that we could make. And it's, it can be very difficult and so sometimes some applications just suffer from those hard bugs. and sometimes it's also just a matter of not enough demand for something for us to spend a lot of time on it. [00:11:11] Elizabeth: Right. [00:11:14] Jeremy: Yeah, I can see how that would be really challenging because you're, like you were saying, you don't have the symbols, so you don't have the source code, so you don't know what any of this software you're supporting, how it was actually written. And you were saying that I. A lot of times, you know, there may be some behavior that's wrong or a crash, but it's not because wine crashed or there was an error in wine. [00:11:42] Jeremy: so you just know the system calls it made, but you don't know which of the system calls didn't behave the way that the application expected. [00:11:50] Elizabeth: Exactly. Test suite (Half the code is tests) [00:11:52] Jeremy: I can see how that would be really challenging. and wine runs so many different applications. I'm, I'm kind of curious how do you even track what's working and what's not as you, you change wine because if you support thousands or tens thousands of applications, you know, how do you know when you've got a, a regression or not? [00:12:15] Elizabeth: So, it's a great question. Um, probably over half of wine by like source code volume. I actually actually check what it is, but I think it's, i, I, I think it's probably over half is what we call is tests. And these tests serve two purposes. The one purpose is a regression test. And the other purpose is they're conformance tests that test, that test how, uh, an API behaves on windows and validates that we are behaving the same way. So we write all these tests, we run them on windows and you know, write the tests to check what the windows returns, and then we run 'em on wine and make sure that that matches. and we have just such a huge body of tests to make sure that, you know, we're not breaking anything. And that every, every, all the code that we, that we get into wine that looks like, wow, it's doing that really well. Nope, that's what Windows does. The test says so. So pretty much any code that we, any new code that we get, it has to have tests to validate, to, to demonstrate that it's doing the right thing. [00:13:31] Jeremy: And so rather than testing against a specific application, seeing if it works, you're making a call to a Windows system call, seeing how it responds, and then making the same call within wine and just making sure they match. [00:13:48] Elizabeth: Yes, exactly. And that is obviously, or that is a lot more, automatable, right? Because otherwise you have to manually, you know, there's all, these are all graphical applications. [00:14:02] Elizabeth: You'd have to manually do the things and make sure they work. Um, but if you write automateable tests, you can just run them all and the machine will complain at you if it fails it continuous integration. How compatibility problems appear to users [00:14:13] Jeremy: And because there's all these potential compatibility issues where maybe a certain call doesn't behave the way an application expects. What, what are the types of what that shows when someone's using software? I mean, I, I think you mentioned crashes, but I imagine there could be all sorts of other types of behavior. [00:14:37] Elizabeth: Yes, very much so. basically anything, anything you can imagine again is, is what will happen. You can have, crashes are the easy ones because you know when and where it crashed and you can work backwards from there. but you can also get, it can, it could hang, it could not render, right? Like maybe render a black screen. for, you know, for games you could very frequently have, graphical glitches where maybe some objects won't render right? Or the entire screen will be read. Who knows? in a very bad case, you could even bring down your system and we usually say that's not wine's fault. That's the graphics library's fault. 'cause they're not supposed to do that, uh, no matter what we do. But, you know, sometimes we have to work around that anyway. but yeah, there's, there's been some very strange and idiosyncratic bugs out there too. [00:15:33] Jeremy: Yeah. And like you mentioned that uh, there's so many different things that could have gone wrong that imagine's very difficult to find. Yeah. And when software runs through wine, I think, Performance is comparable to native [00:15:49] Jeremy: A lot of our listeners will probably be familiar with running things in a virtual machine, and they know that there's a big performance impact from doing that. [00:15:57] Jeremy: How does the performance of applications compare to running natively on the original Windows OS versus virtual machines? [00:16:08] Elizabeth: So. In theory. and I, I haven't actually done this recently, so I can't speak too much to that, but in theory, the idea is it's a lot faster. so there, there, is a bit of a joke acronym to wine. wine is not an emulator, even though I started out by saying wine is an emulator, and it was originally called a Windows emulator. but what this basically means is wine is not a CPU emulator. It doesn't, when you think about emulators in a general sense, they're often, they're often emulators for specific CPUs, often older ones like, you know, the Commodore emulator or an Amiga emulator. but in this case, you have software that's written for an x86 CPU. And it's running on an x86 CPU by giving it the same instructions that it's giving on windows. It's just that when it says, now call this Windows function, it calls us instead. So that all should perform exactly the same. The only performance difference at that point is that all should perform exactly the same as opposed to a, virtual machine where you have to interpret the instructions and maybe translate them to a different instruction set. The only performance difference is going to be, in the functions that we are implementing themselves and we try to, we try to implement them to perform. As well, or almost as well as windows. There's always going to be a bit of a theoretical gap because we have to translate from say, one API to another, but we try to make that as little as possible. And in some cases, the operating system we're running on is, is just better than Windows and the libraries we're using are better than Windows. [00:18:01] Elizabeth: And so our games will run faster, for example. sometimes we can, sometimes we can, do a better job than Windows at implementing something that's, that's under our purview. there there are some games that do actually run a little bit faster in wine than they do on Windows. [00:18:22] Jeremy: Yeah, that, that reminds me of how there's these uh, gaming handhelds out now, and some of the same ones, they have a, they either let you install Linux or install windows, or they just come with a pre-installed, and I believe what I've read is that oftentimes running the same game on both operating systems, running the same game on Linux, the battery life is better and sometimes even the performance is better with these handhelds. [00:18:53] Jeremy: So it's, it's really interesting that that can even be the case. [00:18:57] Elizabeth: Yeah, it's really a testament to the huge amount of work that's gone into that, both on the wine side and on the, side of the graphics team and the colonel team. And, and of course, you know, the years of, the years of, work that's gone into Linux, even before these gaming handhelds were, were even under consideration. Proton and Valve Software's role [00:19:21] Jeremy: And something. So for people who are familiar with the handhelds, like the steam deck, they may have heard of proton. Uh, I wonder if you can explain what proton is and how it relates to wine. [00:19:37] Elizabeth: Yeah. So, proton is basically, how do I describe this? So, proton is a sort of a fork, uh, although we try to avoid the term fork. It's a, we say it's a downstream distribution because we contribute back up to wine. so it is a, it is, it is a alternate distribution fork of wine. And it's also some code that basically glues wine into, an embedding application originally intended for steam, and developed for valve. it has also been used in, others, but it has also been used in other software. it, so where proton differs from wine besides the glue part is it has some, it has some extra hacks in it for bugs that are hard to fix and easy to hack around as some quick hacks for, making games work now that are like in the process of going upstream to wine and getting their code quality improved and going through review. [00:20:54] Elizabeth: But we want the game to work now, when we distribute it. So that'll, that'll go into proton immediately. And then once we have, once the patch makes it upstream, we replace it with the version of the patch from upstream. there's other things to make it interact nicely with steam and so on. And yeah, I think, yeah, I think that's, I got it. [00:21:19] Jeremy: Yeah. And I think for people who aren't familiar, steam is like this, um, I, I don't even know what you call it, like a gaming store and a [00:21:29] Elizabeth: store game distribution service. it's got a huge variety of games on it, and you just publish. And, and it's a great way for publishers to interact with their, you know, with a wider gaming community, uh, after it, just after paying a cut to valve of their profits, they can reach a lot of people that way. And because all these games are on team and, valve wants them to work well on, on their handheld, they contracted us to basically take their entire catalog, which is huge, enormous. And trying and just step by step. Fix every game and make them all work. [00:22:10] Jeremy: So, um, and I guess for people who aren't familiar Valve, uh, softwares the company that runs steam, and so it sounds like they've asked, uh, your company to, to help improve the compatibility of their catalog. [00:22:24] Elizabeth: Yes. valve contracted us and, and again, when you're talking about wine using lower level libraries, they've also contracted a lot of other people outside of wine. Basically, the entire stack has had a tremendous, tremendous investment by valve software to make gaming on Linux work. Well. The entire stack receives changes to improve Wine compatibility [00:22:48] Jeremy: And when you refer to the entire stack, like what are some, some of those pieces, at least at a high level. [00:22:54] Elizabeth: I, I would, let's see, let me think. There is the wine project, the. Mesa Graphics Libraries. that's a, that's another, you know, uh, open source, software project that existed, has existed for a long time. But Valve has put a lot of, uh, funding and effort into it, the Linux kernel in various different ways. [00:23:17] Elizabeth: the, the desktop, uh, environment and Window Manager for, um, are also things they've invested in. [00:23:26] Jeremy: yeah. Everything that the game needs, on any level and, and that the, and that the operating system of the handheld device needs. Wine's history [00:23:37] Jeremy: And wine's been going on for quite a while. I think it's over a decade, right? [00:23:44] Elizabeth: I believe. Oh, more than, oh, far more than a decade. I believe it started in 1990, I wanna say about 1995, mid nineties. I'm, I probably have that date wrong. I believe Wine started about the mid nineties. [00:24:00] Jeremy: Mm. [00:24:00] Elizabeth: it's going on for three decades at this rate. [00:24:03] Jeremy: Wow. Okay. [00:24:06] Jeremy: And so all this time, how has the, the project sort of sustained itself? Like who's been involved and how has it been able to keep going this long? [00:24:18] Elizabeth: Uh, I think as is the case with a lot of free software, it just, it just keeps trudging along. There's been. There's been times where there's a lot of interest in wine. There's been times where there's less, and we are fortunate to be in a time where there's a lot of interest in it. we've had the same maintainer for almost this entire, almost this entire existence. Uh, Alexander Julliard, there was one person starting who started, maintained it before him and, uh, left it maintainer ship to him after a year or two. Uh, Bob Amstat. And there has been a few, there's been a few developers who have been around for a very long time. a lot of developers who have been around for a decent amount of time, but not for the entire duration. And then a very, very large number of people who come and submit a one-off fix for their individual application that they want to make work. [00:25:19] Jeremy: How does crossover relate to the wine project? Like, it sounds like you had mentioned Valve software hired you for subcontract work, but crossover itself has been around for quite a while. So how, how has that been connected to the wine project? [00:25:37] Elizabeth: So I work for, so the, so the company I work for is Code Weavers and, crossover is our flagship software. so Code Weavers is a couple different things. We have a sort of a porting service where companies will come to us and say, can we port my application usually to Mac? And then we also have a retail service where Where we basically have our own, similar to Proton, but you know, older, but the same idea where we will add some hacks into it for very difficult to solve bugs and we have a, a nice graphical interface. And then, the other thing that we're selling with crossover is support. So if you, you know, try to run a certain application and you buy crossover, you can submit a ticket saying this doesn't work and we now have a financial incentive to fix it. You know, we'll try to, we'll try to fix your, we'll spend company resources to fix your bug, right? So that's been so, so code we v has been around since 1996 and crossover, I don't know the date, but it's crossover has been around for probably about two decades, if I'm not mistaken. [00:27:01] Jeremy: And when you mention helping companies port their software to, for example, MacOS. [00:27:07] Jeremy: Is the approach that you would port it natively to MacOS APIs or is it that you would help them get it running using wine on MacOS? [00:27:21] Elizabeth: Right. That's, so that's basically what makes us so unique among porting companies is that instead of rewriting their software, we just, we just basically stick it inside of crossover and, uh, and, and make it run. [00:27:36] Elizabeth: And the idea has always been, you know, the more we implement, the more we get correct, the, the more applications will, you know, work. And sometimes it works out that way. Sometimes not really so much. And there's always work we have to do to get any given application to work, but. Yeah, so it's, it's very unusual because we don't ask companies for any of their code. We don't need it. We just fix the windows API [00:28:07] Jeremy: And, and so in that case, the ports would be let's say someone sells a MacOS version of their software. They would bundle crossover, uh, with their software. [00:28:18] Elizabeth: Right? And usually when you do this, it doesn't look like there's crossover there. Like it just looks like this software is native, but there is soft, there is crossover under the hood. Loading executables and linked libraries [00:28:32] Jeremy: And so earlier we were talking about how you're basically intercepting the system calls that these binaries are making, whether that's the executable or the, the DLLs from Windows. Um, but I think probably a lot of our listeners are not really sure how that's done. Like they, they may have built software, but they don't know, how do I basically hijack, the system calls that this application is making. [00:29:01] Jeremy: So maybe you could talk a little bit about how that works. [00:29:04] Elizabeth: So there, so there's a couple steps to go into it. when you think about a program that's say, that's a big, a big file that's got all the machine code in it, and then it's got stuff at the beginning saying, here's how the program works and here's where in the file the processor should start running. that's, that's your EXE file. And then in your DLL files are libraries that contain shared code and you have like a similar sort of file. It says, here's the entry point. That runs this function, this, you know, this pars XML function or whatever have you. [00:29:42] Elizabeth: And here's this entry point that has the generate XML function and so on and so forth. And, and, then the operating system will basically take the EXE file and see all the bits in it. Say I want to call the pars XML function. It'll load that DLL and hook it up. So it, so the processor ends up just seeing jump directly to this pars XML function and then run that and then return and so on. [00:30:14] Elizabeth: And so what wine does, is it part of wine? That's part of wine is a library, is that, you know, the implementing that parse XML and read XML function, but part of it is the loader, which is the part of the operating system that hooks everything together. And when we load, we. Redirect to our libraries. We don't have Windows libraries. [00:30:38] Elizabeth: We like, we redirect to ours and then we run our code. And then when you jump back to the program and yeah. [00:30:48] Jeremy: So it's the, the loader that's a part of wine. That's actually, I'm not sure if running the executable is the right term. [00:30:58] Elizabeth: no, I think that's, I think that's a good term. It's, it's, it's, it starts in a loader and then we say, okay, now run the, run the machine code and it's executable and then it runs and it jumps between our libraries and back and so on. [00:31:14] Jeremy: And like you were saying before, often times when it's trying to make a system call, it ends up being handled by a function that you've written in wine. And then that in turn will call the, the Linux system calls or the MacOS system calls to try and accomplish the, the same result. [00:31:36] Elizabeth: Right, exactly. [00:31:40] Jeremy: And something that I think maybe not everyone is familiar with is there's this concept of user space versus kernel space. you explain what the difference is? [00:31:51] Elizabeth: So the way I would explain, the way I would describe a kernel is it's the part of the operating system that can do anything, right? So any program, any code that runs on your computer is talking to the processor, and the processor has to be able to do anything the computer can do. [00:32:10] Elizabeth: It has to be able to talk to the hardware, it has to set up the memory space. That, so actually a very complicated task has to be able to switch to another task. and, and, and, and basically talk to another program and. You have to have something there that can do everything, but you don't want any program to be able to do everything. Um, not since the, not since the nineties. It's about when we realized that we can't do that. so the kernel is a part that can do everything. And when you need to do something that requires those, those permissions that you can't give everyone, you have to talk to the colonel and ask it, Hey, can you do this for me please? And in a very restricted way where it's only the safe things you can do. And a degree, it's also like a library, right? It's the kernel. The kernels have always existed, and since they've always just been the core standard library of the computer that does the, that does the things like read and write files, which are very, very complicated tasks under the hood, but look very simple because all you say is write this file. And talk to the hardware and abstract away all the difference between different drivers. So the kernel is doing all of these things. So because the kernel is a part that can do everything and because when you think about the kernel, it is basically one program that is always running on your computer, but it's only one program. So when a user calls the kernel, you are switching from one program to another and you're doing a lot of complicated things as part of this. You're switching to the higher privilege level where you can do anything and you're switching the state from one program to another. And so it's a it. So this is what we mean when we talk about user space, where you're running like a normal program and kernel space where you've suddenly switched into the kernel. [00:34:19] Elizabeth: Now you're executing with increased privileges in a different. idea of the process space and increased responsibility and so on. [00:34:30] Jeremy: And, and so do most applications. When you were talking about the system calls for handling 3D audio or parsing XML. Are those considered, are those system calls considered part of user space and then those things call the kernel space on your behalf, or how, how would you describe that? [00:34:50] Elizabeth: So most, so when you look at Windows, most of most of the Windows library, the vast, vast majority of it is all user space. most of these libraries that we implement never leave user space. They never need to call into the kernel. there's the, there only the core low level stuff. Things like, we need to read a file, that's a kernel call. when you need to sleep and wait for some seconds, that's a kernel. Need to talk to a different process. Things that interact with different processes in general. not just allocate memory, but allocate a page of memory, like a, from the memory manager and then that gets sub allocated by the heap allocator. so things like that. [00:35:31] Jeremy: Yeah, so if I was writing an application and I needed to open a file, for example, does, does that mean that I would have to communicate with the kernel to, to read that file? [00:35:43] Elizabeth: Right, exactly. [00:35:46] Jeremy: And so most applications, it sounds like it's gonna be a mixture. You're gonna have a lot of things that call user space calls. And then a few, you mentioned more low level ones that are gonna require you to communicate with the kernel. [00:36:00] Elizabeth: Yeah, basically. And it's worth noting that in, in all operating systems, you're, you're almost always gonna be calling a user space library. That might just be a thin wrapper over the kernel call. It might, it's gonna do like just a little bit of work in end call the kernel. [00:36:19] Jeremy: [00:36:19] Elizabeth: In fact, in Windows, that's the only way to do it. Uh, in many other operating systems, you can actually say, you can actually tell the processor to make the kernel call. There is a special instruction that does this and just, and it'll go directly to the kernel, and there's a defined interface for this. But in Windows, that interface is not defined. It's not stable. Or backwards compatible like the rest of Windows is. So even if you wanted to use it, you couldn't. and you basically have to call into the high level libraries or low level libraries, as it were, that, that tell you that create a file. And those don't do a lot. [00:37:00] Elizabeth: They just kind of tweak their parameters a little and then pass them right down to the kernel. [00:37:07] Jeremy: And so wine, it sounds like it needs to implement both the user space calls of windows, but then also the, the kernel, calls as well. But, but wine itself does that, is that only in Linux user space or MacOS user space? [00:37:27] Elizabeth: Yes. This is a very tricky thing. but all of wine, basically all of what is wine runs in, in user space and we use. Kernel calls that are already there to talk to the colonel, to talk to the host Colonel. You have to, and you, you get, you get, you get the sort of second nature of thinking about the Windows, user space and kernel. [00:37:50] Elizabeth: And then there's a host user space and Kernel and wine is running all in user, in the user, in the host user space, but it's emulating the Windows kernel. In fact, one of the weirdest, trickiest parts is I mentioned that you can run some drivers in wine. And those drivers actually, they actually are, they think they're running in the Windows kernel. which in a sense works the same way. It has libraries that it can load, and those drivers are basically libraries and they're making, kernel calls and they're, they're making calls into the kernel library that does some very, very low level tasks that. You're normally only supposed to be able to do in a kernel. And, you know, because the kernel requires some privileges, we kind of pretend we have them. And in many cases, you're even the drivers are using abstractions. We can just implement those abstractions kind of over the slightly higher level abstractions that exist in user space. [00:39:00] Jeremy: Yeah, I hadn't even considered the being able to use hardware devices, but I, I suppose if in, in the end, if you're reproducing the kernel, then whether you're running software or you're talking to a hardware device, as long as you implement the calls correctly, then I, I suppose it works. [00:39:18] Elizabeth: Cause you're, you're talking about device, like maybe it's some kind of USB device that has drivers for Windows, but it doesn't for, for Linux. [00:39:28] Elizabeth: no, that's exactly, that's a, that's kind of the, the example I've used. Uh, I think there is, I think I. My, one of my best success stories was, uh, drivers for a graphing calculator. [00:39:41] Jeremy: Oh, wow. [00:39:42] Elizabeth: That connected via USB and I basically just plugged the windows drivers into wine and, and ran it. And I had to implement a lot of things, but it worked. But for example, something like a graphics driver is not something you could implement in wine because you need the graphics driver on the host. We can't talk to the graphics driver while the host is already doing so. [00:40:05] Jeremy: I see. Yeah. And in that case it probably doesn't make sense to do so [00:40:11] Elizabeth: Right? [00:40:12] Elizabeth: Right. It doesn't because, the transition from user into kernel is complicated. You need the graphics driver to be in the kernel and the real kernel. Having it in wine would be a bad idea. Yeah. [00:40:25] Jeremy: I, I think there's, there's enough APIs you have to try and reproduce that. I, I think, uh, doing, doing something where, [00:40:32] Elizabeth: very difficult [00:40:33] Jeremy: right. Poor system call documentation and private APIs [00:40:35] Jeremy: There's so many different, calls both in user space and in kernel space. I imagine the, the user space ones Microsoft must document to some extent, but, oh. Is that, is that a [00:40:51] Elizabeth: well, sometimes, [00:40:54] Jeremy: Sometimes. Okay. [00:40:55] Elizabeth: I think it's actually better now than it used to be. But some, here's where things get fun, because sometimes there will be, you know, regular documented calls. Sometimes those calls are documented, but the documentation isn't very good. Sometimes programs will just sort of look inside Microsoft's DLLs and use calls that they aren't supposed to be using. Sometimes they use calls that they are supposed to be using, but the documentation has disappeared. just because it's that old of an API and Microsoft hasn't kept it around. sometimes some, sometimes Microsoft, Microsoft own software uses, APIs that were never documented because they never wanted anyone else using them, but they still ship them with the operating system. there was actually a kind of a lawsuit about this because it is an antitrust lawsuit, because by shipping things that only they could use, they were kind of creating a trust. and that got some things documented. At least in theory, they kind of haven't stopped doing it, though. [00:42:08] Jeremy: Oh, so even today they're, they're, I guess they would call those private, private APIs, I suppose. [00:42:14] Elizabeth: I suppose. Uh, yeah, you could say private APIs. but if we want to get, you know, newer versions of Microsoft Office running, we still have to figure out what they're doing and implement them. [00:42:25] Jeremy: And given that they're either, like you were saying, the documentation is kind of all over the place. If you don't know how it's supposed to behave, how do you even approach implementing them? [00:42:38] Elizabeth: and that's what the conformance tests are for. And I, yeah, I mentioned earlier we have this huge body of conformance tests that double is regression tests. if we see an API, we don't know what to do with or an API, we do know, we, we think we know what to do with because the documentation can just be wrong and often has been. Then we write tests to figure out what it's supposed to behave. We kind of guess until we, and, and we write tests and we pass some things in and see what comes out and see what. The see what the operating system does until we figure out, oh, so this is what it's supposed to do and these are the exact parameters in, and, and then we, and, and then we implement it according to those tests. [00:43:24] Jeremy: Is there any distinction in approach for when you're trying to implement something that's at the user level versus the kernel level? [00:43:33] Elizabeth: No, not really. And like I, and like I mentioned earlier, like, well, I mean, a kernel call is just like a library call. It's just done in a slightly different way, but it's still got, you know, parameters in, it's still got a set of parameters. They're just encoded differently. And, and again, like the, the way kernel calls are done is on a level just above the kernel where you have a library, that just passes things through. Almost verbatim to the kernel and we implement that library instead. [00:44:10] Jeremy: And, and you've been working on i, I think, wine for over, over six years now. [00:44:18] Elizabeth: That sounds about right. Debugging and having broad knowledge of Wine [00:44:20] Jeremy: What does, uh, your, your day to day look like? What parts of the project do you, do you work on? [00:44:27] Elizabeth: It really varies from day to day. and I, I, a lot of people, a lot of, some people will work on the same parts of wine for years. Uh, some people will switch around and work on all sorts of different things. [00:44:42] Elizabeth: And I'm, I definitely belong to that second group. Like if you name an area of wine, I have almost certainly contributed a patch or two to it. there's some areas I work on more than others, like, 3D graphics, multimedia, a, I had, I worked on a compiler that exists, uh, socket. So networking communication is another thing I work a lot on. day to day, I kind of just get, I, I I kind of just get a bug for some program or another. and I take it and I debug it and figure out why the program's broken and then I fix it. And there's so much variety in that. because a bug can take so many different forms like I described, and, and, and the, and then the fix can be simple or complicated or, and it can be in really anywhere to a degree. [00:45:40] Elizabeth: being able to work on any part of wine is sometimes almost a necessity because if a program is just broken, you don't know why. It could be anything. It could be any sort of API. And sometimes you can hand the API to somebody who's got a lot of experience in that, but sometimes you just do whatever. You just fix whatever's broken and you get an experience that way. [00:46:06] Jeremy: Yeah, I mean, I was gonna ask about the specialized skills to, to work on wine, but it sounds like maybe in your case it's all of them. [00:46:15] Elizabeth: It's, there's a bit of that. it's a wine. We, the skills to work on wine are very, it's a very unique set of skills because, and it largely comes down to debugging because you can't use the tools you normally use debug. [00:46:30] Elizabeth: You have to, you have to be creative and think about it different ways. Sometimes you have to be very creative. and programs will try their hardest to avoid being debugged because they don't want anyone breaking their copy protection, for example, or or hacking, or, you know, hacking in sheets. They want to be, they want, they don't want anyone hacking them like that. [00:46:54] Elizabeth: And we have to do it anyway for good and legitimate purposes. We would argue to make them work better on more operating systems. And so we have to fight that every step of the way. [00:47:07] Jeremy: Yeah, it seems like it's a combination of. F being able, like you, you were saying, being able to, to debug. and you're debugging not necessarily your own code, but you're debugging this like behavior of, [00:47:25] Jeremy: And then based on that behavior, you have to figure out, okay, where in all these different systems within wine could this part be not working? [00:47:35] Jeremy: And I, I suppose you probably build up some kind of, mental map in your head of when you get a, a type of bug or a type of crash, you oh, maybe it's this, maybe it's here, or something [00:47:47] Elizabeth: Yeah. That, yeah, there is a lot of that. there's, you notice some patterns, you know, after experience helps, but because any bug could be new, sometimes experience doesn't help and you just, you just kind of have to start from scratch. Finding a bug related to XAudio [00:48:08] Jeremy: At sort of a high level, can you give an example of where you got a specific bug report and then where you had to look to eventually find which parts of the the system were the issue? [00:48:21] Elizabeth: one, one I think good example, that I've done recently. so I mentioned this, this XAudio library that does 3D audio. And if you say you come across a bug, I'm gonna be a little bit generics here and say you come across a bug where some audio isn't playing right, maybe there's, silence where there should be the audio. So you kind of, you look in and see, well, where's that getting lost? So you can basically look in the input calls and say, here's the buffer it's submitting that's got all the audio data in it. And you look at the output, you look at where you think the output should be, like, that library will internally call a different library, which programs can interact with directly. [00:49:03] Elizabeth: And this our high level library interacts with that is the, give this sound to the audio driver, right? So you've got XAudio on top of, um. mdev, API, which is the other library that gives audio to the driver. And you see, well, the ba the buffer is that XAudio is passing into MM Dev, dev API. They're empty, there's nothing in them. So you have to kind of work through the XAudio library to see where is, where's that sound getting lost? Or maybe, or maybe that's not getting lost. Maybe it's coming through all garbled. And I've had to look at the buffer and see why is it garbled. I'll open up it up in Audacity and look at the weight shape of the wave and say, huh, that shape of the wave looks like it's, it looks like we're putting silence every 10 nanoseconds or something, or, or reversing something or interpreting it wrong. things like that. Um, there's a lot of, you'll do a lot of, putting in print fs basically all throughout wine to see where does the state change. Where was, where is it? Where is it? Right? And then where do things start going wrong? [00:50:14] Jeremy: Yeah. And in the audio example, because they're making a call to your XAudio implementation, you can see that Okay, the, the buffer, the audio that's coming in. That part is good. It, it's just that later on when it sends it to what's gonna actually have it be played by the, the hardware, that's when missing. So, [00:50:37] Elizabeth: We did something wrong in a library that destroyed the buffer. And I think on a very, high level a lot of debugging, wine is about finding where things are good and finding where things are bad, and then narrowing that down until we find the one spot where things go wrong. There's a lot of processes that go like that. [00:50:57] Jeremy: like you were saying, the more you see these problems, hopefully the, the easier it gets to, to narrow down where, [00:51:04] Elizabeth: Often. Yeah. Especially if you keep debugging things in the same area. How much code is OS specific?c [00:51:09] Jeremy: And wine supports more than one operating system. I, I saw there was Linux, MacOS I think free BSD. How much of the code is operating system specific versus how much can just be shared across all of them? [00:51:27] Elizabeth: Not that much is operating system specific actually. so when you think about the volume of wine, the, the, the, vast majority of it is the high level code that doesn't need to interact with the operating system on a low level. Right? Because Windows keeps putting, because Microsoft keeps putting lots and lots of different libraries in their operating system. And a lot of these are high level libraries. and even when we do interact with the operating system, we're, we're using cross-platform libraries or we're using, we're using ics. The, uh, so all these operating systems that we are implementing are con, basically conformed to the posix standard. which is basically like Unix, they're all Unix based. Psic is a Unix based standard. Microsoft is, you know, the big exception that never did implement that. And, and so we have to translate its APIs to Unix, APIs. now that said, there is a lot of very operating system, specific code. Apple makes things difficult by try, by diverging almost wherever they can. And so we have a lot of Apple specific code in there. [00:52:46] Jeremy: another example I can think of is, I believe MacOS doesn't support, Vulkan [00:52:53] Elizabeth: yes. Yeah.Yeah, That's a, yeah, that's a great example of Mac not wanting to use, uh, generic libraries that work on every other operating system. and in some cases we, we look at it and are like, alright, we'll implement a wrapper for that too, on top of Yuri, on top of your, uh, operating system. We've done it for Windows, we can do it for Vulkan. and that's, and then you get the Molten VK project. Uh, and to be clear, we didn't invent molten vk. It was around before us. We have contributed a lot to it. Direct3d, Vulkan, and MoltenVK [00:53:28] Jeremy: Yeah, I think maybe just at a high level might be good to explain the relationship between Direct 3D or Direct X and Vulcan and um, yeah. Yeah. Maybe if you could go into that. [00:53:42] Elizabeth: so Direct 3D is Microsoft's 3D API. the 3D APIs, you know, are, are basically a way to, they're way to firstly abstract out the differences between different graphics, graphics cards, which, you know, look very different on a hardware level. [00:54:03] Elizabeth: Especially. They, they used to look very different and they still do look very different. and secondly, a way to deal with them at a high level because actually talking to the graphics card on a low level is very, very complicated. Even talking to it on a high level is complicated, but it gets, it can get a lot worse if you've ever been a, if you've ever done any graphics, driver development. so you have a, a number of different APIs that achieve these two goals of, of, abstraction and, and of, of, of building a common abstraction and of building a, a high level abstraction. so OpenGL is the broadly the free, the free operating system world, the non Microsoft's world's choice, back in the day. [00:54:53] Elizabeth: And then direct 3D was Microsoft's API and they've and Direct 3D. And both of these have evolved over time and come up with new versions and such. And when any, API exists for too long. It gains a lot of croft and needs to be replaced. And eventually, eventually the people who developed OpenGL decided we need to start over, get rid of the Croft to make it cleaner and make it lower level. [00:55:28] Elizabeth: Because to get in a maximum performance games really want low level access. And so they made Vulcan, Microsoft kind of did the same thing, but they still call it Direct 3D. they just, it's, it's their, the newest version of Direct 3D is lower level. It's called Direct 3D 12. and, and, Mac looked at this and they decided we're gonna do the same thing too, but we're not gonna use Vulcan. [00:55:52] Elizabeth: We're gonna define our own. And they call it metal. And so when we want to translate D 3D 12 into something that another operating system understands. That's probably Vulcan. And, and on Mac, we need to translate it to metal somehow. And we decided instead of having a separate layer from D three 12 to metal, we're just gonna translate it to Vulcan and then translate the Vulcan to metal. And it also lets things written for Vulcan on Windows, which is also a thing that exists that lets them work on metal. [00:56:30] Jeremy: And having to do that translation, does that have a performance impact or is that not really felt? [00:56:38] Elizabeth: yes. It's kind of like, it's kind of like anything, when you talk about performance, like I mentioned this earlier, there's always gonna be overhead from translating from one API to another. But we try to, what we, we put in heroic efforts to. And try, try to make sure that doesn't matter, to, to make sure that stuff that needs to be fast is really as fast as it can possibly be. [00:57:06] Elizabeth: And some very clever things have been done along those lines. and, sometimes the, you know, the graphics drivers underneath are so good that it actually does run better, even despite the translation overhead. And then sometimes to make it run fast, we need to say, well, we're gonna implement a new API that behaves more like windows, so we can do less work translating it. And that's, and sometimes that goes into the graphics library and sometimes that goes into other places. Targeting Wine instead of porting applications [00:57:43] Jeremy: Yeah. Something I've found a little bit interesting about the last few years is [00:57:49] Jeremy: Developers in the past, they would generally target Windows and you might be lucky to get a Mac port or a Linux port. And I wonder, like, in your opinion now, now that a lot of developers are just targeting Windows and relying on wine or, or proton to, to run their software, is there any, I suppose, downside to doing that? [00:58:17] Jeremy: Or is it all just upside, like everyone should target Windows as this common platform? [00:58:23] Elizabeth: Yeah. It's an interesting question. I, there's some people who seem to think it's a bad thing that, that we're not getting native ports in the same sense, and then there's some people who. Who See, no, that's a perfectly valid way to do ports just right for this defacto common API it was never intended as a cross platform common API, but we've made it one. [00:58:47] Elizabeth: Right? And so why is that any worse than if it runs on a different API on on Linux or Mac and I? Yeah, I, I, I guess I tend to, I, that that argument tends to make sense to me. I don't, I don't really see, I don't personally see a lot of reason for, to, to, to say that one library is more pure than another. [00:59:12] Elizabeth: Right now, I do think Windows APIs are generally pretty bad. I, I'm, this might be, you know, just some sort of, this might just be an effect of having to work with them for a very long time and see all their flaws and have to deal with the nonsense that they do. But I think that a lot of the. Native Linux APIs are better. But if you like your Windows API better. And if you want to target Windows and that's the only way to do it, then sure why not? What's wrong with that? [00:59:51] Jeremy: Yeah, and I think the, doing it this way, targeting Windows, I mean if you look in the past, even though you had some software that would be ported to other operating systems without this compatibility layer, without people just targeting Windows, all this software that people can now run on these portable gaming handhelds or on Linux, Most of that software was never gonna be ported. So yeah, absolutely. And [01:00:21] Elizabeth: that's [01:00:22] Jeremy: having that as an option. Yeah. [01:00:24] Elizabeth: That's kind of why wine existed, because people wanted to run their software. You know, that was never gonna be ported. They just wanted, and then the community just spent a lot of effort in, you know, making all these individual programs run. Yeah. [01:00:39] Jeremy: I think it's pretty, pretty amazing too that, that now that's become this official way, I suppose, of distributing your software where you say like, Hey, I made a Windows version, but you're on your Linux machine. it's officially supported because, we have this much belief in this compatibility layer. [01:01:02] Elizabeth: it's kind of incredible to see wine having got this far. I mean, I started working on a, you know, six, seven years ago, and even then, I could never have imagined it would be like this. [01:01:16] Elizabeth: So as we, we wrap up, for the developers that are listening or, or people who are just users of wine, um, is there anything you think they should know about the project that we haven't talked about? [01:01:31] Elizabeth: I don't think there's anything I can think of. [01:01:34] Jeremy: And if people wanna learn, uh, more about the wine project or, or see what you're up to, where, where should they, where should they head? Getting support and contributing [01:01:45] Elizabeth: We don't really have any things like news, unfortunately. Um, read the release notes, uh, follow some, there's some, there's some people who, from Code Weavers who do blogs. So if you, so if you go to codeweavers.com/blog, there's some, there's, there's some codeweavers stuff, uh, some marketing stuff. But there's also some developers who will talk about bugs that they are solving and. And how it's easy and, and the experience of working on wine. [01:02:18] Jeremy: And I suppose if, if someone's. Interested in like, like let's say they have a piece of software, it's not working through wine. what's the best place for them to, to either get help or maybe even get involved with, with trying to fix it? [01:02:37] Elizabeth: yeah. Uh, so you can file a bug on, winehq.org,or, or, you know, find, there's a lot of developer resources there and you can get involved with contributing to the software. And, uh, there, there's links to our mailing list and IRC channels and, uh, and, and the GitLab, where all places you can find developers. [01:03:02] Elizabeth: We love to help you. Debug things. We love to help you fix things. We try our very best to be a welcoming community and we have got a long, we've got a lot of experience working with people who want to get their application working. So, we would love to, we'd love to have another. [01:03:24] Jeremy: Very cool. Yeah, I think wine is a really interesting project because I think for, I guess it would've been for decades, it seemed like very niche, like not many people [01:03:37] Jeremy: were aware of it. And now I think maybe in particular because of the, the Linux gaming handhelds, like the steam deck,wine is now something that a bunch of people who would've never heard about it before, and now they're aware of it. [01:03:53] Elizabeth: Absolutely. I've watched that transformation happen in real time and it's been surreal. [01:04:00] Jeremy: Very cool. Well, Elizabeth, thank you so much for, for joining me today. [01:04:05] Elizabeth: Thank you, Jeremy. I've been glad to be here.

Tu entends souvent cette question en séance :“À votre place, vous feriez quoi ?” ou “Mais vous me conseillez quoi, du coup ?” 

This week on Reimagining Cyber, we unpack one of the biggest supply chain attacks of the year: the NPM hack. Attackers compromised widely used packages like Chalk and Debug—billions of weekly downloads—slipping in code that silently hijacked crypto transactions. Tyler Moffitt joins us to explain how it happened, who's most at risk, and the practical steps every developer and security leader should take right now.Follow or subscribe to the show on your preferred podcast platform.Share the show with others in the cybersecurity world.Get in touch via reimaginingcyber@gmail.com As featured on Million Podcasts' Best 100 Cybersecurity Podcast and Best 70 Chief Information Security Officer CISO Podcasts rankings.

Major npm compromise A number of high-profile npm libraries were compromised after developers fell for a phishing email. This compromise affected libraries with a total of hundreds of millions of downloads a week. https://bsky.app/profile/bad-at-computer.bsky.social/post/3lydioq5swk2y https://github.com/orgs/community/discussions/172738 https://github.com/chalk/chalk/issues/656#issuecomment-3266894253 https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised HTTP Request Signatures It looks like some search engines and AI bots are starting to use the HTTP request signature. This should make it easier to identify bot traffic. https://isc.sans.edu/diary/HTTP%20Request%20Signatures/32266

This is a recap of the top 10 posts on Hacker News on September 08, 2025. This podcast was generated by wondercraft.ai (00:30): NPM debug and chalk packages compromisedOriginal post: https://news.ycombinator.com/item?id=45169657&utm_source=wondercraft_ai(01:51): Signal Secure BackupsOriginal post: https://news.ycombinator.com/item?id=45170515&utm_source=wondercraft_ai(03:12): Chat Control Must Be StoppedOriginal post: https://news.ycombinator.com/item?id=45173277&utm_source=wondercraft_ai(04:34): 14 Killed in anti-government protests in NepalOriginal post: https://news.ycombinator.com/item?id=45166972&utm_source=wondercraft_ai(05:55): Immich – High performance self-hosted photo and video managementOriginal post: https://news.ycombinator.com/item?id=45165684&utm_source=wondercraft_ai(07:17): Meta suppressed research on child safety, employees sayOriginal post: https://news.ycombinator.com/item?id=45167705&utm_source=wondercraft_ai(08:38): iPhone dumbphoneOriginal post: https://news.ycombinator.com/item?id=45171200&utm_source=wondercraft_ai(10:00): Experimenting with Local LLMs on macOSOriginal post: https://news.ycombinator.com/item?id=45168953&utm_source=wondercraft_ai(11:21): No adblocker detectedOriginal post: https://news.ycombinator.com/item?id=45176206&utm_source=wondercraft_ai(12:43): How RSS beat MicrosoftOriginal post: https://news.ycombinator.com/item?id=45166750&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

Tu es en séance, tu poses une question, et ton bénéficiaire part en digression, te coupe ou ne t'écoute qu'à moitié… et ça a tendance à te tendre

No matter how much you've achieved — degrees, titles, even a thriving business — do you still feel like you keep hitting the same wall? Maybe it's money. Maybe it's visibility. Maybe it's that quiet voice that says, “You're not enough.” The truth? That's not laziness or lack of discipline. Those are outdated destiny codes — unconscious patterns that keep you looping in scarcity, self-sabotage, and burnout. In Episode 3 of The Sovereign Path livestream series, I'm sharing how to debug your destiny codes and finally break free. You'll learn: ✅ The 3 hidden disguises of self-sabotage (Safety, Loyalty, Identity) ✅ Why success without sovereignty will always feel like bondage ✅ The 5-step Cornerstone Process™ to rewrite your story, rewire your brain, and reclaim authorship of your destiny ✅ A live guided practice to release one old code and install a new one — right here, right now This isn't about fixing yourself. It's about freeing yourself — so you can become the Architect of your Destiny.

Trajimos a un "Hacker" de los "BUENOS", pongan atención pa' que no se les duerma.

Named in honour of Simon's darting triumph, welcome to this week's podcast edition of the One Life Left radio show, dear listeners! This week we are joined by Super Special Guest Richie Shoemaker, games magazine editor extraordinaire, here to talk about new project Debug++ plus PCZone, MCV and A Certain Type of Game. We also review our time at Develop: Brighton last week which, of course, included Maraoke! Are you Liam Delahunty? What have you done since June 1997?? Let us know at team@onelifeleft.com or join our Discord and surprise us. Link below! TTFN,Team OLL x Links: The OLL Everything Link!http://hello.onelifeleft.com/ The Maraoke Everything Link!https://hello.maraoke.com Block Words Link!https://blockwords.app/ The Shure link!https://tag.gs/OneLifeLeft_Shure Reviews: HITMAN World of AssassinationPilotwings 64Super Mario StrikersElite Dangerous Learn more about your ad choices. Visit podcastchoices.com/adchoices

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVM 

Neste episódio técnico, mergulhamos nos conceitos fundamentais de Sistema Operacional que todo desenvolvedor deveria dominar. Com insights práticos e exemplos reais, discutimos sobre threads, paralelismo e alguns conceitos importantes para você que é desenvolvedor(a) sobre S.O. e o que isso impacta no desenvolvimento de sistemas. Tivemos a participação do Vinicios Cararine. Assuntos abordados no tema Introdução ao convidado Por que Devs precisam entender de Sistema Operacional Casos reais: apps lentos ou instáveis por ignorar conceitos de S.O. O que é uma thread Context switching: custos e impacto no desempenho Thread pools: quando usar e como configurar Paralelismo vs Concorrência - diferença, múltiplos cores vs. tempo compartilhado exemplos em linguagens (Go, Rust, Java) Quando usar multi-threading (ex.: servidores web) Quando evitar threads (ex.: tasks I/O-bound); Async/Await sob a perspectiva do SO. Links úteis Nosso Discord: https://discord.com/invite/hGpFPsV2gB Café Debug globalhttps://open.spotify.com/show/3S1OK2ecjZj7zoaZ34bFkP?si=ae09a6a1796a4587 Patrocinadora do programa https://king.host/ https://www.mongodb.com/products/tools/compass The Linux Kernel documentation https://www.kernel.org/doc/html/latest/ Operating System https://pages.cs.wisc.edu/~remzi/OSTEP/ Why Are Threads Needed On Single-Core Processors https://www.youtube.com/watch?v=M9HHWFp84f0 Livro Sistemas Operacionais Modernos - https://www.amazon.com.br/Sistemas-Operacionais-Modernos-Andrew-Tanenbaum/dp/8582606168/?_encoding=UTF8&pd_rd_w=wRcRl&content-id=amzn1.sym.454738cc-1d38-49bf-ab88-1bd74f2484a1%3Aamzn1.symc.abfa8731-fff2-4177-9d31-bf48857c2263&pf_rd_p=454738cc-1d38-49bf-ab88-1bd74f2484a1&pf_rd_r=K22XK4M0NPBDZ5XZRB5E&pd_rd_wg=P0TkT&pd_rd_r=be39ae3f-29cf-4b24-b82c-9cecafa25f60&ref_=pd_hp_d_btf_ci_mcx_mr_ca_id_hp_d Participantes Jéssica Nathany (Software Developer e host)LinkedIn: https://www.linkedin.com/in/jessica-nathany-carvalho-freitas-38260868/ Weslley Fratini (Software Developer e co-host)LinkedIn: https://www.linkedin.com/in/weslley-fratini/ Vinicios Cararine (Software Engineer na Splitcare)Linkedin: https://www.linkedin.com/in/vinicios-cararine/ Edição: Thiago Carvalhohttps://www.linkedin.com/in/thi-agocarvalho/ Dúvidas, sugestões ou anúncios envie para: debugcafe@gmail.comSee omnystudio.com/listener for privacy information.

Neste episódio, exploramos o MongoDB além do básico, focando nas tendências e práticas avançadas que estão moldando o futuro dos bancos de dados NoSQL. Conversamos com Jhonathan Soares sobre como usar MongoDB como sistema de cache, os desafios do Teorema de CAP em ambientes distribuídos, e as novas possibilidades de integração com inteligência artificial através de dados vetoriais e o protocolo MCP. Conheça o AI Agent do Mongodb. Assuntos abordados no tema Mongo como cache Teorema de CAP (breve menção) Melhor integração com inteligência artificial e dados vetoriais. Protocolo MCP Expansão de capacidades serverless via MongoDB Atlas. Read Secondary: cenários ideais para utilização Armadilhas comuns em dados inconsistentes Query pipelines cada vez mais sofisticados, substituindo ferramentas de ETL Edge computing com Mongo embutido em dispositivos (Realm). Maior uso de BSON + JSON Schema para validação automática. O que a IA deveria fazer com o Mongodb Links úteis Nosso Discord: https://discord.com/invite/hGpFPsV2gB Café Debug globalhttps://open.spotify.com/show/3S1OK2ecjZj7zoaZ34bFkP?si=ae09a6a1796a4587 Patrocinadora do programa https://king.host/ https://www.mongodb.com/products/tools/compass https://learn.mongodb.com/ https://dev-aditya.medium.com/understanding-temporary-inconsistency-in-mongodb-during-network-partitions-causes-and-solutions-7ab418a76ac5 https://www.educative.io/blog/what-is-cap-theorem https://openai.com/codex/ https://github.com/modelcontextprotocol https://www.mongodb.com/docs/manual/mcp/ https://www.mongodb.com/resources/basics/json-and-bson https://www.mongodb.com/pt-br/docs/atlas/architecture/current/solutions-library/manufacturing-agentic-ai-framework/ Participantes Jéssica Nathany (Software Developer e host)LinkedIn: https://www.linkedin.com/in/jessica-nathany-carvalho-freitas-38260868/ Weslley Fratini (Software Developer e co-host)LinkedIn: https://www.linkedin.com/in/weslley-fratini/Jonathan Soares (Senior Project Leader no Mercado Livre e Criador de Conteúdo do Código Simples) Linkedin:https://www.linkedin.com/in/jhonathansoares/Codigo simples: https://codigosimples.net/ Produtora AGO Filmes: https://thiagocarvalhofotografia.wordpress.com/dúvidas, sugestões ou anúncios envie para: debugcafe@gmail.comSee omnystudio.com/listener for privacy information.

Comment les jeux psychologiques — souvent invisibles — peuvent impacter ta relation d'accompagnement et comment en sortir sans t'épuiser ni blesser l'autre ?Question à 10000 balles !

Neste episódio, conversamos sobre as diferenças entre ser contratado como CLT e como PJ no mercado de tecnologia. Discutimos os impactos na vida de Devs, QAs, DevOps e até gerentes de tecnologia, abordando pontos como carga tributária, segurança jurídica, oportunidades no exterior, planejamento financeiro e muito mais. Assuntos abordados no tema Introdução ao tema e ao participante Diferença entre contratação CLT e PJ (visão prática, jurídicam, vantagens e desvantagens) Tributos envolvidos para PJ (Simples Nacional, MEI, Lucro Presumido etc.) O que ninguém te conta antes de virar PJ PJ precisa de contador? Quanto custa manter uma empresa? Planejamento financeiro ao se tornar PJ (instabilidade, reserva de emergência, impostos…) PJ para exterior: Como funciona a contratação de devs brasileiros por empresas de fora? Plataformas como Remessa Online, Remote, Oyster, Wise, etc. Impostos para PJ que presta serviço para o exterior Links úteis Nosso Discord: https://discord.com/invite/hGpFPsV2gB Café Debug globalhttps://open.spotify.com/show/3S1OK2ecjZj7zoaZ34bFkP?si=ae09a6a1796a4587 https://www.husky.io/melhor-opcao-receber-do-exterior Participantes Jéssica Nathany (Software Developer e host)LinkedIn: https://www.linkedin.com/in/jessica-nathany-carvalho-freitas-38260868/ Weslley Fratini (Software Developer e co-host)LinkedIn: https://www.linkedin.com/in/weslley-fratini/ André Aranha (Profissional de TI setor financeiro e criador conteúdo ContratoPJ)LinkedIn: https://www.linkedin.com/in/andrearanha/Canal Youtube: https://www.youtube.com/@Contrato_PJ Produtora AGO Filmes: https://thiagocarvalhofotografia.wordpress.com/dúvidas, sugestões ou anúncios envie para: debugcafe@gmail.comSee omnystudio.com/listener for privacy information.

Tu procrastines, tu sabotes une opportunité, tu te bloques au dernier moment ?

In deze aflevering van De Nederlandse Kubernetes Podcast spreken hosts Ronald Kers (CNCF Ambassador) en Jan Stomphorst (Solutions Architect bij ACC ICT) met Evelien Schellekens, Solutions Architect bij Elastic. We ontmoeten haar tijdens een live opname op de Veluwe, waar de sfeer informeel en energiek is – een perfecte setting voor een spontaan en inhoudelijk gesprek over Kubernetes, logging, observability en certificering.Van astronautendroom naar Kubernetes-certificeringen Evelien vertelt hoe haar IT-carrière begon met het open schroeven van computers samen met haar vader. Inmiddels heeft ze haar sporen verdiend met meerdere Kubernetes-certificeringen – vier in drie dagen tijd! Ze deelt haar aanpak, hoe ze zich voorbereidt, waarom AI soms helpt (en soms juist niet), en wat haar dreef om zich in recordtempo te certificeren.Elastic: meer dan Elasticsearch Ze legt uit hoe Elastic geëvolueerd is tot een veelzijdig Search AI Platform met drie hoofdoplossingen:Search: van productzoekmachines tot document indexingObservability: metrics, logs, tracing, profilingSecurity: SIEM, endpoint protection en anomaly detectionElastic draait perfect op Kubernetes met behulp van de Elastic Cloud on Kubernetes (ECK) operator. We bespreken best practices zoals het gebruik van CRD's, het vermijden van single points of failure, en waarom drie master nodes het minimum zijn voor een productiecluster.Logging zonder sidecars Een interessant deel van het gesprek gaat over logging: hoe je zonder sidecars volledige observability kunt realiseren via agents zoals Filebeat of Elastic Agent. Evelien legt uit hoe je debug-logging onder controle houdt met ingest pipelines en log-retentiebeleid, en waarom sommige developers nét iets te enthousiast debug inschakelen.De toekomst: OpenTelemetry Volgens Evelien ligt de toekomst van observability in OpenTelemetry, een CNCF-project dat snel aan populariteit wint. Net zoals Kubernetes nu de standaard is voor container orchestration, ziet zij OpenTelemetry als de aanstaande standaard voor vendor-neutrale observability én security-integratie.Eindconclusie Evelien combineert technische diepgang met een heldere uitleg van concepten. Of het nu gaat om logbeheer, schaalbaarheid op Kubernetes, of de rol van Elastic binnen moderne DevOps-praktijken – deze aflevering zit vol praktische inzichten én een flinke dosis energie.Stuur ons een bericht.Dutch Cloud Native Day 2025Koop je tickets met kortingscode: Community30 en ontvang 30% korting! https://acc-ict.com/liveSupport the showLike and subscribe! It helps out a lot.You can also find us on:De Nederlandse Kubernetes Podcast - YouTubeNederlandse Kubernetes Podcast (@k8spodcast.nl) | TikTokDe Nederlandse Kubernetes PodcastWhere can you meet us:EventsThis Podcast is powered by:ACC ICT - IT-Continuïteit voor Bedrijfskritische Applicaties | ACC ICT

Nós começamos uma pequena série sobre Devs e Empreendedores, vamos entrevistar desenvolvedores que ainda programam e tem seu próprio negócio. Como gerenciam seu tempo? Como organizam suas empresas? Neste programa entrevistamos o Franco Lamping que compartilhou sua experiência com nós. Assuntos abordados no tema Apresentação do convidado A carreira como desenvolvedor De onde surgiu a ideia de fundar a 180 Seguros e como o motivou? Como foi sair de uma das maiores fintechs brasileiras para arriscar no seu próprio negócio? Como pensar em um MVP? Qual melhor caminho? Desafios e como ser um bom gestor Desenvolvedores precisam empreender? (opinião pessoal) Programador(a) vai sempre ser um programador(a) ou é natural ir para o caminho da gestão? Na sua opinião, como você enxerga o mercado de tecnologia para desenvolvedores e empreendedores com tanto avanço e investimentos em IA? Gerenciamento de tempo Links úteis Nosso Discord: https://discord.com/invite/hGpFPsV2gB Café Debug globalhttps://open.spotify.com/show/3S1OK2ecjZj7zoaZ34bFkP?si=ae09a6a1796a4587 https://180s.com.br/ Patrocinadora do programa https://king.host/ Participantes Jéssica Nathany Software Developer e host)LinkedIn: https://www.linkedin.com/in/jessica-nathany-carvalho-freitas-38260868/Weslley Fratini (Software Developer e co-host)LinkedIn: https://www.linkedin.com/in/weslley-fratini/ Franco Lamping (Co-Fundador e CTO da 180 Seguros) LinkedIn: https://www.linkedin.com/in/francolamping/ Anuncie em nosso site: http://www.cafedebug.com.brProdutora AGO Filmes: https://thiagocarvalhofotografia.wordpress.com/ dúvidas, sugestões ou críticas construtivas envie para: debugcafe@gmail.comSee omnystudio.com/listener for privacy information.

Tu te dis que fuir le conflit, c'est préserver la paix ?

Neste episódio, conversamos sobre a importância das soft skills na carreira de quem desenvolve software. Apesar do foco técnico ser essencial, cada vez mais empresas valorizam profissionais que sabem se comunicar bem, trabalhar em equipe, lidar com feedbacks e resolver problemas de forma colaborativa. Com a presença do Tiago Aguiar e Daniel Jesus. Assuntos abordados no tema Introdução ao tema O que são soft skills e porque elas são tão relevantes para devs? Habilidades mais valorizadas além da técnica: comunicação, colaboração, empatia, inteligência emocional, pensamento crítico.. Por que devs técnicos incríveis podem perder oportunidades por falta de soft sills? Como as soft skills impactam no trabalho remoto e na convivência em times diversos? Diferenças entre dev jr, pleno e sênior vai além da stack: maturidade e autonomia contra Dificuldades comuns de devs com soft skills e como desenvolvê-las na prática Como se preparar para entrevistas técnicas que também avaliam comportamento Dicas de cursos, livros e podcasts Links úteis Nosso Discord: https://discord.com/invite/hGpFPsV2gB Café Debug globalhttps://open.spotify.com/show/3S1OK2ecjZj7zoaZ34bFkP?si=ae09a6a1796a4587 Patrocinadora do programa https://king.host/ https://www.husky.io/melhor-opcao-receber-do-exterior https://www.amazon.com.br/Upstarts-Airbnb-Companies-Sil%C3%ADcio-Mudando/dp/8551002082 https://www.amazon.com.br/Como-fazer-amigos-influenciar-pessoas/dp/8543108683 https://www.amazon.com.br/arte-comunica%C3%A7%C3%A3o-impacto-naturalidade-potencialize/dp/6555443464 Participantes Jéssica Nathany (Software Developer e host)LinkedIn: https://www.linkedin.com/in/jessica-nathany-carvalho-freitas-38260868/ Weslley Fratini (Software Developer e co-host)LinkedIn: https://www.linkedin.com/in/weslley-fratini/Tiago Aguiar (Desenvovledor .NET na InfoJobs e Criador de conteúdo)Site: https://beacons.ai/aguiardev Daniel Jesus (Líder Técnico na XP e Criador de conteúdo)Linkedin: https://www.linkedin.com/in/djesusnet/Site: https://danieljesus.io/ Produtora AGO Filmes: https://thiagocarvalhofotografia.wordpress.com/dúvidas, sugestões ou anúncios envie para: debugcafe@gmail.comSee omnystudio.com/listener for privacy information.

Neste programa, convidamos a Ludmila Pontremolez CTO e Cofundadora da Zippi, para entender como ela enxerga as transformações recentes no mercado de desenvolvimento de software. A conversa traz uma visão estratégica sobre contratação, capacitação, impacto da IA nas equipes técnicas, mudanças nos modelos de trabalho e o que realmente importância na hora de formar e reter bons talentos. Assuntos abordados no tema Introdução ao tema: como o mercado mudou do ponto de vista da liderança O que mudou nas demandas das empresas entre 2024 e 2025? Como a IA está impactando a gestão e a produtividade dos times de tecnologia? Reorganização dos times: devs generalistas, especialistas ou híbridos? Como CTOs estão escolhendo talentos e avaliando competências técnicas e comportamentais Como a empresa pode fomentar um ambiente que estimula crescimento técnico e pessoal? O papel do Dev no core do negócio: expectativa de visão estratégica além do código Visão sobre a adoção de IA como ferramenta de apoio (ex: GitHub Copilot, ChatGPT, etc.) Modelos de trabalho: o que CTOs preferem hoje? Remoto, híbrido ou presencial? O que os líderes esperam dos devs iniciantes hoje? Desenvolvedores excepcionais que não sem bem avaliados e perdem oportunidades A importância de ter devs que otimizam sistemas críticos e pensam em performance e escalabilidade Links úteis Nosso Discord: https://discord.com/invite/hGpFPsV2gB Café Debug globalhttps://open.spotify.com/show/3S1OK2ecjZj7zoaZ34bFkP?si=ae09a6a1796a4587 Patrocinadora do programa https://king.host/ https://www.jetbrains.com/pt-br/lp/devecosystem-2024/ https://www.gitclear.com/ai_assistant_code_quality_2025_research https://www.spiceworks.com/research/it-report/ Dynamic programming https://www.youtube.com/watch?v=Hdr64lKQ3e4 Episódio 131 participação da Ludmila https://open.spotify.com/episode/6EOzeVA003rWVEZefnG3rn Participantes Jéssica Nathany (Software Developer e host)LinkedIn: https://www.linkedin.com/in/jessica-nathany-carvalho-freitas-38260868/ Ludmila Pontremolez (CTO e Cofundadora da Zippi)Linkedin: https://www.linkedin.com/in/ludmilapontremolez/ Produtora AGO Filmes: https://thiagocarvalhofotografia.wordpress.com/dúvidas, sugestões ou anúncios envie para: debugcafe@gmail.comSee omnystudio.com/listener for privacy information.

"J'ai tout essayé", "je fais tout ce qu'il faut mais rien ne change" : et si la solution, c'était d'arrêter de faire ?

O que mudou do mercado de desenvolvimento nos últimos 2 anos? Convidei Tiago Aguiar para discutir esse assunto. Fizemos um balanço sobre alguns pontos importantes a ser considerado na carreira de desenvolvimento de software, e como desenvolvedores podem se capacitar com tanta mudança e tendência em IAs. Assuntos abordados no tema Introdução ao tema O que mudou no mercado de trabalho de 2024 para 2025 Modelo de trabalho híbrido O que Devs iniciantes ou não precisam se atualizar Comentando alguns tópicos da pesquisa Spiceworks report Como usar ferramentas de IA para produtividade sem depender dela Devs que usam Copilot tem 55% mais chance de aprovação em entrevistas Capacitação: como se capacitar em um mundo com tanta mudança? Portfólio relevante no Github Hard skills não é o suficiente é preciso também de soft skills Inglês ja não é mais o diferencial Otimizar sistemas críticos torna um Dev de valor Links úteis Nosso Discord: https://discord.com/invite/hGpFPsV2gB Café Debug globalhttps://open.spotify.com/show/3S1OK2ecjZj7zoaZ34bFkP?si=ae09a6a1796a4587 Patrocinadora do programa https://king.host/ https://www.jetbrains.com/pt-br/lp/devecosystem-2024/ https://www.gitclear.com/ai_assistant_code_quality_2025_research https://www.spiceworks.com/research/it-report/ Vídeo sobre estrutura de dados https://www.youtube.com/watch?v=7kf1SACqlRw System Design interview Google https://www.youtube.com/watch?v=Ti5vfu9arXQ Dynamic programming https://www.youtube.com/watch?v=Hdr64lKQ3e4 Participantes Jéssica Nathany (Software Developer e host)LinkedIn: https://www.linkedin.com/in/jessica-nathany-carvalho-freitas-38260868/ Weslley Fratini (Software Developer e co-host)LinkedIn: https://www.linkedin.com/in/weslley-fratini/ Tiago Aguiar (Desenvovledor .NET na Redarbor Brasil e Criador de conteúdo)Site: https://beacons.ai/aguiardev Produtora AGO Filmes: https://thiagocarvalhofotografia.wordpress.com/dúvidas, sugestões ou anúncios envie para: debugcafe@gmail.comSee omnystudio.com/listener for privacy information.

AI-based coding has exploded in popularity on the promise that it will make developers' jobs faster and easier. But it's also resulted in something else: a vast increase in lines of code, and thus the likelihood of bugs resulting in crashes or other mishaps. Learn more about your ad choices. Visit podcastchoices.com/adchoices

Já parou para pensar que os Sistemas Embarcados estão presentes em praticamente tudo ao nosso redor? Desde o seu smartphone até a sua geladeira, passando por carros, aviões e dispositivos médicos, esses sistemas são a base da tecnologia moderna. Neste programa, conversamos com Gleisson Bezerra, especialista em IO, Machine Learning e Sistemas Embarcados que explicou tudo pra nós. Assuntos abordados no tema O que são Sistemas Embarcados e porque eles são tão importantes? Linguagens utilizadas: C, C++, Python, Rust e Assembly Definição técnica: hardware + software dedicado a uma função específica Diferença entre sistemas embarcados e computadores tradicionais Dados curiosos: exemplos de onde os sistemas embarcados estão presentes (eletrodomésticos, carros, dispositivos médicos, etc.) Aplicações e Sistemas Críticos: Indústria automotiva: sistemas de controle, sensores, carros autônomos, smart home, agro, e etc. Aplicações real-time Inteligência Artificial em sistemas embarcados Por onde começar a desenvolver sistemas embarcados: ferramentas, linguagens como testar Habilidades necessárias: programação, eletrônica, pensamento lógico Mercado de trabalho: oportunidade de crescimento, carreira e formação Links úteis Nosso Discord: https://discord.com/invite/hGpFPsV2gB Café Debug Global https://open.spotify.com/show/3S1OK2ecjZj7zoaZ34bFkP?si=ae09a6a1796a4587 Pesquisa de satisfação Café Debug 2024 https://docs.google.com/forms/d/e/1FAIpQLSdlkPGS-sqfD3QOmkddRDqj7dlYE8mpIlZXORIfTtn-MztKKA/viewform Patrocinadora do programa https://king.host/ https://embarcados.com.br/o-que-sao-sistemas-embarcados/ https://victorvision.com.br/blog/sistemas-embarcados/ https://www.linkedin.com/pulse/voc%C3%AA-inteiro-dentro-do-metaverso-parte-1-de-2-gleisson-s-bezerra/ https://www.youtube.com/watch?v=J2pHgzdAJRk Participantes Jéssica Nathany (Software Developer e host)LinkedIn: https://www.linkedin.com/in/jessica-nathany-carvalho-freitas-38260868/ Weslley Fratini (Software Developer e co-host)LinkedIn: https://www.linkedin.com/in/weslley-fratini/Gleisson Bezerra (Especialista em Machine Learning no Google e PhD no ITA)LinkedIn: https://www.linkedin.com/in/gleisson/ Produtora AGO Filmes: https://thiagocarvalhofotografia.wordpress.com/dúvidas, sugestões ou anúncios envie para: debugcafe@gmail.comSee omnystudio.com/listener for privacy information.

Invest Like the Best Key Takeaways  Identify and invest in outliers: The best venture capital investors recognize outlier potential when they see it and have a curiosity to discover what makes the outlier tick and WHY they tick that way On being a VC or a founder: Inherent builders should be in the field – they should be building companies, not coaching other builders Debug problems as far upstream as possible; take the rocks out of the river so the water can flow as fast as possible  Black magic is reserved for founders; every other area of the company-building process is mere mortal stuff Stewardship over ownership: The goal is to leave your creation in a better place for the next generation It is okay to choose the parallel tracked path of banking or consulting, and it is okay to take risks, but it is not okay to do one and spend your life thinking you did the other The most common mistake that investors make is doing something contrary to the best interests of the founder Traits of the best investment memos:(1) Clearly state the one or two strongest reasons to invest(2) Two to three pages max(3) Present clear data from the opposing side(4) argue why the investment should happen despite the opposing dataSuccess starts at the foundational layer: Great culture is downstream of getting the foundation right and fostering internal belief, which is all a firm needs to be successful Performance is the cultural component that matters mostRead the full notes @ podcastnotes.orgWelcome to this classic episode. Classics are my favorite episodes from the past 10 years published once a month. These are N of one conversations with N of one people. There's nobody I've met quite like Doug Leone. Doug led one of the world's most successful venture firms, Sequoia, for over 25 years after he was given responsibility for the firm by its founder, Don Valentine, in 1996. Alongside Mike Moritz, the pair managed its expansion from a single $150m early-stage fund into an $85 billion global powerhouse. It was a privilege to sit down with Doug and learn from him. We talk about his tough start at Sequoia, get into the technicalities of great go-to-market motions, and survey his advice for other investors in the industry. A key theme that will stick with me from this conversation is Doug's insistence on keeping things simple and clear. I listen to this at least once a year. I hope you enjoy it. Subscribe to Colossus Review. For the full show notes, transcript, and links to mentioned content, check out the episode page here. ----- This episode is brought to you by Passthrough. Passthrough streamlines subscription documents, KYC, and AML compliance, so you can focus on running your fund, not managing paperwork. New SEC Update 31 CFR hits investment firms in under a year, and managers are getting ready for it now. If you think basic OFAC screening is enough, think again. You'll need continuous monitoring of your investors and all their beneficial owners across multiple watchlists, plus a comprehensive anti money laundering program. Passthrough has already processed 50,000 LPs and built the complete solution. Don't risk SEC deficiency letters, fines, or regulatory enforcement. Visit passthrough.com to get compliant now. ----- Invest Like the Best is a property of Colossus, LLC. For more episodes of Invest Like the Best, visit joincolossus.com/episodes.  Past guests include Tobi Lutke, Kevin Systrom, Mike Krieger, John Collison, Kat Cole, Marc Andreessen, Matthew Ball, Bill Gurley, Anu Hariharan, Ben Thompson, and many more. Stay up to date on all our podcasts by signing up to Colossus Weekly, our quick dive every Sunday highlighting the top business and investing concepts from our podcasts and the best of what we read that week. Sign up here. Follow us on Twitter: @patrick_oshag | @JoinColossus Show Notes [00:00:00] Welcome to Invest Like the Best [00:05:21] What Don Valentine's heart was like [00:08:30] The most productive and unproductive parts of Don's toughness  [00:12:55] Why it's so important to understand someone's core motivations [00:18:44] The most formative experiences he had prior to becoming an investor that impacted his investing the most  [00:22:37] What venture looks like to him today relative to his prior career [00:28:37] Whether or not he'd go into venture today if he was in his late 20s  [00:34:10] Helping companies circumnavigate mediocre positioning  [00:39:15] How interacting with companies early on has changed over the ears [00:43:12] Whether or not new entrants into venture should build firms with enterprise value  [00:48:14] Sussing out the killer gene in somebody  [00:51:04] How successful people can instill the lessons learned from hardship into their children  [00:54:30] Whether or not competitive advantage can be architected ahead of time when building a company   [00:57:21] The early 2000s clawback at Sequoia and what navigating that period was like  [01:01:06] What he's learned about picking the right LPs and partnering with them [01:04:18] Making sure that performance is on everyone's minds all the time  [01:09:59] The kindest thing anyone has ever done for him

Wherein Chris has a benchy and Frank is stuck in the 90's.

With tracks from Max Essa, Grabo'sky, Romanski, Manuel Tur, Scruscru & Dwaal, Erol Alkan, Debug, Children Of Toni, Martin Matiske, C.O.M.B.I., Totem Projects, Tech Support, Sex Judas Feat. Ricky, Franc Spangler & Hudson's Choice, Adam Stegemann & Universal Cave, Jaz, YUF-O, Yuksek & Diogo Strausz, Cale Parks, Jan Driver, Gazpa. Contact: dj@ribeaud.ch.

Original text by Darin Adler. An overview of the Motorola MEK6800D2 single board computer/development kit. Roger Heinen “engineers are a dime a dozen” story from episode 40 of the Algorithms + Data Structures = Programs Podcast. The General Magic documentary is a good hard look at how General Magic fizzled out, though it somehow managed to survive long enough to power the General Motors OnStar service. Darin Adler later joined the Nautilus (a.k.a. the GNOME desktop file manager) development team with Andy Hertzfeld at Eazel. Demonstration. Bryan Cantrill recounts the object-oriented operating system craze of the 1990s and counts the corpses: Spring, Taligent, Copland, and JavaOS. Lisa Melton recounts crisis management at Eazel and the history of the Safari and WebKit project on episode 11 of the Debug podcast. Waldemar Horwat went on to head JavaScript development at Netscape. Like many other eerily smart math and programming language types, he now works at Google.