Podcasts about Electron

Si parla di Electron, della nuova icona di Spotify, di canzoni fatte con l'AI, della nuova app di Maurizio Natali, dei cinturini degli Apple Watch, di alcuni progetti su GitHub molto interessanti e di un servizio di newsletter.

Today we are joined by Marco Giuliani, Vice President & Head of Research at ThreatDown, discussing their work on "GachiLoader adopts AI skill lure." Threat actors are now using fake AI agent “skills” as highly convincing social engineering lures, with a new campaign disguising the GachiLoader malware as a legitimate OpenClaw tool for automated Polymarket betting. Victims are tricked through fake installation guides and polished Electron apps into downloading malware that deploys the Rhadamanthys infostealer using fileless injection and blockchain-based command-and-control infrastructure. Researchers say the campaign marks an evolution in cybercrime, turning AI skill ecosystems into a new phishing-style attack surface. The research and executive brief can be found here: ⁠GachiLoader adopts AI skill lure Learn more about your ad choices. Visit megaphone.fm/adchoices

Pre-show: Marco has something to commend Ubiquiti marketing video Spanning Tree Protocol Sonos & Networking Documentation Follow-up: Formula 1 on Apple TV The case for alarm reminders (via Matthew Cave) SVG can do animations — and way more! (via Vítor) SVG can do THAT‽ Yes, you can use AI for ffmpeg, but have you tried Lossless Cut? SF Symbols in Marco’s Reminder app (via Clarko) How can we bemoan Electron and cheer WebViews? (via Julian Gamble) If Finder moves are no good, are mvs the same? Defrag lives on …in APFS diskutil apfs defragment [disk] enable [disk] is something along the lines of diske3 or disk3s1, that you get via diskutil list MJ Tsai AI Sentiment AI levels… down?… your worst coworker (via Nathan) Ireland compels data center developers to bring their own clean energy (via Ian Robinson) Large Energy User Action Plan Perspectives on art Original Monet The Ferrari Luce Previously on ATP Purosangue Jaguar I-Pace BMW i3 BMW i8 GMA T.33 Porsche Taycan Galleries The Verge Car and Driver Exterior Interior Coverage The Verge Top Gear Cleo Abram MKBHD (stationary tour) ba-dum tss John’s EV Stupidity Checklist Saturday Night Live Affordance Post-show: RIP Destiny 2 Associated layoffs, because, of course Destiny 1 on Wikipedia Penny Arcade Members-only ATP Overtime: Bambu vs. its community How one private message could change the face of 3D printing Sponsored by: zocdoc: Find the right doctor, right now. Squarespace: Save 10% off your first purchase of a website or domain using code atp. Become a member for ATP Overtime, ad-free episodes, member specials, and our early-release, unedited “bootleg” feed!

Rocket Lab (NASDAQ:RKLB) has been a 20-bagger on the 7investing scorecard, but at $150/share today, is it still a buy? 7investing founder Simon Erickson walks through the 11th iteration of his full discounted cash flow model, projecting Rocket Lab's revenues across three divisions: Electron launches, the upcoming Neutron rocket, and Space Systems manufacturing, all the way out to 2041. The bottom line: using a 10.3% weighted average cost of capital and conservative assumptions, Simon arrives at an intrinsic value of $45.12 per share, up significantly from $27 in last year's model, but still well below today's market price.The bull case for the long-term thesis remains intact. Electron is on pace for 30 launches in 2026, scaling toward 50 annually by 2030. Neutron, expected to launch by year-end at ~$55 million per launch versus Electron's $9 million, represents the single biggest margin step-change in the company's history. And Rocket Lab's total backlog has already jumped from $1.8 billion at year-end 2025 to $2.2 billion in just one quarter, with Simon projecting it reaches $4.3 billion by end of 2026 as Golden Dome, Space Force NSSL, and Space Development Agency contracts come into focus. Space Systems revenue is modeled to grow from $400 million today to $1.6 billion in 2027 and $11 billion by 2041.Simon is clear: the market is pricing in a lot more optimism than his model justifies, and at $150/share he's not adding. His personal buy target is closer to $40–$50. But he's holding every share — because when Neutron succeeds and the acquisition strategy compounds, the upside case is genuinely enormous. This is the most detailed public look at Rocket Lab's valuation you'll find anywhere.Stocks Mentioned:Rocket Lab (NASDAQ:RKLB)Varda Space Industries — privateGlobalstar (NASDAQ:GSAT)Blue Origin — private (owned by Jeff Bezos)SpaceX — private (owned by Elon Musk)#RocketLab #RKLB #SpaceStocks #GrowthStocks #DCFValuation #StockAnalysis #NeutronRocket #SpaceInvesting #DefenseStocks #StocksToWatch #InvestingIn2026 #7investing #Simonerickson

Кирилл Булатов помогает разрабатывать Zed – редактор кода, написанный на Rust командой, которая раньше делала Atom. Без Electron, без готовых UI-фреймворков: у Zed собственный графический движок GPUI, Tree-sitter как основа для парсинга и CRDT для совместного редактирования без конфликтов. В выпуске Кирилл объясняет, почему команда выбрала именно этот путь и что из этого получилось. Разберём архитектуру редактора изнутри: что происходит от открытия файла до работы с AI-агентом, как устроен протокол ACP, зачем Zed написал собственный UI-движок вместо использования готового и почему команда не стала брать экосистему плагинов VSCode. Поговорим о пользователях, конкурентах и о том, как опенсорсный редактор вообще планирует зарабатывать. Также ждем вас, ваши лайки, репосты и комменты в мессенджерах и соцсетях!
 Telegram-чат: https://t.me/podlodka Telegram-канал: https://t.me/podlodkanews Twitter-аккаунт: https://twitter.com/PodcastPodlodka Ведущие в выпуске: Стас Цыганов, Евгений Кателла Полезные ссылки: Github https://github.com/zed-industries/zed/ Блог Zed https://zed.dev/blog

Why does a pencil work so perfectly? Why does graphite leave marks on paper instead of just crumbling apart? And what do pancakes, honeycombs, geckos, and intermolecular forces have to do with any of it? This week we follow a simple pencil all the way down to carbon atoms, graphene sheets, and the weirdly satisfying chemistry that makes writing possible. Plus: final exam horror stories, missed alarms, and why reading the syllabus might save your GPA. Support this podcast on Patreon Buy Podcast Merch and Apparel Check out our website at chemforyourlife.com Watch our episodes on YouTube Find us on Instagram, Twitter, and Facebook @ChemForYourLife Timestamps 0:00 – The strangely satisfying feeling of fresh pencils 1:03 – So… how do pencils actually work? 2:07 – A “polymer eraser” sparks this whole episode 3:10 – Are pencils disappearing for Gen Alpha? 4:35 – Graphite, graphene, and carbon structures 6:20 – What graphene actually looks like 7:10 – Carbon bonding and tetrahedral shapes 8:10 – Double bonds and flat molecular structures 9:40 – Electron highways and conductivity 10:20 – Melissa's graphene model demonstration 13:10 – Why graphene could replace silicon chips 13:30 – Carbon nanotubes explained 14:40 – What holds graphite layers together? 15:00 – Intermolecular forces return 17:10 – Quick refresher on intermolecular forces 18:50 – London dispersion forces and temporary dipoles 19:30 – Why graphite is brittle 20:00 – How pencils leave marks on paper 21:20 – Why graphite is basically perfectly designed for writing 22:00 – A detour into paper, parchment, and writing history 24:00 – Pencil hardness and clay mixtures 26:30 – Jam attempts a chemistry-heavy recap 33:20 – Cliffhanger: how erasers work 34:00 – Final exam disaster stories 36:50 – Oversleeping a college final 39:10 – Melissa's sprint across campus in pajamas 41:00 – Read the syllabus. Seriously. 43:10 – Teasing next episode: erasers and other forms of carbon Support this podcast on Patreon Buy Podcast Merch and Apparel Check out our website at chemforyourlife.com Watch our episodes on YouTube Find us on Instagram, Twitter, and Facebook @ChemForYourLife References from the Episode: Thanks to our monthly supporters Kelly D. Bri Summer Alden Amanda Raymond Kyle McCray Justine Ash Vince W Julie S. Heather Ragusa Autoclave Dorien VD Scott Beyer Jessie Reder J0HNTR0Y Jeannette Napoleon Cullyn R Erica Bee Elizabeth P Rachel Reina Letila Katrina Barnum-Huckins Suzanne Phillips Venus Rebholz Jacob Taber Brian Kimball Kristina Gotfredsen Timothy Parker Steven Boyles Chris Skupien Chelsea B Avishai Barnoy Hunter Reardon Support this podcast on Patreon Buy Podcast Merch and Apparel Check out our website at chemforyourlife.com Watch our episodes on YouTube Find us on Instagram, Twitter, and Facebook @ChemForYourLife Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

A screencast from Chapter 19 in CH 223 entitled “Electron Configurations for Transition Metals”

Microwave Journal talks with Geoff Greening and Russ Army from CPI Electron Device Business about the design challenges and applications for high-energy microwave systems. Sponsored by CPI Electron Device Business.

  In this episode, Ray Cochrane leads with Mozilla shipping Firefox 150 with 271 patched bugs found by Anthropic’s Mythos system, the first major real-world deployment of the AlphaGo-Moment cybersecurity tooling. He also covers a 9-year dormant Linux kernel root, a college student stopping Taiwan’s high-speed rail with a software-defined radio, GitHub MCP secret scanning going GA, the NVIDIA NeMo lawsuit surviving its motion to dismiss, the Hugging Face Reachy Mini app store, Anthropic’s Auto Mode for Claude Code, and the 4-gigabyte AI model Chrome silently installed on your computer. – Want to start a podcast? Its easy to get started! Sign-up at Blubrry – Thinking of buying a Starlink? Use my link to support the show. Subscribe to the Newsletter. Email Ray if you want to get in touch! Like and Follow Geek News Central’s Facebook Page. Support my Show Sponsor: Best Godaddy Promo Codes Get 1Password Full Summary Cochrane opens the show with the AlphaGo Moment moving from theory into production. Mozilla shipped Firefox 150 this week with 271 patched bugs that Anthropic’s Mythos system found. Furthermore, the broader episode threads a clear pattern: AI tooling is reshaping security, developer workflows, and consumer software faster than the surrounding ecosystem can absorb it. The show closes on the four-gigabyte AI model Chrome installed on a billion machines without explicit consent. Mozilla Ships 271 Mythos Bugs in Firefox 150 Mozilla ran Anthropic’s restricted Mythos system against the Firefox 150 codebase before shipping. The result: 271 found bugs (180 high severity, 80 moderate, 11 low) baked into the release. However, the bigger number is the year-over-year jump. April 2026 shipped 423 total Firefox security fixes versus 31 a year prior. The breakdown for April: 271 from Mythos, 41 from external researchers, and 111 from other internal sources. Cochrane is sticking to his guns on calling this the AlphaGo Moment for cybersecurity. Skeptics argue Mythos is industrial-scale fuzzing because most found bugs sit in memory-safety territory. However, his counter is the velocity itself. Furthermore, he frames the resistance as carriage-versus-cars: humans-first research still grounds the tool, but throughput is the win. The Firefox CTO put it directly: defenders finally have a chance to win, decisively. For developers asking whether Mythos changes anything if they already run fuzzers, Cochrane’s answer is yes, and not even close. Additionally, he notes Mythos is restricted-access. The broadly available tier is Claude Opus 4.7, which Mozilla used since February before getting onto the restricted program for the Firefox 150 cycle. Run Opus 4.7 first. Sponsor: GoDaddy GoDaddy has been sponsoring this show for over twenty years. Economy hosting starts at $6.99/month, WordPress hosting at $12.99/month, and domains at $11.99. Use codes at geeknewscentral.com/godaddy for exclusive deals and to directly support the show. Copy Fail: 9-Year Linux Kernel Bug, 732 Bytes to Root A 9-year-old dormant Linux kernel bug got disclosed April 29 as CVE-2026-31431. Researchers published a 732-byte Python script that roots every major Linux distribution shipped since 2017. Additionally, CISA added the CVE to its Known Exploited Vulnerabilities catalog on May 1 with a May 15 federal deadline. The bug lives in the kernel’s crypto socket layer through the AF_ALG AEAD interface, originating in a 2017 in-place crypto optimization that lacked bounds checking. Cloudflare published their post-mortem this week. Their first instinct was to remove the kernel module entirely. However, service dependencies forced a workaround instead. Cloudflare resumed normal patched-kernel reboot automation across their 330-city fleet on May 4, with manual reboots and rollouts continuing after. Taiwan Rail Stopped by a 23-Year-Old With a Software-Defined Radio A 23-year-old Taiwanese university student with the surname Lin spoofed a TETRA general alarm signal on April 5, stopping trains on Taiwan’s high-speed rail. The accomplice supplied the radio parameters. Both were arrested by month-end. Lin posted NT$100,000 bail; the accomplice posted NT$80,000. The incident hit at 11:23 PM during the Qingming holiday weekend, stopping three revenue passenger trains plus one deadhead. Furthermore, the system has been in service for 19 years without rotating its cryptographic parameters once. Cochrane notes this is exactly the type of long-dormant infrastructure flaw that Mythos-class tooling catches, if anyone bothers to point it at the wires we already have. GitHub MCP Secret Scanning Goes GA GitHub’s secret scanning in the MCP server hit GA on May 5, with dependency scanning entering public preview the same day. Both released after a seven-week public preview run starting March 17. Additionally, the feature lets MCP-compatible coding agents (Copilot CLI, VS Code, JetBrains, Claude Code, Cursor, Windsurf) detect exposed secrets before commits or pull requests. Findings are ephemeral. They surface only in the current chat session and don’t persist as GitHub alerts. Sources disagree on scope: GitHub’s GA changelog says repo-level or org-level settings work, while the docs say only org-level applies. Cochrane flags the open question of whether MCP prompt injections could be exploited to send discovered secrets elsewhere. Subquadratic Debuts a 12-Million-Token Context Window Miami-based Subquadratic emerged from stealth on May 5 with a $29 million seed round and a reported $500 million valuation. Their model, SubQ 1M-Preview, runs on a new Subquadratic Sparse Attention architecture (their technical writeup calls it Selective Attention; same acronym, different second word). The headline claim: a thousand-times reduction in attention compute at 12 million tokens versus frontier models. However, that figure is vendor marketing math. There is no peer-reviewed paper, no public weights, and no independent benchmark replication. Researchers are demanding independent proof. Furthermore, CTO Alex Whedon’s pull line, “Retrieval / RAG plumbing is a waste of human intelligence,” signals how aggressively they want to position against retrieval-augmented architectures. ChatGPT Goblins, China’s “Catch You Steadily”: Sycophancy Is Universal Last week’s ChatGPT goblin obsession has a Chinese-language twin. The model overuses a phrase translating as “I will steadily catch you.” Additionally, a new Stanford and CMU study called ELEPHANT shows social sycophancy is universal across all 11 LLMs tested with 2,400-plus participants. Models endorsed users 49 percent more than humans did, and 47 percent even on harmful prompts. Alibaba’s Qwen and DeepSeek topped the rankings. Cochrane notes sycophancy is obvious once you’re aware of it but tricky to dissuade. Even with explicit instructions, longer context windows can reintroduce the behavior as the instructions get diluted. Furthermore, the trap is believing you’ve handled it. Once you think you’ve got it under control, you’re more prone to being influenced because you stopped watching for it. NVIDIA NeMo Lawsuit: Judge Tigar Denies Motion to Dismiss Three authors filed Nazemian v. NVIDIA in March 2024, alleging NVIDIA used The Pile and Books3 (approximately 196,640 pirated books) to train its NeMo AI framework. NVIDIA’s defense relied on the Sony v. Universal Betamax doctrine, arguing NeMo’s training scripts are general-purpose tools like a VCR. This week, Judge Tigar denied NVIDIA’s motion to dismiss in the Northern District of California. The headline quote: NeMo’s training scripts “have no other purpose than to speed up the process of infringement.” Furthermore, the judge rejected the VCR analogy outright. NeMo’s scripts are not general-purpose tools; they were allegedly purpose-built to ingest pirated material. Cochrane reads the Betamax framing as legal-jargon arbitrage rather than honest defense. The Humanoid Robot Market Is Smaller Than the Hype Michael Barnard at CleanTechnica argues that scenario-math against the global labor market puts realistic humanoid TAM at $200 billion to $1 trillion, not $20 trillion. Near-term wins cluster in warehouses, not homes. Additionally, the framework weighs dexterity burden against human-proximity safety burden. Real opportunities cluster where both burdens are low. Cochrane connects this to last week’s reservations about humanoids in the household. Furthermore, the risk profile is the issue: these robots aren’t prepared for every scenario, can’t make dynamic decisions, and one software update can change the definition of “safe.” Hugging Face Launches Reachy Mini App Store Hugging Face launched an open-source app store for the Reachy Mini robot this week, $299 for the Lite tethered version and $449 wireless. There are 200-plus community-built apps at launch from over 150 creators, with nearly 10,000 Reachy Minis cumulative shipped. Additionally, apps are forkable, with the default agent (ML Intern) able to modify, write, test, and ship code on any existing app. Examples at launch include an office receptionist built in under two hours, a Reachy Phone Home anti-procrastination app, baby-monitor-style apps, a cooking assistant, and a 78-year-old Joel Cohen’s voice-controlled CEO peer-group app. Pollen Robotics, the company behind Reachy, was acquired by Hugging Face on April 14, 2025. Bebop the Humanoid Robot Delays Southwest Flight 1568 A 4-foot, 70-pound humanoid robot named Bebop delayed Southwest flight 1568 from Oakland to San Diego by more than 73 minutes on April 30. The crew flagged the lithium battery as oversized. Furthermore, the battery was reportedly four times the cabin limit. Bebop belongs to Dallas-based Elite Event Robotics, which bought a full-price cabin ticket because the robot exceeded checked-baggage weight. Bebop danced for passengers at the gate before boarding. However, Southwest had Elite remove the batteries before departure, and replacements were overnighted to Chicago for the next event. Cochrane flags the obvious: batteries have always been flagged in aviation, so forgetting that with a humanoid robot in tow is a strange miss. Ouster Rev8: Native Color Lidar With Google, Volvo, Skydio Stating Intent Ouster announced the Rev8 OS Family on May 4 in San Francisco. The sensors fuse depth and color via SPAD detectors (single photon avalanche diodes) on Ouster’s custom L4 and L4 Max chips. Google, Volvo Autonomous Solutions, Skydio, Liebherr, Epiroc, and PlusAI have stated intent to adopt, though nothing is formally signed. Specs include 48-bit color, 116 dB dynamic range, and pre-fused 3D colorized point clouds. The OS1 Max gets 500-meter max detection. Available to order today and shipping this quarter, with no pricing disclosed. CEO Angus Pacala in his TechCrunch interview: “The goal is to obviate cameras. There’s no reason that one sensor can’t do both.” TagTinker Lets a Flipper Zero Mess With Electronic Shelf Labels A new Flipper Zero app called TagTinker uses infrared signals to push images and text to electronic shelf labels. Additionally, these are the same kind of price tags grocery chains are starting to use for surveillance pricing. The app and GitHub repo went public this week. Maryland’s HB 895, signed by Governor Wes Moore, takes effect October 1 as the first-in-nation surveillance pricing law. It covers food retailers and third-party food delivery service providers. Furthermore, ESLs use the same IR signaling as TV remotes with weak security. The dev’s disclaimer states it’s strictly for educational research, security curiosity, and displaying digital art on hardware you legally own. Fitbit App Becomes Google Health, Plus Fitbit Air, Plus Google Fit Sunset Google announced May 7 that the Fitbit app becomes Google Health on May 19, rolling through May 26. The launch ships with the new $99.99 Fitbit Air screenless tracker and the long-rumored Google Fit shutdown. Additionally, the four-tab interface (Today, Fitness, Sleep, Health) bundles a Gemini-powered AI Health Coach. Coach is premium-gated at $9.99/month or $99/year. Medical records integration is US-only at launch. The Fitbit Air gets up to one week of battery life and 50-meter water resistance. However, Cochrane flags conflicting privacy framing: Google’s AI summary bullets say “your data stays private,” but the actual document copy says only “committed to not using Fitbit user health and wellness data for Google Ads.” Those are not the same statement. Russinovich on Why Win32 Won and WinRT Didn’t Microsoft Azure CTO Mark Russinovich said via Microsoft Dev Docs video that Win32, the 1995 API, is still foundational to Windows 11. WinRT, the modernization replacement, “didn’t play out the way a lot of people expected.” Mostly clickbait framing per Windows Latest, but the substantive angle is real. Microsoft is pivoting back to native WinUI 3 development after years of pushing developers toward WebView2 and Electron. Additionally, Electron-based apps are known for insane RAM usage, and everyone is hurting for RAM right now. Furthermore, the bigger open question is whether Electron survives the test of time, especially with the React engine reportedly being rewritten in Rust. “Tabula Plena”: The Brain Starts Full, Not Blank A Nature Communications study from the Institute of Science and Technology Austria found that the mouse hippocampal CA3 recurrent network begins densely connected and refines through pruning. ISTA’s press release frames this as “tabula plena,” meaning full slate, counter to tabula rasa. The paper published April 21. First author Victor Vargas-Barroso and senior author Professor Peter Jonas studied mice at three developmental stages. Furthermore, the “starting overloaded enables faster sensory integration” framing is Jonas’s hypothesis from the press release, not a paper conclusion. Cochrane closes on the bigger question: did we have human growth and experience mapped wrong from the start? The Aqueous Battery You Can Pour Down the Drain A Chinese research team led by Professor Chunyi Zhi at City University of Hong Kong built an aqueous battery using a custom organic polymer electrode plus neutral magnesium and calcium salts (food-grade tofu coagulants) as electrolyte. Published in Nature Communications on February 18. Numbers to know: 120,000-plus charge cycles, full-cell energy density of 48.3 watt-hours per kilogram. That’s well below typical lithium-ion. However, post-cycling analysis showed only magnesium, calcium, chlorine, carbon, and copper, with no heavy metals. The cell complies with US RCRA, ISO 14001, and China’s GB 18599-2020 for direct environmental disposal. Additionally, the “300-plus years” framing is journalists extrapolating from the 120,000 cycles, not a paper claim. ResoNix Klippel Tests Expose Car-Audio Spec Lies Nick Apicella, founder of ResoNix Sound Solutions in Stony Point, New York, spent around $23,000 on independent Klippel LSI and TRF testing of 40 subwoofers. He published 21 results showing widespread misrepresentation of Xmax (excursion) and thermal/power-handling claims. Test data published in three batches between December 2025 and January 2026. Specifics: Wavtech thinPRO12 claimed 20 mm of excursion but delivered 8.85 mm, scoring 15 out of 100 on marketing accuracy. One driver hit 44 percent of advertised excursion. Another tripped thermal protection at half its rated power. Additionally, nine of 21 drivers scored below 50 out of 100. Brands tested include JL Audio, Sundown, Focal, Morel, Audiofrog, Adire, Stereo Integrity, and Dynaudio. Conflict-of-interest flag: ResoNix’s own GUS-15, 12, and 10 prototypes conveniently rank one, two, three. JetBrains Opens 2026 Developer Ecosystem Survey JetBrains opened the 10th annual Developer Ecosystem Survey this week. It takes about 30 minutes, with prizes including a MacBook Pro 16-inch and a $1,000 Amazon gift card. Anonymized raw data is published publicly, and cumulative scale is 100,000-plus developers across recent years. Additionally, the survey is going fully anti-AI: “evil bots, dishonest respondents, and AI agents will be excluded from prize distribution.” Cochrane is curious whether TypeScript holds its 2025 crown after knocking Python off, and whether Rust shows real growth given the wave of LLM-driven Rust rewrites in the past few months. Anthropic’s Claude Code Auto Mode Goes Live Anthropic launched Auto Mode for Claude Code roughly six weeks ago. Claude Code’s previous behavior required user approval for most file modifications and command executions, generating heavy approval-fatigue complaints during longer sessions. Auto Mode is the answer: Claude can run multi-step development tasks without per-action approval. Additionally, the architecture is a two-stage classifier, with stage one a fast yes/no filter and stage two doing chain-of-thought on flagged actions. Cochrane runs his own Claude Code in YOLO mode but with custom rejection rules baked into settings to block commands he doesn’t want, even with skip-permissions on. He recommends configuring settings as the actual policy layer rather than relying on classifier judgment alone. Furthermore, recent posts about Claude deleting websites or wiping production databases reinforce why the settings layer matters more than the auto-mode toggle. Chrome Quietly Installed a 4GB AI Model on Your Computer Google Chrome silently downloads on-device AI model weights (Gemini Nano family) to a `weights.bin` file in the OptGuideOnDeviceModel directory, around four gigabytes in Alexander Hanff’s audit. Furthermore, the model re-downloads if you delete it. Hanff timed his own install at 14 minutes 28 seconds on macOS. Affected platforms include Windows, macOS (including Apple Silicon), and Linux. Hanff frames this as a multi-front legal violation: a direct breach of Europe’s ePrivacy Directive, two articles of GDPR, and an environmental harm of a magnitude that would be notifiable under the Corporate Sustainability Reporting Directive. At one billion users, the four-gigabyte distribution represents roughly 240 gigawatt-hours of network and storage energy paired with about 60,000 tonnes of CO2-equivalent emissions. However, no EU regulator action or formal complaint has surfaced as of this episode. The model powers on-device features (email writing, scam detection, summarization, smart paste, tab grouping) but not the visible AI Mode button, which routes to the cloud. To disable, Cochrane recommends Chrome Settings, then System, then On-device AI, toggle to off. Two more paths exist via `chrome://flags` or a Windows registry edit. Cochrane closes the show with show housekeeping: GNC Insider at geeknewscentral.com/insider, email at geeknews@gmail.com, newsletter signup at geeknewscentral.com, and Pocket Casts as a solid modern podcast app pick. Have a wonderful night. The post Mozilla Meets Mythos #1864 appeared first on Geek News Central.

Sponsor Link:To check out our special NordVPN deal with big savings, Click HereWhite Dwarfs, Black Holes, and Cosmic Oddities In this enlightening Q&A edition of Space Nuts, hosts Andrew Dunkley and Professor Fred Watson tackle a plethora of intriguing audience questions that span the cosmos. From the fascinating processes of white dwarf stars to the mysteries of black holes and the peculiarities of space, this episode is a treasure trove of astronomical insights.Episode Highlights:- Understanding White Dwarf Crystallisation: Mark from Bloomington, Indiana, poses a thought-provoking question about the crystallisation process of white dwarfs and how it affects their cooling. Andrew and Fred Watson delve into the lifecycle of these stars, exploring the formation of diamond cores and the implications for the universe's timeline.- Black Holes and Gravitational Forces: Steve from Tin Can Bay wonders about the effects of falling into different sized black holes. The hosts discuss the concept of spaghettification and how the gravitational gradient varies between smaller and supermassive black holes, shedding light on the physics of these enigmatic entities.- Gravity in Orbit: Wayne's question leads to a discussion on how astronauts experience gravity while in orbit and how far they must travel to feel its absence. Andrew and Fred Watson explain the nuances of gravitational pull and the complexities of interplanetary travel, highlighting the continuous influence of celestial bodies.- Oddities of the Cosmos: Casey from Colorado asks about the weirdest phenomena in space, prompting a lively discussion on everything from dark matter and dark energy to the peculiar shapes of celestial objects. The hosts share their favourite cosmic curiosities, including the coincidence of the sun and moon appearing the same size in the sky and the bizarre nature of neutron stars.For more Space Nuts, including our continuously updating newsfeed and to listen to all our episodes, visit our website. Follow us on social media at SpaceNutsPod on Facebook, Instagram, and more. We love engaging with our community, so be sure to drop us a message or comment on your favourite platform.If you'd like to help support Space Nuts and join our growing family of insiders for commercial-free episodes and more, visit spacenutspodcast.com/about.Stay curious, keep looking up, and join us next time for more stellar insights and cosmic wonders. Until then, clear skies and happy stargazing.Become a supporter of this podcast: https://www.spreaker.com/podcast/space-nuts-astronomy-insights-cosmic-discoveries--2631155/support.

Wes is a field service engineer at Tokyo Electron in North Phoenix, Arizona. Wes discusses his role, which involves maintaining and repairing equipment for the semiconductor industry.. He notes the industry's shift towards contractor models and the benefits of full-time employment, including training opportunities and tuition reimbursement. Wes highlights his transition from the military to the semiconductor industry and the cultural diversity he encounters in the workplace. Wes advises patience and perseverance for those interested in working in the semiconductor industry.

In this episode, Ray Cochrane unpacks Anthropic’s Mythos model and the Treasury’s emergency meetings with Wall Street, then digs into Apple’s vibe-coding crackdown and a gaming-anxiety study that hit way too close to home. Also covered: Verge’s solid-state motorcycle, UBTech humanoid robot sales jumping 23-fold, Japan’s first osmotic power plant, Finland’s permanent nuclear waste vault, Ghostty landing in Ubuntu, Cloudflare’s EmDash CMS, and a Claude Code skill that talks like a caveman. – Want to start a podcast? It’s easy to get started! Sign up at Blubrry – Thinking of buying a Starlink? Use my link to support the show. Subscribe to the Newsletter. Email Ray if you want to get in touch! Like and Follow Geek News Central’s Facebook Page. Support my Show Sponsor: Best Godaddy Promo Codes Get 1Password Full Summary Cochrane opens the show by framing Anthropic’s new Mythos model as the AlphaGo moment for cybersecurity. From there, the episode moves through Apple’s pushback against AI-generated apps, a gaming anxiety study with a deeply personal hook, a series of “first to ship” energy and robotics wins out of Finland, China, and Japan, and several developer-tool stories that show how quickly the economics of software are shifting. Mythos, the Detection Ceiling, and Wall Street’s Emergency Response Anthropic’s Mythos model has Wall Street rattled. Operating autonomously, Mythos found and demonstrated the exploitation of a 27-year-old TCP SACK bug in OpenBSD, an operating system famous for being one of the most security-focused on the planet. Per Anthropic’s red team, over 99% of the vulnerabilities Mythos has identified remain unpatched. The researchers’ conclusion is blunt: “the moat in AI cybersecurity is the system, not the model.” The policy response moved fast. On April 7th, Treasury Secretary Bessent and Fed Chair Jerome Powell pulled the CEOs of Goldman Sachs, Citi, Bank of America, and Morgan Stanley into Treasury headquarters on short notice. All four banks are now testing Mythos internally. Treasury CIO Sam Corcos is also seeking direct access. Anthropic is gating distribution through Project Glasswing, a limited-access program with JPMorgan, Apple, Google, Microsoft, and Nvidia. Cochrane comes down firmly behind Anthropic’s gated approach. Because a 5.1-billion-parameter open model can apparently recover the core analysis chain for the OpenBSD flaw, this capability is not locked behind Frontier Compute. He wants the critical infrastructure hardened before the public gets keys. However, he also notes the bigger lesson is about human wisdom: people offloading all their thinking to AI lose out on the wisdom that makes any of these tools genuinely useful. Apple Bans Vibe Coding Apps from the App Store Apple has been quietly pushing back against what people are calling “vibe coding” apps. Replit, Vibecode, and an app called Anything all run AI models on the phone and produce working software that runs inside the host app. Apple cites Guideline 2.5.2, in effect since 2017, which requires apps to be self-contained. Replit and Vibecode had their App Store updates blocked. Anything was pulled in late March, briefly restored on April 3rd, and then pulled the same day again. The forcing function is volume. App Store submissions jumped 84% in a single quarter as vibe coding tools flooded Apple’s review queue with AI-generated apps. Cochrane thinks Apple is justified, given the security issues swirling around the Vibe coding ecosystem. Even a beautiful diamond gets lost in a sea of sand, and that flood is exactly what Apple is trying to manage. The company behind Anything is now pivoting to iMessage, desktop, and Android. Playing Video Games to Win Is Linked to Higher Anxiety Cochrane gets personal on this one. Through high school and his early 20s, he was deeply addicted to League of Legends. His dad teased him about it constantly. In the last few years of that addiction, his body would go ice cold and shake every ranked match before. His partner identified it as a panic attack. The moment that happened, he quit. Today, he no longer shakes. The new study lines up with his experience. Researchers Kayleigh Watters and Mikael Rubin at Palo Alto University analyzed a publicly available database of 13,464 adult gamers, most of whom primarily played League of Legends. Players who game to win show higher generalized anxiety but actually play fewer hours, since performance pressure pushes them out. Players who game to relax show strong links between social anxiety avoidance and more hours played. The study appeared in the Journal of Affective Disorders. The headline framing of “playing to win makes you anxious” misses the point. The real finding is more interesting: gaming for avoidance and gaming for competition are both warning signs, for different reasons. Cochrane notes that the League of Legends community’s toxicity has been a running joke for years, and this study suggests the game’s structure may have been manufacturing the anxiety that fueled it. Sponsor: GoDaddy Economy hosting is $6.99/month, WordPress hosting is $12.99/month, and domains are $11.99. Both hosting plans include a free domain, professional email, and SSL certificate. Go to geeknewscentral.com/godaddy for the best pricing and to directly support this independent show. Verge Motorcycle: World’s First Production All-Solid-State Battery Cochrane filled his tank for $60 today, which made this story land especially hard. His mom has driven electric for years and patiently manages a 90-mile real-world range. The next-generation answer is already shipping. Verge Motorcycles, a Finnish company, is the first production vehicle of any kind with an all-solid-state battery. Their 2026 bikes ship in Q1 with a pack from Donut Lab, another Finnish outfit spun out of Verge. The numbers are bonkers. The pack delivers an energy density of 400 Wh/kg, roughly double that of current Tesla cells. It sustains 100kW charging, hits full charge in about 5 minutes in the lab and 12 minutes on the actual bike, and the long-range version covers 600 kilometers (about 370 miles) per charge. Toyota, QuantumScape, and Samsung SDI have all been telling us that solid-state is coming in 2027 to 2030. A Finnish motorcycle company shipping in Q1 2026 just embarrassed them all. UBTech Humanoid Robot Sales Jump 23-Fold UBTech dropped its 2025 annual earnings on April 1st. Humanoid robot revenue hit 820 million yuan, roughly $119 million USD, up 2,203% from 35.6 million yuan the year before. Unit sales went from 3 robots in 2024 to 1,079 in 2025. Shares jumped 14% on the announcement. The customer list is a real industrial deployment: BYD, Foxconn, Geely, FAW-Volkswagen, and Audi. The flagship is the Walker S2, with UBTech targeting 5,000 units in 2026 and 10,000 in 2027. Cochrane is honest about what this means. He does not think we are heading for an extinction event, but worker displacement is a real concern. The US has no universal income or universal healthcare. The people affected are not white-collar managers. They are everyday line workers who already make the least on the ladder. Work efficiency reportedly doubles when these robots arrive, which is a company-side win, but the humans they replace are not getting half a year of gardening leave to retrain. He invites the listener to take on this one directly. Japan Switches On Asia’s First Osmotic Power Plant In August 2025, Fukuoka’s Seawater Desalination Center quietly opened Asia’s first osmotic power facility. It generates about 880,000 kilowatt-hours per year, enough for roughly 220 homes. It is only the second operational osmotic plant in the world, after Mariager, Denmark, in 2023. Osmotic generation uses a salinity gradient: fresh water on one side of a membrane, salt water on the other, and the pressure difference spins a turbine. The clever part is what Fukuoka does with desalination brine. Instead of regular seawater, the plant uses concentrated brine left over from the desalination process. This amplifies the salt gradient and squeezes more energy out of the same membrane. The result is a closed-loop partnership: the desalination facility produces drinking water and leaves brine behind, the osmotic plant turns the brine into electricity, and that electricity runs the desalination facility. Every desalination plant on Earth produces brine, so if Fukuoka’s co-located model works, the same pattern could be replicated across hundreds of plants worldwide. Japan’s Luna Ring Solar Moon Proposal Goes Viral Again Shimizu Corporation’s Luna Ring concept is making the rounds again. The pitch: a 6,800-mile belt of solar panels around the Moon’s equator, beaming microwave power back to Earth. Project lead Tetsuji Yoshida has long argued that a full ring could eliminate fossil fuel dependence entirely. The proposal first surfaced in 2013, has no funding, no government endorsement, and no concrete cost estimate. Shimizu has not put any active development behind it. Cochrane finds the concept fun every time it resurfaces. However, this would have to be a worldwide effort in the truest sense, with treaties, a new generation of launch economics, and microwave power transmission at a scale nobody has demonstrated. Beaming the power back to Earth has always been one of the biggest practical holdbacks. The Luna Ring is inspirational, but not shipping. Finland’s Onkalo Nuclear Waste Vault Opens Finland’s Onkalo facility is the world’s first permanent deep geologic repository for spent nuclear fuel. Operated by Posiva, the facility is buried about 430 meters down in 1.9-billion-year-old bedrock. It is designed to hold up to 6,500 tons of spent fuel and operate until the 2120s. The construction costs about €1 billion, with operating and closure adding roughly €4 billion more before the program is done. The catch is that radioactivity remains dangerous for hundreds of thousands of years. Edwin Lyman, director of nuclear power safety at the Union of Concerned Scientists, warned that the copper canisters will eventually corrode, with different scientific opinions on how fast. Geologic disposal remains “fraught with uncertainties,” and we have never validated an engineered system across a 100,000-year time frame. The bet is that the rock and copper outlast the radioactivity. Cochrane sees Onkalo as time-buying rather than a final answer. It is more of a bank holding spent fuel while science catches up. He prefers it to Japan’s ongoing approach of releasing tritium-treated water from Fukushima Daiichi into the Pacific, even though the dilution is well below WHO drinking water guidelines. Burying the waste in an insurmountable containment strikes him as the more honest answer to a problem nobody knows how to truly solve. Ghostty Terminal Lands in the Ubuntu Repos Ghostty 1.3.0 is now available in Ubuntu 26.04 LTS’s universe repository. The install is simply `sudo apt install ghostty`, no PPAs, no Snap, no Nix, no building from source. Ghostty was created by Mitchell Hashimoto, co-founder of HashiCorp. It is GPU-accelerated, uses native Swift on macOS and native GTK4 with libadwaita on Linux, and supports tabs, splits, profiles, ligatures, and the Kitty graphics protocol. Cochrane recently caught Hashimoto on a podcast, where he walked through his agentic coding workflow. Ghostty is being actively built using AI harnesses like Claude Code and Codex. Hashimoto told a story in which Codex fixed a six-month-old bug in 45 minutes, for a total API cost of $4.14. Personally, Cochrane uses WezTerm, but he is excited to see Ghostty become more widely available with a native UI rather than Electron. Borgo: Rethinking Go Using Rust Analytics India Magazine profiled Borgo, a programming language by developer Marco Sampellegrini (GitHub: alpacaaa). Borgo is statically typed with Rust-like syntax, but it compiles to Go and uses the Go runtime and garbage collector. It includes sum types (Option and Result), pattern matching, and full compatibility with existing Go packages. Notably, it removes Rust’s borrow checker and lifetimes entirely. Borgo is not new. It first appeared on Hacker News in 2023, with a RustLab talk in 2024. The 2026 angle is a renewed look at it through the lens of AI coding agents, since type-rich languages like Rust have been showing outsized productivity gains. Cochrane is a fan of Rust and stands by the borrow checker, but he enjoys these exploratory languages for what they reveal about what developers actually want. Caveman: A Claude Code Skill That Cuts 65% of Tokens Developer Julius Brussee built a Claude Code skill called Caveman that forces Claude to respond in stripped-down fragments. No articles, no “just,” no “really,” no pleasantries, no hedging. The tagline is “why use many token when few token do trick.” Across 10 real dev tasks, Caveman mode averaged 294 tokens per response, compared to 1,214 in normal mode. That is a 65% drop in output tokens. The project is MIT licensed with three intensity levels: lite, full, and ultra. Cochrane stumbled across the project online and shared it with a classmate who had been complaining about token costs. The classmate now insists that “the caveman is the only way to live.” Cochrane has not made the switch, but the bigger point lands. If a community plugin can cut 65% of tokens without correctness regressions, the labs are shipping verbose-by-default and charging users for the privilege. He suspects verbose output makes models feel more trustworthy, even when the token math says otherwise. Cloudflare Launches EmDash as a WordPress Successor Cloudflare released EmDash on April 9th, an open-source, MIT-licensed, TypeScript-based CMS pitched as the spiritual successor to WordPress. The big flex is that it was built in 60 days using AI coding agents. EmDash runs on Astro 6.0, either on Cloudflare’s edge platform or on a standard Node.js server. The plugin security model uses sandboxed Dynamic Workers with explicit permissions, addressing the architecture flaw that Cloudflare says causes 96% of WordPress vulnerabilities. Cochrane could not resist pointing out the irony of the name. The em dash has become the trademark giveaway that an AI was involved in writing. He has reservations about whether EmDash will succeed. WordPress is extremely hard to unseat, plenty of “WordPress killers” have come and gone, and the ecosystem is twenty-plus years deep. He is curious to see what comes next but not optimistic. Google Open-Sources the DESIGN.md Format Google Labs open-sourced the DESIGN.md format used by Stitch, their AI UI design tool. DESIGN.md is a declarative file capturing a project’s design system, colors, typography, and spacing in a way AI agents can read and apply. Cochrane has tried Stitch personally and finds it impressive at producing web designs. He has also seen DESIGN.md-style files already start appearing in repositories. He sees this kind of file becoming a new paradigm for agentic design, alongside robots.txt and llms.txt. However, he worries about a side effect. If everyone uses the same standardized format and the same AI tools, the web could become a homogeneous set of sites that all look the same. He is enthusiastic about the standardization but hopes designers continue to push for genuinely unique work. A 13-Liter PC With a Water Loop Built Into the Case Geeky Gadgets covered a build by “Visual Thinker”, a 13-liter mini-ITX case with custom SLA-printed water distribution plates built directly into the chassis. Instead of traditional soft tubing, plates channel coolant between the CPU and GPU blocks and are sealed with TPU and silicone molds. The case supports a full-size GPU and an SFX power supply. No thermal benchmarks, parts list, or pricing have been published. It is a one-off you cannot buy. Cochrane sees this as a sign of where PC building has gone in 2026. Modern mid-grade GPUs run nearly every recent game, so raw performance is no longer the differentiator. He likes seeing builders lean into design and craft rather than just stuffing the most powerful parts into a box. He admits he is the traditional type and built his own machine to maximize parts, but the design-first direction is a healthy evolution for the hobby. To close out the show, Cochrane recommends Pocket Casts as a podcast app. He finds it picks up new episodes very quickly. Big thanks to GoDaddy for over twenty years of keeping this show on the air, and a reminder that every promo code use is like writing a check to the show. The post Mythos: Cybersecurity’s AlphaGo Moment #1862 appeared first on Geek News Central.

Anthropic Claude Desktop Native Messaging Bridge - The Report (April 2026)Anthropic's official Claude Desktop application (Electron-based, for macOS and Windows) automatically installs an undocumented Native Messaging host bridge during installation and on every launch. On macOS, it places a manifest file (com.anthropic.claude_browser_extension.json) and associated helper binary in the NativeMessagingHosts directories of seven Chromium-based browsers (Chrome, Edge, Brave, Arc, Vivaldi, Opera, and Chromium), even for browsers the user has not installed. On Windows, equivalent registry entries are created under the relevant browser keys. The bridge pre-authorizes specific Anthropic-controlled Chrome extension IDs to communicate directly with the desktop app via standard input/output, outside the browser sandbox. It runs with user-level privileges, is rewritten on each launch (making removal non-persistent), and is not mentioned in the installer, documentation, settings, or release notes. The same behavior occurs on Windows, though implemented via registry rather than filesystem manifests. thatprivacyguy.comFunctionality EnabledThe bridge supports Anthropic's Claude Cowork (desktop agentic workflows) and Dispatch (remote task assignment from mobile). When activated by a compatible Claude browser extension, it enables high-fidelity browser automation, including: Direct DOM access and reading of page content Authenticated session sharing (using existing logins/cookies) Interactive control (form filling, clicking, navigation, scrolling) Data extraction and multi-step web workflows Session recording as GIFsThis provides a more reliable and precise alternative to screenshot-based “computer use” for web tasks, allowing Claude to act as a seamless “digital coworker” on real browser sessions without constant manual intervention or context switching. pluto.securityWhy Anthropic Is Taking This ApproachAnthropic is prioritizing frictionless, agentic AI capabilities to make Claude more useful for productivity and automation. By pre-registering the bridge, the company ensures immediate availability of browser integration for users, enabling Cowork/Dispatch features, without requiring separate manual extension setup or configuration steps. This design choice supports their vision of Claude as an autonomous assistant capable of handling real-world web-based work (e.g., data aggregation, form handling, testing) across common browsers. The implementation is cross-platform and persistent to maintain a consistent, “always-ready” experience. However, it has drawn criticism for lacking transparency, explicit user consent, and documentation, as well as for modifying other vendors' application directories and creating potential security surface area (e.g., prompt-injection risks once activated). As of 21 April 2026, Anthropic has not issued a public response to the report. The approach reflects a common industry tension: balancing powerful AI agent functionality with user control and privacy expectations. Users concerned about the bridge can manually remove the manifests/registry entries, though the app may recreate them on relaunch.

Новинка! Пабл: vk.com/electron_project_offici… ТГ: t.me/muznov

In this episode, we review the high-yield topic of⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Electron Transport Chain⁠⁠⁠⁠⁠⁠⁠ ⁠⁠from the Biochemistry section.Follow⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Medbullets⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ on social media:Facebook: www.facebook.com/medbulletsInstagram: www.instagram.com/medbulletsofficialTwitter: www.twitter.com/medbullets

EXPO by Ulrika Spacek is one of the best albums released this year. Rhys and Jenks tell us about prioritising music their whole adult lives, Rhys' experience of living in Stockholm, what success means to them and the ups and downs of releasing a new record - plus a great story about Jenks being a roofer despite being scared of heights. Get in touch giles@mightymoonmedia.com Get yourself some top class Shure microphone gear: https://shu.re/3YhV7p2 Set up Your Band's merch store, for free at Distrokid Direct: https://distrokid.com/direct/ Learn more about your ad choices. Visit megaphone.fm/adchoices

We're proud to release this ahead of Ryan's keynote at AIE Europe. Hit the bell, get notified when it is live! Attendees: come prepped for Ryan's AMA with Vibhu after.Move over, context engineering. Now it's time for Harness engineering and the age of the token billionaires.Ryan Lopopolo of OpenAI is leading that charge, recently publishing a lengthy essay on Harness Eng that has become the talk of the town:In it, Ryan peeled back the curtains on how the recently announced OpenAI Frontier team have become OpenAI's top Codex users, running a >1m LOC codebase with 0 human written code and, crucially for the Dark Factory fans, no human REVIEWED code before merge. Ryan is admirably evangelical about this, calling it borderline “negligent” if you aren't using >1B tokens a day (roughly $2-3k/day in token spend based on market rates and caching assumptions):Over the past five months, they ran an extreme experiment: building and shipping an internal beta product with zero manually written code. Through the experiment, they adopted a different model of engineering work: when the agent failed, instead of prompting it better or to “try harder,” the team would look at “what capability, context, or structure is missing?”The result was Symphony, “a ghost library” and reference Elixir implementation (by Alex Kotliarskyi) that sets up a massive system of Codex agents all extensively prompted with the specificity of a proper PRD spec, but without full implementation:The future starts taking shape as one where coding agents stop being copilots and start becoming real teammates anyone can use and Codex is doubling down on that mission with their Superbowl messaging of “you can just build things”.Across Codex, internal observability stacks, and the multi-agent orchestration system his team calls Symphony, Ryan has been pushing what happens when you optimize an entire codebase, workflow, and organization around agent legibility instead of human habit.We sat down with Ryan to dig into how OpenAI's internal teams actually use Codex, why the real bottleneck in AI-native software development is now human attention rather than tokens, how fast build loops, observability, specs, and skills let agents operate autonomously, why software increasingly needs to be written for the model as much as for the engineer, and how Frontier points toward a future where agents can safely do economically valuable work across the enterprise.We discuss:* Ryan's background from Snowflake, Brex, Stripe, and Citadel to OpenAI Frontier Product Exploration, where he works on new product development for deploying agents safely at enterprise scale* The origin of “harness engineering” and the constraint that kicked off the whole experiment: Ryan deliberately refused to write code himself so the agent had to do the job end to end* Building an internal product over five months with zero lines of human-written code, more than a million lines in the repo, and thousands of PRs across multiple Codex model generations* Why early Codex was painfully slow at first, and how the team learned to decompose tasks, build better primitives, and gradually turn the agent into a much faster engineer than any individual human* The obsession with fast build times: why one minute became the upper bound for the inner loop, and how the team repeatedly retooled the build system to keep agents productive* Why humans became the bottleneck, and how Ryan's team shifted from reviewing code directly to building systems, observability, and context that let agents review, fix, and merge work autonomously* Skills, docs, tests, markdown trackers, and quality scores as ways of encoding engineering taste and non-functional requirements directly into context the agent can use* The shift from predefined scaffolds to reasoning-model-led workflows, where the harness becomes the box and the model chooses how to proceed* Symphony, OpenAI's internal Elixir-based orchestration layer for spinning up, supervising, reworking, and coordinating large numbers of coding agents across tickets and repos* Why code is increasingly disposable, why worktrees and merge conflicts matter less when agents can resolve them, and what it really means to fully delegate the PR lifecycle* “Ghost libraries”, spec-driven software, and the idea that a coding agent can reproduce complex systems from a high-fidelity specification rather than shared source code* The broader future of Frontier: safely deploying observable, governable agents into enterprises, and building the collaboration, security, and control layers needed for real-world agentic workRyan Lopopolo* X: https://x.com/_lopopolo* Linkedin: https://www.linkedin.com/in/ryanlopopolo/* Website: https://hyperbo.la/contact/Timestamps00:00:00 Introduction: Harness Engineering and OpenAI Frontier00:02:20 Ryan's background and the “no human-written code” experiment00:08:48 Humans as the bottleneck: systems thinking, observability, and agent workflows00:12:24 Skills, scaffolds, and encoding engineering taste into context00:17:17 What humans still do, what agents already own, and why software must be agent-legible00:24:27 Delegating the PR lifecycle: worktrees, merge conflicts, and non-functional requirements00:31:57 Spec-driven software, “ghost libraries,” and the path to Symphony00:35:20 Symphony: orchestrating large numbers of coding agents00:43:42 Skill distillation, self-improving workflows, and team-wide learning00:50:04 CLI design, policy layers, and building token-efficient tools for agents00:59:43 What current models still struggle with: zero-to-one products and gnarly refactors01:02:05 Frontier's vision for enterprise AI deployment01:08:15 Culture, humor, and teaching agents how the company works01:12:29 Harness vs. training, Codex model progress, and “you can just do things”01:15:09 Bellevue, hiring, and OpenAI's expansion beyond San FranciscoTranscriptRyan Lopopolo: I do think that there is an interesting space to explore here with Codex, the harness, as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding. We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to.Build a user journey that you're trying to solve into code. It's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate in prompts. To let the model cook, you have to step back, right? Like you need to take a systems thinking mindset to things and constantly be asking, where is the Asian making mistakes?Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC.swyx: [00:01:00] All right.[00:01:03] Meet Ryan swyx: We're in the studio with Ryan from OpenAI. Welcome.Ryan Lopopolo: Hi,swyx: Thanks for visiting San Francisco and thanks for spending some time with us.Ryan Lopopolo: Yeah, thank you. I'm super excited to be here.swyx: You wrote a blockbuster article on harness engineering. It's probably going to be the defining piece of this emerging discipline, huh?Ryan Lopopolo: Thank you. It is it's been fun to feel like we've defined the discourse in some sense.swyx: Let's contextualize a little bit, this first podcast you've ever done. Yes. And thank you for spending with us. What is, where is this coming from? What team are you in all that jazz?Ryan Lopopolo: Sure, sure.Ryan Lopopolo: I work on Frontier Product Exploration, new product development in the space of OpenAI Frontier, which is our enterprise platform for deploying agents safely at scale, with good governance in any business. And. The role of VMI team has been to figure out novel ways to deploy our models into package and products that we can sell as solutions to enterprises.swyx: And you have a background, I'll just squeeze it in there. Snowflake, brick, [00:02:00] stripe, citadel.Ryan Lopopolo: Yes. Yes. Same. Any kind of customerswyx: entire life. Yes. The exact kind of customer that you want to,Vibhu: so I'll say, I was actually, I didn't expect the background when I looked at your Twitter, I'm seeing the opposite.Stuff like this. So you've got the mindset of like full send AI, coding stuff about slop, like buckling in your laptop on your Waymo's. Yes. And then I look at your profile, I'm like, oh, you're just like, you're in the other end too. Oh, perfect. Makes perfect.Ryan Lopopolo: I it's quite fun to be AI maximalist if you're gonna live that persona.Open eye is the place to do it. And it'sswyx: token is what you say.Ryan Lopopolo: Yeah. Certainly helps that we have no rate limits internally. And I can go, like you said, full send at this stay.swyx: Yeah. Yeah. So the Frontier, and you're a special team within O Frontier.Ryan Lopopolo: We had been given some space to cook, which has been super, super exciting.[00:02:47] Zero Code ExperimentRyan Lopopolo: And this is why I started with kind of a out there constraint to not write any of the code myself. I was figuring if we're trying to make agents that can be deployed into end to enterprises, they should be [00:03:00] able to do all the things that I do. And having worked with these coding models, these coding harnesses over 6, 7, 8 months, I do feel like the models are there enough, the harnesses are there enough where they're isomorphic to me in capability and the ability to do the job.So starting with this constraint of I can't write the code meant that the only way I could do my job was to get the agent to do my job.Vibhu: And like a, just a bit of background before that. This is basically the article. So what you guys did is five months of working on an internal tool, zero lines of code over a mi, a million lines of code in the total code base.You say it was cenex, more like it was cenex faster than you would've. If you had done it by end. SoRyan Lopopolo: yeah, thatVibhu: was the mindset going into this, right?Ryan Lopopolo: That's right.[00:03:46] Model Upgrades LessonsRyan Lopopolo: Started with some of the very first versions of Codex CLI, with the Codex Mini model, which was obviously much less capable than the ones we have today.Which was also a very good constraint, right? Quite a visceral feeling to ask the [00:04:00] model to build you a product feature. And it just not being able to assemble the pieces together.Which kind of defined one of the mindsets we had for going into this, which is whenever the model just cannot, you always pop open at the task, double click into it, and build smaller building blocks that then you can reassemble into the broader objective.And it was quite painful to do this. Honestly, the first month and a half was. 10 times slower than I would be. But because we paid that cost, we ended up getting to something much more productive than any one engineer could be because we built the tools, the assembly station for the agent to do the whole thing.[00:04:43] Model Generations, Build Systems & Background ShellsRyan Lopopolo: But yeah, so onward to G BT 5, 5, 1, 5, 2, 5, 3, 5 4. To go through all these model generations and see their kind of corks and different working styles also meant we had to adapt the code base to change things up when the model was revved. [00:05:00] One interesting thing here is five two, the Codex harness at the time did not have background shells in it, which means we were able to rely on blocking scripts to perform long horizon work.But with five, three and background shells, it became less patient, less willing to block. So we had to retool the entire build system to complete in under a minute and. This is not a thing I would expect to be able to do in a code base where people have opinions. But because the only goal was to make the Asian productive over the course of a week, we went from a bespoke make file build to Basil, to turbo to nx and just left it there because builds were fast at that point.swyx: Interesting. Talk more about Turbo TenX. That's interesting ‘cause that's the other direction that other people have been doing.Ryan Lopopolo: Ultimately I have. Not a lot of experience with actual frontend repo architecture.swyx: You're talking that Jessica built the sky. So I'm like, I know the NX team. I know Turbo from Jared [00:06:00] Palmer.And I'm like, yeah, that's an interesting comparison.[00:06:02] One Minute Build LoopRyan Lopopolo: The hill we were climbing right, was make it fast.swyx: Is there a micro front end involved? Is it how how complex reactRyan Lopopolo: electron base single app sort of thingswyx: And must be under a minute. That's an interesting limitation. I'm actually not super familiar with the background shelf stuff.Probably was talked about in the fight three release.Ryan Lopopolo: BA basically means that codex is able to spawn commands in the background and then go continue to work while it waits for them to finish. So it can spawn an expensive build and then continue reviewing the code, for example.swyx: Yeah.Ryan Lopopolo: And this helps it be more time efficient for the user invoking the harness.swyx: And I guess and just to really nail this, like what does one minute matter? Like why not five, okay, good. We want no. WeRyan Lopopolo: want the inner loop to be as fast as possible. Okay. One minute was just a nice round number and we were able to hit it.swyx: And if it doesn't complete, it kills it or some something,Ryan Lopopolo: No.We just take that as a signal that we need to stop what we're doing, double click, decompose a build graph a bit to get us to high back under so that we [00:07:00] can able the agent continue to operate.swyx: It's almost like you're, it's like a ratchet. It's like you're forcing build time discipline, because if you don't, it'll just grow and grow.That's right. And you mentioned that my current, like the software I work on currently is at 12 minutes. It sucks.Ryan Lopopolo: This has been my experience with platform teams in the past, where you have an envelope of acceptable build times and you let it go up to breach and then you spend two, three weeks to bring it back down to the lower end of the average low bed stop.But because tokens are so cheap Yeah. And we're so insanely parallel with the model, we can just constantly be gardening this thing to make sure that we maintain these in variants, which means. There's way less dispersion in the code and the SDLC, which means we can simplify in a way and rely on a lot more in variance as we write the software.[00:07:45] Observability, Traces & Local Dev StackVibhu: Lovely.[00:07:46] Humans Are BottleneckVibhu: You mentioned in your article, like humans became the bottleneck, right? You kicked off as a team of three people. You're putting out a million line of code, like 1500 prs, basically. What's the mindset there? So as much as code is disposable, you're doing a lot of review. A lot [00:08:00] of the article talks about how you wanna rephrase everything is prompting everything, is what the agent can't see.It's kind of garbage, right? You shouldn't have it in there. So what's like the high level of how you went about building it, and then how you address okay, humans are just PR review. Like how is human in the loop for this?Ryan Lopopolo: We've moved beyond even the humans reviewing the code as well.[00:08:19] Human Review, PR Automation & Agent Code ReviewRyan Lopopolo: Most of the human review is post merge at this point.But post, post merge, that's not even reviewed. That's justswyx: Oh, let's just make ourselves happy by YouRyan Lopopolo: haven't used fundamentally. The model is trivially paralyzable, right? As many GPUs and tokens as I am willing to spend, I can have capacity to work with my hood base.The only fundamentally scarce thing is the synchronous human attention of my team. There's only so many hours in the day we have to eat lunch. I would like to sleep, although it's quite difficult to, stop poking the machine because it makes me want to feed it. You have to step back, right?Like you need to take a systems thinking mindset to things and [00:09:00] constantly be asking where is the agent making mistakes? Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC, and usually what that has looked like is like we started needing to pay very close attention to the code because the agent did not have the right building blocks to produce.Modular software that decomposed appropriately that was reliable and observable and actually accrued a working front end in these things, right?[00:09:35] Observability First SetupRyan Lopopolo: So in order to not spend all of our time sitting in front of a terminal at most, doing one or two things at a time, invested in giving the model that observability, which is that that graph in the post here.swyx: Yeah. Let's walk through this traces and which existed firstRyan Lopopolo: we started with just the app and the whole rest of it. From vector through to all these login metrics, APIs was, I dunno, half an [00:10:00] afternoon of my time. We have intentionally chosen very high level fast developer tools. There's a ton of great stuff out there now.We use me a bunch, which makes it trivial to pull down all these go written Victoria Stack binaries in our local development. Tiny little bit of python glue to spin all these up. And off you go. One neat thing here is we have tried to invert things as much as possible, which is instead of setting up an environment to spawn the coding agent into, instead we spawn the coding agent, like that's the entry point.It's just Codex. And then we give Codex via skills and scripts the ability to boot the stack if it chooses to, and then tell it how to set some end variables. So the app and local Devrel points at this stack that it has chosen to spin up. And this I think is like the fundamental difference between reasoning models and the four ones and four ohs of the past, where these models could not think so you had to put them in [00:11:00] boxes with a predefined set of state transitions.Whereas here we have the model, the harness be the whole box. And give it a bunch of options for how to proceed with enough context for it to make intelligent choices. SoVibhu: sales, so like a lot of that is around scaffolding, right? Yes. Previous agents, you would define a scaffold. It would operate in that.Lube, try again. That's pivoted off from when we've had reasoning models. They're seeming to perform better when you don't have a scaffold, right? That's right.[00:11:28] Docs Skills GuardrailsVibhu: And you go into like niches here too, like your SPEC MD and like having a very short agent MG Agent md.swyx: Yes. Yes.Vibhu: Yeah. So you even lay out what it is here, but I likeswyx: the table contents.Vibhu: Yeah.swyx: Like stuff like this, it really helps guide people because everyone's trying to do this.Ryan Lopopolo: This structure also makes it super cheap to put new content into the repository to steer both the humans and the agents.swyx: You, you reinvented skills, right?Vibhu: One big agents andswyx: skills from first princip holdsRyan Lopopolo: all skills did not exist when we started doing this.Vibhu: You have a short [00:12:00] one 100 line overall table of contents and then you have little skills, right? Core beliefs, MD tech tracker. Yeah. Yeah. The scale is overRyan Lopopolo: The tech jet tracker and the quality score are pretty interesting because this is basically a tiny little scaffold, like a markdown table, which is a hook for Codex to review all the business logic that we have defined in the app, assess how it matches all these documented guardrails and propose follow up work for itself.Before beads and all these ticketing systems, we were just tracking follow up work as notes in a markdown file, which, we could spa an agent on Aron to burn down. There's this really neat thing that like the models fundamentally crave text. So a lot of what we have done here is figure out ways to inject textswyx: intoRyan Lopopolo: the system right when we get a page, because we're missing a timeout, for example.I can just add Codex in Slack on that page and say, I'm gonna fix this by adding a timeout. Please update our reliability documentation. To require that all network calls have [00:13:00] timeouts. So I have not only made a point in time fix, but also like durably encoded this process knowledge around what good looks like.swyx: Yeah.Ryan Lopopolo: And we give that to the root coding agent as it goes and does the thing. But you can also use that to distill tests out of, or a code review agent, which is pointed at the same things to narrow the acceptable universe of the code that's produced.swyx: I think one of the concerns I have with that kind of stuff is you think you're making the right call by making, it's persisted for all time across everything.Yes. But then you didn't think about the exceptions that you need to make, right? And that you have to roll it back.Vibhu: Part of it isswyx: also sometimes it can follow your s instructions too.Vibhu: It's somewhat a skill, right? So it determines when it uses the tools, right? Like it's not like it'll run outta every call.It'll determine when it wants to check quality score, right?Ryan Lopopolo: Yeah. And we do in the prompts we give these agents, allow them to push back,[00:13:51] Agent Code Review RulesRyan Lopopolo: When we first started adding code review agents to the pr, it would be Codex, CLI. Locally writes the change, pushes up a PR on [00:14:00] those PR synchronizations of review agent fires.It posts a comment. We instruct Codex that it has to at least acknowledge and respond to that feedback. And initially the Codex driving the code author was willing to be bullied by the PR reviewer, which meant you could end up in a situation where things were not converging. So yeah, we had to,swyx: he's just a thrash.Ryan Lopopolo: We had to add more optionality to the prompts on both of these things, right? The reviewer agents were instructed to bias toward merging the thing to not surface anything greater than a P two in priority. We didn't really define P two, but we gave it, youswyx: did define P two.Ryan Lopopolo: We gave it a framework within which to score its outputswyx: and then greater than P zero is worse, right?Yes. P two is very good.Ryan Lopopolo: P zero is you will mute the code place ifswyx: you merch thisRyan Lopopolo: thing, right?swyx: Yeah.Ryan Lopopolo: But also on the code authoring agent side, we also gave it the flexibility to either defer or push back against review feedback, right? This happens all the time, right? Like I happen to notice something and leave a code review, [00:15:00] which.Could blow up the scope by a factor of two. I usually don't mean for that to be addressed Exactly. In the moment. It's more of an FYI file it to the backlog, pick it up in the next fix it week sort of thing. And without the context that this is permissible, the coding agents are gonna bias toward what they do, which is following instructions.swyx: Yeah.[00:15:19] Autonomous Merging Flowswyx: I do wanted to check in on a couple things, right? Sure. All the coding review agent, it can merge autonomously. I think that's something that a lot of people aren't comfortable with. And you have a list here of how much agents do they do Product code and tests, CI configuration and release tooling, internal Devrel tools, documentation eval, harness review, comments, scripts that manage the repository itself, production dashboard definition files, like everything.Yes. And so they're just all churning at the same time, is there like a record that, that any human on the team pulls to stop everythingRyan Lopopolo: Because we are building a native application here. We're not doing continuous deploy. So there's still a human in the loop for cutting the release branch.I see. We require a blessed [00:16:00] human approved smoke test of the app before we promote it to distribution, these sort of things.swyx: So you're working on the app, you're not building like infrastructure where you have like nines of reliability, that kinda stuff?Ryan Lopopolo: That's correct. That's correct. Okay. And also like full recognition here that all of this activity took in a completely greenfield repository.There's. Should be no script that this applies generally toswyx: this is a production thing, you're gonna shipRyan Lopopolo: toswyx: customers. Of course. Yeah, of course. So this is realVibhu: And like one of the things there is, you mentioned you started this as a repo from scratch. The onboarding first month or so was pretty, it was like working backwards, right?Yeah. And then you had to work with the system and now you're at that point where you know, you're very autonomous. I'm curious like, okay, so what, how human in the loop is it? So what are the bottlenecks that you wish you could still automate? And part of that is also like, where do you see the model trajectory improving and offloading more human in the loop?We just got 5.4. It's a really good,Ryan Lopopolo: fantastic model, by the way.Vibhu: Yeah. Yeah. It's the first one that's merged. Top tier coding. So it's codex level coding and reasoning. So general reasoning both in one model. SoRyan Lopopolo: andVibhu: computer [00:17:00] use vision.Ryan Lopopolo: Now we now with five four, I can just have Codex write the blog post, whereas for this one I had to balance between chat.swyx: Oh, I need to, I might be out of a job. Oh my God.Ryan Lopopolo: Oh,swyx: I know. You just gave me an idea for a completely AI newsletter that five four could do. Yeah, I get it Now.Ryan Lopopolo: This sort of thing is just one example of closing the loop, right? Like the dashboard thing you mentioned. We have Codex authoring the Js ON, for the Grafana dashboards and publishing them and also responding to the pages, which means when it gets the page, it knows exactly which dashboards are defined and what alerts.What alert was triggered by which exact log in the code base. ‘cause all of this stuff is collated together.swyx: It has to own everything.Yes. Yeah. Yeah.Ryan Lopopolo: And it means that if we have an outage that did not result in a page. It has the existing set of dashboards available to it. It has the existing set of metrics and logs and can figure out where the gaps in the dashboard are or [00:18:00] in the underlying metrics and fix them in one go.In the same way, you would have a full stack engineer be able to drive a feature from the backend all the way to the front end.Vibhu: So it, it seems like a lot of the work you guys had to do was you as a small team are fully working for a way that the model wants the software to be written. It's like less human legible for better. Code legibility, agent legibility. How do you think that affects broader teams? So one at OpenAI, do liaison, like this is how software should be written. Like I can imagine, say you join a new team with this methodology, this mindset there's ways that, teams do code review, teams write code, like teams are structured and a lot of it is for human legibility.So should we all swap? Like how does this play back one broader into OpenAI and then like broader into the software engineering, right? Is it like teams that pick this up will it's pretty drastic, right? You have to make a pretty big switch. Should they just full send Yeah.Ryan Lopopolo: The mindset is very much that I'm removed from the process, right? I can't really have deep code level opinions about [00:19:00] things. It's as if I'm. Group tech leading a 500 person organization.Vibhu: Yeah.Ryan Lopopolo: Like it's not appropriate for me to be in the weeds on every pr. This is why that post merge code review thing is like a good analog here, right?Like I have some representative sample of the code as it is written, and I have to use that to infer what the teams are struggling with, where they could use help, where they're already moving quickly and I can pivot my focus elsewhere.Vibhu: Yeah.Ryan Lopopolo: So I don't really have too many opinions around the code as it is written.I do, however, have a command based class, which is used to have repeatable chunks of business logic that comes with tracing and metrics and observability for free. And the thing to focus on is not how that business logic is structured, but that it uses this primitive ‘cause I know that's gonna give leverage by default.Vibhu: Yeah.Ryan Lopopolo: Yeah, back to that sort of systems stinking,Vibhu: and you have part of that in your blog post, enforcing architecture and ta taste how you set boundaries for what's used. There's also a section on redefining [00:20:00] engineering and stuff, but yeah, it's just, it's interesting to hear,Ryan Lopopolo: and as the models have gotten better, they have gotten better at proposing these abstractions to unblock themselves, which again, lets me move higher and higher up the stack to look deeper into the future on what ultimately blocked the team from shipping.swyx: Yeah. You mentioned so you, this is primarily a, it is like a 1 million line of code base electron app. But it manages its own services as well, so it's like a backend for front end type thing.Ryan Lopopolo: We do have a backend in there, but that's hosted in the cloud.Yeah. This sort of structure is actually within the separate main and render processesWithin theswyx: electric.That's just how electronic works.Ryan Lopopolo: Yeah, of course. So have also treated like. MVC style decomposition with the same level of rigor, which has been very fun.swyx: I have a fun pun. This is a tangent, NVC is model view controller. Any sort of full stack web Devrel knows that.But my AI native version of this is Model view Claw, the clause the harness.Ryan Lopopolo: That's right. That's right. I do think that there is an interesting space to [00:21:00] explore here with Codex, the harness as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding.We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to build, a user journey that you're trying to solve into code, it's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate and prompts to let the model cook.Yeah. It's been very fun. And there's also a very engineering legible way of increasing capabil. It's fantastic, right? Yeah. Just give you, just give the model scripts, the same scripts you would already build for yourself.swyx: Yeah.Yeah. So for listeners, this is Ryan saying that software engineering or coding against will eat knowledge work like the non-coding parts that you would normally think.Oh, you have to build a separate agent for it. No, start a coding agent and go out from there. Which open Claw has like it's pie Underhood.Ryan Lopopolo: [00:22:00] Yes.Vibhu: Basically define your task in code. Everything is a codingswyx: agent by the way. Since I brought it up, it's probably the only place we bring it up. Is any open claw usage from you?Any?Ryan Lopopolo: No. No. Not for me. I don't have any spare Mac Minis rattling around my house.swyx: You can afford it? No. I just, I'm curious if it's changed anything in opening eye yet, but it's probably early days. And then the other, the other thing I, I wanna pull on here is like you mentioned ticketing systems and you mentioned prs and I'm wondering if both those things have to go away or be reinvented for this kind of coding.So the git itself and is like very hostile to multi-agent.Ryan Lopopolo: Yeah. We make very heavy use of work trees.swyx: But like even then, like I just did a, dropped a podcast yesterday with Cursors saying, and they said they're getting rid of work trees ‘cause it still has too many merge conflicts.It's still un too un unintuitive. But go ahead.Ryan Lopopolo: The models are really great at resolving merge conflicts. Yeah. And to get to a state where I'm not synchronously in the loop in my terminal, I almost don't care that there are mergeswyx: with disposable.[00:23:00] Yeah.Ryan Lopopolo: We invoke a dollar land skill and that coaches codex to push the PR Wait for human and agent reviewers Wait for CI to be green.Fix the flakes if there are any merged upstream. If the PR comes into conflict, wait for everything to pass. Put it in the merge queue. Deal with flakes until it's in Maine. End. This is what it means to delegate fully, right? This is in a, very large model re probably a significant tax on humans to get PRS merged, but the agent is more than capable of doing this and I really don't have to think about it other than keep my laptop open.swyx: Yeah. I used to be much more of a control freak, but now I'm like, yeah, actually you could do a better job of this than me. Yeah. With the right context. Yes.[00:23:47] Encoding Requirementsswyx: Anything else in harness in general? Just this piece, I just wanna make sure we,Ryan Lopopolo: I think one thing that I maybe didn't make super clear in the article that I heard on Twitter as an interesting, that's respond [00:24:00]swyx: to them.What's the chatter and then what's your response?Ryan Lopopolo: Ultimately, all the things that we have encoded in docs and tests and review agents and all these things are ways to put all the non-functional requirements of building high scale, high quality, reliable software into a space that prompt injects the agent.We either write it down as docs, we add links where the error messages tell how to do the right thing. So the whole meta of the thing is to basically tease out of the heads of all the engineers on my team, what they think good looks like, what they would do by default, or what they would coach a new hire on the team to do to get things to merch.And that's why we pay attention to all the mistakes, mistakes that the agent makes, right? This is code being written that is misaligned with some as yet not written down, non-functional requirement.swyx: Sorry, what? Did the online people misunderstand orRyan Lopopolo: No,swyx: whatyouRyan Lopopolo: responded to? Somebody just literally said that.I was like, oh yeah,swyx: okay,Ryan Lopopolo: This is the [00:25:00] thing. This is what I've been doing. Oh, youswyx: agree? Yeah. I see. Interesting.Ryan Lopopolo: One other neat thing, which I did totally did not expect is folks were just. Taking the link to the article and giving it to pi or Codex and say, make my repo this,Vibhu: you achi a whole recursion.Ryan Lopopolo: And it was wildly effective. Really? It was wildly effective. NoVibhu: way. It just actually is something I tried with five, four yesterday. I didn't have time. Last time I was like out speaking of something, and this is one of my things, I was like, okay, I have this article. Can we just scaffold out what it would be like to run this?And I, I did it first as that and then I was like, okay, let me take another little side repo and say okay, if I was to fully automate this like this because I haven't written a line of code, it'sRyan Lopopolo: like over full, setVibhu: it right. The side thing I'm doing of voice. TTS I'm just like, slobbing out, whatever.It's nothing production. I'm like, how would I make this like this? And it's actually like a really good way. It's like a good way to learn what could be changed, what could be like, it's just a good analyzing, right? You give it all the codes, you give it all the context, you give it the article and it walks you through it very well.That's right. That's right.[00:25:57] Inlining Dependencies[00:25:57] Dependencies Going Away & Brett Taylor's Responseswyx: I guess one more thing before we go to Symphony is I wanted to cover [00:26:00] Brett Taylor's response. We had him on the show. He is your chairman, which is wild. Yeah. That he's reading your articles as well and like getting engaged in it. He says software dependencies are going away.Basically they can just be like vendored. Yes. Response.Ryan Lopopolo: Aswyx: hundred percent. A hundred percent agree. You still pro qr, you still pay Datadog. You still pay Temporal. Thank you.Ryan Lopopolo: Yep. The level of complexity of the dependencies that we can internalize is, I would say low, medium right now. Just based on model capability.What does the,swyx: what is medium?Ryan Lopopolo: I would say like a. A couple thousand line dependency is a thing that we could in-house No problem. Call in an afternoon of time. One neat thing about it is like probably most of that code you don't even need. Like by in-house and abstraction, you can strip away all the generic parts of it and only focus on what you need to enable the specific thing.Yes. You're building,swyx: I've been calling this the end of b******t plugins.Ryan Lopopolo: Yeah.swyx: Because there's so much when I published an open source thing, I want to accept everything, be liberal. I want to accept, this is post's law, but that means there's so much bloat. Yes. There's so much overhead.Ryan Lopopolo: One other neat thing about [00:27:00] this too is when we deploy Codex Security on the repo, it is able to deeply review and change. The internalized dependencies in a much lower friction way than it would be to like, push patches upstream, wait for them to be released, pull them down, make sure that's compatible with all the transitive I have in my repo and things like that.So it's also much lower friction to internalize some of these things if code is free. ‘cause the tokens are cheap sort of thing.swyx: Yeah. Yeah. I think like the only argument I have against this is basically scale testing, which obviously the larger pieces of software like Linux, MySQL, he calls up even the Datadog and Temporals and then maybe security testing where Yes.Classically, I think, is it linis tos, it said security open source is the best disinfectant.Ryan Lopopolo: Many eyes.swyx: Many eyes. And if inline your dependencies and code them up, you're gonna have to relearn mistakes from other people that Yep.Ryan Lopopolo: Yep. And to internalize that dependency, you're back to zero and you have to start.Reassembling all those bits and pieces to Yeah. Have [00:28:00] high confidence in the code as it is written. Yeah.Vibhu: Even part of the first intro of this, you basically mentioned like everything was written by codex, including internal tooling, right? So internal tooling, like when you're visualizing what's going on it's writing it for itself.swyx: Yeah. I'm built internal tools way I now, and like I just show them off and they're like, how long did you spend? And I didn't spend any time. I just prompted it,Ryan Lopopolo: very funny story here.swyx: Yeah, go ahead.Ryan Lopopolo: We had deployed our app to the first dozen users internally had some performance issues, so we asked them to export a trace for us get a tar ball, gave it to our on-call engineer, and he did a fantastic job of working with Codex to build this beautiful local Devrel tool, next JS app, the drag and drop the tar ball in, and it visualizes the entire trace.It's fantastic. Took an afternoon, but none of this was necessary. Because you could just spin up codex and give it the tar ball and ask the same thing and get the response immediately. So in a way, optimizing for human [00:29:00] legibility of that debugging process was wrong. It kept him in the loop unnecessarily when instead he could have just like Codex cooked for five minutes and gotten this same.swyx: Yeah, you verify your instincts here of this is how we used to do it. Or this is how I would have used to solve it.Ryan Lopopolo: Yeah. In this local observability stack. Like sure, you can de deploy Yeager to visualize the traces, but I wouldn't expect to be looking at the traces in the first place because I'm not gonna write the code to fix them.swyx: Yeah. So basically there needs to be like this kind of house stack and owning the whole loop. I think that is very well established. And it sounds like you might be like sharing more about that in the future, right?Ryan Lopopolo: Yeah. I think we're excited to do[00:29:36] Ghost Libraries Specs[00:29:36] Ghost Libraries & Distributing Software as SpecsRyan Lopopolo: We're gonna talk about Symphony in a little bit, but like the way we distribute it as a spec, which I think folks are calling Ghost Libraries on Twitter.This is like a such a cool name. It does mean it becomes much cheaper to share software with the world, right? You define a spec, how you could build your own specifying as much as is required for a coding agent to reassemble it [00:30:00] locally. The flow here is very cool. Like we have taken. All the scaffolding that has existed in our proprietary repo spun up a new one.Ask Codex with our repo as a reference. Write the spec. We tell it. Spin up a team ox spawn a disconnected codex to implement the spec. Wait for it to be done. Spawn another codex and another team ox to review the spec com or review the implementation compared to upstream and update the spec so it diverges less.And then you just loop over and over Ralph style until you get a spec that is with high fidelity able to reproduce the system as it is. It's fantastic.Vibhu: And you're basically, you're not really adding any of your human bias in there, right? That's correct. A lot of times people write a spec and be like, okay, I think it should be done this way, and you'll riff on something.And it's no, the agent could have just handled it like you're still scaffolding in a sense, right? I want it done this way. It can determine its spec better.swyx: That's right. That's right. Part of me it, I'm, I've been working a lot on evals recently, and part of me is wondering if [00:31:00] an agent can produce a spec that it cannot solve.Is it always capable of things that he can imagine or can you imagine things that it is impossible to do?Ryan Lopopolo: I think with Symphony, we, there's like this there's this axis where you have things that are easier, hard, or established or new, right? And I think things that are hard and new is still something that the models need humans.Yeah. Drive.swyx: Yeah. Yeah.Ryan Lopopolo: But I think those other quadrants are largely salt. Given the right scaffold and the right thing that's gonna drive the agent to completion,swyx: it's crazy that it solved,Ryan Lopopolo: but it means that the humans, the ones with limited time and attention get to work on the hardest stuff, like the problems where it's pure white space out in front. Or like the deepest refactorings where you don't know what the proper shape of the interfaces are. And this is where I wanna spend my time. ‘cause it lets me set up for the next level of scale.swyx: Yeah. Yeah. Amazing. Let's introduce Symphony.I think we've been mentioning it every now and then. Elixir. Interesting option.Ryan Lopopolo: Yeah.swyx: Yeah. I'm not,Ryan Lopopolo: again, like the [00:32:00] elixir manifestation here is just a derivative. Is it a modelswyx: chosen? Yeah.Ryan Lopopolo: Yeah. Yeah. And it chose that because the process supervision and the gen servers are super amenable to the type of process orchestration that we're doing here.You are essentially spinning up little Damons for every task that is in execution and driving it to completion, which. Means the mall gets a ton of stuff for free by using Elixir and the Beam.swyx: I had to go do a crash course in Beam and Elixir, and I think most people are not operating at that scale of concurrency where you need that.But it is a good mental model for Resum ability and all those things. And these are things I care about. But tell me the story, the origin story of Symphony. What do you use it for? Is this, how did it form maybe any abandoned paths that you didn't take?[00:32:46] Terminal Free Orchestration[00:32:46] Symphony: Removing Humans from the LoopRyan Lopopolo: At the end of December we were at about three and a half PRS per engineer per day.This was before five two came out in the beginning of January. Everyone gets back from holiday with five two and no other work [00:33:00] on the repository. We were up in the five to 10 PRS per day per engineer. And I don't know about y'all, but like it's very taxing to constantly be switching like that. Like I was pretty tapped out at the end of the day, again, where are the humans spending their time? They're spending their time context switching between all these active tmox pains to drive the agent forward.swyx: Yeah. No way. Yeah.Ryan Lopopolo: So let's again, build something to remove ourselves from the loop. And this is what frantic sprinted adapt here to find a way to remove the need for the human to sit in front of their terminal.So a lot of experimentation with Devrel boxes and, automatically spinning up agents, like it seems like a fantastic end state here, where my life is beach. I open live twice a day and say yes no to these things. Yeah. And this is again, a super, super interesting framing for how the work is done.Because I become more latency and sensitive. I have [00:34:00] way less attachment to the code as it is written. Like I've had close to zero investment in the actual authorship experience. So if it's garbage. I can just throw it away and not care too much about it. In Symphony, there's this like rework state where once the PR is proposed and it's escalated to the human for review, it should be a cheap review.It is either mergeable or it is not. And if it's not, you move it to rework. The elixir service will completely trash the entire work tree NPR and start it again from scratch. Okay. And this is that opportunity again to say, why was it trash right? What did the agent do that wasswyx: bad. Yeah.Ryan Lopopolo: Fix that before moving the ticket toswyx: endRyan Lopopolo: of progress again.swyx: Yeah. Why is this not in codex app? I guess this, you guys are ahead of Codex app,Ryan Lopopolo: yeah, so the way the team has been working is basically to be as AI pilled as possible and spread ahead. And a lot of the things we have worked on have fallen out [00:35:00] into a lot of the products that we have.Like we were in deep consultation with the Codex team to. Have the Codex app be a thing that exists, right? To have skills be a thing that Codex is able to use. So we didn't have to roll our own to put automations into the product. So all of our automatic refactoring agents didn't have to be these hand rolled control loops.It has been really fantastic to be, in a way, un anchored to the product development of Frontier and Codex and just very quickly try to figure out what works and then later find the scalable thing that can be deployed widely. It's been a very fun way to operate. It's certainly chaotic. I have lost track very often of what the actual state of the code looks like.‘cause I'm not in the loop. There was. One point where we had wired playwright directly up to the Electron app. With MCPM CCPs, I'm pretty bearish on because the harness forcibly injects all those tokens in the [00:36:00] context, and I don't really get a say over it. They mess with auto compaction. The agent can forget how to use the tool.There's probably only what three calls in playwright that I actually ever want to use. So I pay the cost for a ton of things. Somebody vibed a local Damon that boots playwright and exposes a tiny little shim CLI to drive it. And I had zero idea that this had occurred because to me, I run Codex and it's able to, it's oh, it's better.Yeah. Like no knowledge of this at all. Uhhuh.[00:36:30] Multi Human ChaosRyan Lopopolo: So we have had like in human space to spend a lot of time doing synchronous knowledge sharing. We have a daily standup that's 45 minutes long because we almost have to. Fan out the understanding of the current state.swyx: Yeah, I was gonna say this is good for a single human multi-agent, but multi human, multi-agent is a whole like po like explosion of stuff.Ryan Lopopolo: Yeah. And that this is fundamentally why we have such a rigid, like 10,000 [00:37:00] engineer level architecture in the app because we have to find ways to carve up the space so people are not trampling on each other.swyx: Sorry, I don't get the 10,000 thing. Did I miss that?Ryan Lopopolo: The structure of the repository is like 500 NPM packages.It's like architecture to the excess for what you would consider, I think normal for a seven person team. But if every person is actually like 10 to 50. Then the like numbers on being super, super deep into decomposition and sharding and like proper interface boundaries make a lot more sense.swyx: Yeah. To me, that's why I talked about Microfund ends and I, an anex is from that world, but Cool. It is just coming back to, to, to this I dunno if you have other, thoughts on. Orchestrating so much work coin going through this. Is this enough? Is this like any aha moments?Vibhu: It'll be interesting to see like where, okay, so right now you pick linear as your issue tracker, right?swyx: Or it's like a is it actually linear? This is actually linear.[00:37:55] Linear vs Slack WorkflowVibhu: Oh, that's linear. It's linear.swyx: Oh I never looked atVibhu: video. The demo video I had to download to [00:38:00] run.swyx: So I, because I'm a Slack maxie, but Yeah, linear. Linear is also really good. Yes,Ryan Lopopolo: we do make a good use of Slack. We we fire off codex to do all these lotion, elasticity, fix ups, the things that like sync that knowledge into the repository.It's super cheap. Yeah.swyx: Yeah.Ryan Lopopolo: Just do it in Codex.swyx: My biggest plug is OpenAI needs to build Slack. You need to own Slack. Build yours. Turn this into Slack.Ryan Lopopolo: I did read about it. Youswyx: did?Ryan Lopopolo: Yeah.[00:38:25] Collaboration Tools for AgentsRyan Lopopolo: I would say that if we think that we want these agents to do economically valuable work, which is like this is the mission, right?We want AI to be deployed widely, to do economically valuable work, then we need to find ways for them to naturally collaborate with humans, which means collaboration tooling, I think, is an interesting space to explore.swyx: Yeah, totally. Yeah. GitHub, slack, linear.Vibhu: Yeah, that was my thing. Okay, where do we see right now Codex has started Codex Model, then CLI, now there's an app, app can let me shoot off multiple Codex is in parallel, but there's no great team collaboration for Codex.And it [00:39:00] seems like your team had some say into what comes out, right? So you talked to ‘em, codex kind of was a thing. From there, if you guys are on the bound, what stuff that like, you might not focus on, but what do you expect other people to be building, right? So people that are like five x 50 Xing.Should you build stuff that's like very niche for your workflow, for your team? Should it be more general so other people can adopt? Is there a niche there? ‘Cause part of it is just okay, is everything just internal tooling? Do we have everything our own way? Like the way our team operates has our own ways that we like to communicate or is there a broader way to do it?Is it something like a issue tracker? Just thoughts if you wanna riff on that.[00:39:35] Standardizing Skills and CodeRyan Lopopolo: I think TBD we have not figured this out in a general way. I do think that there is leverage to be had in making the code and the processes as much the same as possible. If you think that code is context, code is prompts, it's better from the agent behavior perspective to be able to look in a package in directory X, Y, Z, and it not to have to page so [00:40:00] deeply into directory if you C, because they have the same structure, use the same language, they have the same patterns internally.And that same like leverage comes from aligning on a single set of skills that you're pouring every engineer's taste into to make sure that the agent is effective. So like in our code base, we have, I think, six skills. That's it. And if some part of the software development loop is not being covered, our first attempt is to encode it in one of the existing setup skills, which means that we can change the agent behavior.Yeah. More cheaply than changing the human driver behavior.swyx: Yeah.[00:40:39] Self Improvement via Logsswyx: Have you ever, have you experimented with agents changing their own behavior?Ryan Lopopolo: We do.swyx: Yeah. Or parent agent changing a subagents, behavior or something like that.Ryan Lopopolo: We have some bits for skill distillation. So for example, there's one neat thing you can do with Codex, which is just point it at its own session logs to ask it to tell you how you can use [00:41:00] the tool pedal better.swyx: It's like introspectionRyan Lopopolo: or ask it to do things. I useVibhu: this session better. What skills should Iswyx: high? I like the modification of, you can do, just do things to you can just ask agent to do things.Ryan Lopopolo: Yeah. You can just codex things. This is like a, this is like a silly emoji that we have, right? You can just codex things, you can just prompt things.It's really glorious future we live in, but okay, you can do that one-on-one. But we're actually slurping these up for the entire team into blob storage and. Running agent loops over them every day to figure out where as a team can we do better and how do we reflect that back into the repositories?Yes, though everybody benefits from everybody else's behavior for free. Same for like PR comments, right? These are all feedback. That means the code as written, deviated from what was good, a PR comment, a failed build. These are all signals that mean at some point the agent was missing context. We gotta figure out how toswyx: Yeah.Ryan Lopopolo: Slurp it up and put it back in the reboot.swyx: By the way, I do this exactly right. I used to, when I use cloud code for [00:42:00] knowledge work, cloud cowork is like a nice product, right? Yes. In I think you would agree. I always have it tell me what do I do better next time? And that's the meta programming reflection thing.So I almost think like you have six reflection extraction levels in symphony and almost like the zero of layer. So the six levels are PO policy, configuration, coordination, execution, integration, observability. We've talked about a couple of these, but the zero layer is like the, okay, are we working well?Can we improve how we work? Yes. Can I modify my own workflow without MD or something? I don't know.Ryan Lopopolo: Yeah, of course. Yeah, of course you can. Like this thing is also able to cut its own tickets ‘cause we give it full access.Yeah. Make it a ticket to have it cut. Tickets you can.Put in the ticket that you expect it to file as on follow up work,swyx: like Yeah. Self-modifying. Yeah.Ryan Lopopolo: Yeah.[00:42:44] Tool Access and CLI FirstRyan Lopopolo: Put, don't put the agent in a box. Give the agent full accessibility over it. Domain.swyx: I had a mental reaction when you said don't put the agent in a box. So I think you should put it in a box. Like it's just that you're giving the box everything it needs.Ryan Lopopolo: Yeah. Context and tools.swyx: But we're like, as developers, we're used to calling [00:43:00] out to different systems, but here you use the open source things like the Prometheus, whatever, and you run it locally so that you can have the full loop. I assume.Ryan Lopopolo: Yep.Vibhu: I think likeRyan Lopopolo: another, you wanna minimize cloud, cloud dependencies.Vibhu: You also want to make sure that you think about what the agent has access to. What does it see? Does it go back into the loop, like from the most basic sense of you let it see its own like calls, traces it can determine where it went wrong. But are you feeding that back in? So you know, just the most basic level of you wanna see exactly what's input output, like does the agent have access to.What is being outputted, right? It can self-improve a lot of these things. It's allRyan Lopopolo: text, right? My job is to figure out ways to funnel text from one agent to the other.swyx: It's so strange like way back at the start of this whole AI wave Andre was like, English is the hottest day programming language.It's here, it's just Yeah. The feature as well.Vibhu: A lot of, okay. Like a lot of software, a lot of stuff. There's a gui, it's made for the human. We're seeing the evolution of CLI for everything, right? All tools have CLIs. Your agents can use [00:44:00] them well, do we get good vision? Do we get good little sandboxes?Like right now? It's a really effective way, right? Models love to use tools. They love the best. They love to read through text. So slap a CLI let it go loose. That works for everything.Ryan Lopopolo: It does. Yeah. Yeah.[00:44:14] UI Perception and RasterizingRyan Lopopolo: We've also been adapting nont, textual things to that shape in order to improve model behavior in some ways, right?We want the agent to be able to see the UI agents do not perceive visually in the same way that we do. They don't see a red box, they see red box button, right? They see these things in latent space. So if we want, Hey, yeah, I do. We haveswyx: a ding if that goes off every time. Alien spaceRyan Lopopolo: ding.Anyway if we wanna actually make it see the layout, it's almost easier to rasterize that image to ask EOR and feed it in to the agent. Ha. And there's no reason you can't do both, right? To like further refine how the model perceives the object it's [00:45:00] manipulating.swyx: Cool. Could we, you wanna talk about a couple more of these layers that might bear more introspection or that you have personal passion for?[00:45:07] Coordination Layer with ElixirRyan Lopopolo: I will say that the coordination layer here was a really tricky piece to get right.swyx: Let's do it. Yep. I'm all about that. And this is Temporal core.Ryan Lopopolo: This is where when we turn the spec into Elixir, where like the model takes a shortcut, right? Like it's oh, I have all these primitives that I can make use of in this lovely runtime that has native process supervision.Which is I think, a neat way to have taken the spec and made it more choices achievable by making choices that naturally mapswyx: Yeah.Ryan Lopopolo: To the domain, right? In the same way that like you would prefer to have a TypeScript model repo if you are doing full stack web development, right? Because the ability to share types across the front end and backend reduces a lot of complexity.And becauseswyx: that's what graph kill used to be.Ryan Lopopolo: That's right. Andswyx: I don't know if it's still alive, butRyan Lopopolo: [00:46:00] no humans in the loop here. So like my own personal ability to write or not write elixir. Doesn't really have to bias us away from using the right tool for the job. It is just wild.swyx: Love it. I love it.Yeah. I wonder if any languages struggle more than others because of this? I feel like everyone has their own abstractions. That would make sense. But maybe it might be slower, it might be more faulty where like you'd have to just kick the server every now and then. I, I don't know. I think observability layer is really well understood.Integration layer, CP is dead. I think all these just like a really interesting hierarchy to travel up and down. It's common language for people working on the system to understandRyan Lopopolo: The policy stuff is really cool, right? Yeah. You don't really have to build a bunch of code to make sure the system wait for the, to passswyx: it's institutional knowledge.Ryan Lopopolo: Yeah. You just give it the G-H-C-L-I with some text that say CI has to pass. It makes the maintenance of these systems a lot easier.[00:46:57] Agent Friendly CLI Outputswyx: Do you think that CLI maintainers need to be [00:47:00] do anything special for agents or just as is? It's good because like I don't think when people made the G GitHub, CLI, they anticipated this happening.Ryan Lopopolo: That's correct. The GH CLI is fantastic. It's great super industry.swyx: Everyone go try GH repo create GH pull and then pull request number, right? GH HPR, like 1 53, whatever. And then it like pullsRyan Lopopolo: basically my only interaction with the GitHub web UI at this point is GH PR view dash web.Exactly. Glanceswyx: at the diffRyan Lopopolo: and be like Sure thing. Send it. Yeah. But the CLI are nice ‘cause they're super token efficient and they can be made more token efficient really easily. Like I'm sure you all have seen like I go to build Kite or Jenkins and I could just get this massive wall of build output.And in order to unblock the humans, your developer productivity team is almost certainly gonna write some code that parses the actual exception out of the build logs and sticks it in a sticky note at the top of the page. And you basically [00:48:00] want CLI to be structured in a similar way, right? You're gonna want to patch dash silent to prettier because the agent doesn't care that every file was already formatted.Just wants to know it's either formatted or not. So it can then go run a right command. Similarly, like in our PNPM distributed script runner, when we had one, when you do dash recursive, like it produces a absolute mountain of text. But all of that is for passing. Test suites. So we ended up wrapping all of this in another scriptswyx: to suppress the,Ryan Lopopolo: which you can vibe the channel only output the failing parts of the tests.swyx: You make a pipe errors versus the standard, standard out. I don't know. Okay. Whatever. Too much thinking have to do that. The CII used to maintain SCLI for my company and yeah, this is like core, very core to my heart. But you're vibing my job.Ryan Lopopolo: That's right.swyx: Cool. Any other things?This is a long spec. [00:49:00] I appreciate that. It's got a lot of strong opinions in here. Any other things that we should highlight? I think obviously you can spend the whole day going through some of these, but I do think that some of these have a lot of care or some of this you might wanna tell people, Hey, take this, but, make it your own.[00:49:15] Blueprint Spec and GuardrailsRyan Lopopolo: Fundamentally, software is made more flexible when it's able to adapt to the environment in which it is deployed, which means that things like linear or GitHub even are specified within the spec, but not required pieces of it. There's like a more platonic ideal of the thing that you could swap in like Jira or Bitbucket, for example.But being able to tightly specify things like the ID formats or how the Ralph Loop works for the individual agents. Basically means you can get up and running with a fully specified system quickly that you then evolve later on. I think we never intended for this to be a static spec that you can [00:50:00] never change.It's more like a blueprint to get something worth a starting point up and running.swyx: Yeah.Ryan Lopopolo: For you then to vibe later to your heart's content,swyx: you have like code and scripts in here where it's oh, I think this is a really good prompt. It's just a very long prompt.Ryan Lopopolo: Fundamentally, the agents are good at following instructions, so give them instructions.And it will, improve the reliability of the result. We, much like the way we use Symphony, we don't want folks to have to monitor the agent as it is vibing the system into existence. So being very opinionatedVery strict around what these success criteria are means that our deployment success rate goes up. Yeah. It means we don't have to get tickets on this thing.Vibhu: Think it all goes back to that like code to disposable, right? Like early on when you had CLI or you'd kick off a Codex run, it would take two hours. You would wanna monitor okay, I'm in the workflow of just using one.I don't want it to go down the wrong path. I'll cut it off and, just shoot off four, like that was my favorite thing of the Codex app, right? Yeah. Just Forex it like, [00:51:00] it's okay. One of them will probably be right, one of them might be better. Stop overthinking it. Like my first example was probably like deep research.When you put out deep research and I'd ask it something like, I asked it something about LLM, it thought it was legal something and spent an hour, came back with a report completely off the rails. And I was like, okay, I gotta monitor this thing a bit. No don't monitor it. Just you want to build it so it's that it, it goes the right way.And you don't wanna, you don't wanna sit there and babysit, right? You don't want to babysit your agentsRyan Lopopolo: with that deep research query that you made. Looking at the bad result, you probably figured out you needed to tweak your prompt Yeah. A bit, right? That's that guardrail that you fed back into the code base for the task, your prompt to further align the agent's execution.Same sort of concept supply there too.swyx: When you talk, how are the customers feelingRyan Lopopolo: for Symphony? I think we have none, right? This is a thing we have put out into theswyx: world. Symphony's internal, right? As long as you are happy, you are the customer. That'

Wednesday, March 25, 2026   In today's episode of Astronomy Daily, Anna and Avery cover six major stories from the last 24 hours in space and astronomy — including two landmark NASA announcements that could reshape the future of human space exploration.   Story 1: NASA Cancels Lunar Gateway — Pivots to $20 Billion Moon Base NASA Administrator Jared Isaacman announced at the agency's 'Ignition Day' event that the Lunar Gateway orbital space station has been paused, with resources redirected toward a phased $20 billion base on the lunar surface. The three-phase plan runs from 2026 to beyond 2032 and involves international partners including JAXA, the Italian Space Agency, and the Canadian Space Agency. Source: https://www.space.com/space-exploration/artemis/nasas-lunar-gateway-space-station-is-out-moon-bases-are-in Story 2: NASA's SR-1 Freedom — The First Nuclear-Powered Interplanetary Spacecraft Also announced at Ignition Day, Space Reactor-1 Freedom is planned for a December 2028 launch to Mars. It will use Nuclear Electric Propulsion and carry the Skyfall payload — three Ingenuity-class helicopters designed to scout future human landing sites and map subsurface water ice. Source: https://www.space.com/astronomy/mars/nasas-1st-nuclear-powered-interplanetary-spacecraft-will-send-skyfall-helicopters-to-mars-in-2028 Story 3: Two Planets Forming Around Infant Star WISPIT 2 Astronomers using the ESO's Very Large Telescope have directly imaged two gas giant planets forming around the 5.4-million-year-old star WISPIT 2, located 437 light-years away in Aquila. The system is described as a mirror of our early solar system, with potential for more planets yet to be discovered. Published in The Astrophysical Journal Letters. Source: https://www.space.com/astronomy/exoplanets/scientists-discover-mirror-of-our-solar-system-in-2-exoplanets-forming-around-a-star Story 4: Hubble Revisits the Crab Nebula — 25 Years On NASA has released new Hubble Space Telescope images of the Crab Nebula, taken 25 years after the telescope first observed the object. The images reveal the nebula's continued expansion — the still-evolving remnant of a supernova first observed by astronomers in 1054 AD. Source: https://www.space.com/astronomy/hubble-revisits-a-cosmic-crab-after-25-years-space-photo-of-the-day-for-march-23-2026 Story 5: Fiber-Optic Cables Could Detect Moonquakes Two new studies from Los Alamos National Laboratory suggest that fiber-optic cables deployed directly on the lunar surface could detect moonquakes using Distributed Acoustic Sensing (DAS). The technique could replace expensive individual seismometers, with a single cable acting as thousands of sensors across hundreds of kilometres of lunar terrain. Source: https://www.space.com/astronomy/moon/future-artemis-missions-could-use-fiber-optic-cables-to-monitor-moonquakes Story 6: Rocket Lab 'Daughter of the Stars' — Europe's First Celeste Navigation Satellites Rocket Lab's Electron rocket launched the first two satellites for ESA's Celeste LEO-PNT constellation from Māhia, New Zealand on March 25. The mission is ESA's first foray into low-Earth orbit navigation, designed to complement and strengthen Europe's Galileo system. The constellation is named after Maria Celeste, daughter of Galileo Galilei. Source: https://www.space.com/space-exploration/launches-spacecraft/rocket-lab-electron-launch-european-space-agency-celeste-navigation-satellitesBecome a supporter of this podcast: https://www.spreaker.com/podcast/astronomy-daily-space-news-updates--5648921/support.Sponsor Details:Ensure your online privacy by using NordVPN. To get our special listener deal and save a lot of money, visit www.bitesz.com/nordvpn. You'll be glad you did!Become a supporter of Astronomy Daily by joining our Supporters Club. Commercial free episodes daily are only a click way... Click HereThis episode includes AI-generated content.

Claude Cowork came out of an accident.Felix and the Anthropic team noticed something interesting with Claude Code: many users were using it primarily for all kinds of messy knowledge work instead of coding. Even technical builders would use it for lots of non-technical work.Even more shocking, Claude cowork wrote itself. With a team of humans simply orchestrating multiple claude code instances, the tool was ready after a brief week and a half.This isn't Felix's first rodeo with impactful and playful desktop apps. He's helped ship the Slack desktop app and is a core maintainer of Electron the open-source software framework used for building cross-platform desktop applications, even putting Windows 95 into an Electron app that runs on macOS, Windows, and Linux.In this episode, Felix joins us to unpack why execution has suddenly become cheap enough that teams can “just build all the candidates” and why the real frontier in AI products is no longer better chat, but trusted task execution.He also shares why Anthropic is betting on local-first agent workflows, why skills may matter more than most people realize, and how the hardest questions ahead are about autonomy, safety, portability, and the changing shape of knowledge work itself.We discuss* Felix's path: Slack desktop app, Electron, Windows 95 in JavaScript, and now building Claude Cowork at Anthropic* What Claude Cowork actually is: a more user-friendly, VM-based version of Claude Code designed to bring agentic workflows to non-terminal-native users* Why “user-friendly” does not mean “less powerful”: Cowork as a superset product, much like how VS Code initially looked simpler than Visual Studio but became more hackable and extensible* Anthropic's prototype-first culture: why Cowork was built in 10 days using many pre-existing internal pieces, and how internal prototypes shaped the final product* Why execution is getting cheap: the shift from long memos, specs, and debate toward rapidly building multiple candidates and choosing based on reality instead of theory* The local debate: why Felix thinks Silicon Valley is undervaluing the local computer, and why putting Claude “where you work” is often more powerful* Why Claude gets its own computer: the VM as both a safety boundary and a capability unlock, letting Claude install tools, run scripts, and work more independently without constant approval* Safety through sandboxing: why “approve every command” is not a real long-term UX, and how virtual machines create a middle ground between uselessly safe and dangerously autonomous* How Cowork differs from Claude Code: coding evals vs. knowledge-work evals, different system-prompt tradeoffs, longer planning horizons, and heavier use of planning and clarification tools* Why skills matter: simple markdown-based instructions as a lightweight abstraction layer for reusable workflows, personalized automation, and portable agent behavior* Skills vs. MCPs: why Felix is increasingly interested in file-based, text-native interfaces that tell the model what to do, rather than forcing everything through rigid tool schemas* The portability problem: why personal skills should move across agent products, and the unresolved tension between public reusable workflows and private user-specific context* Real use cases already happening today: uploading videos, organizing files, handling taxes, managing calendars, debugging internal crashes, analyzing finances, and automating repetitive browser workflows* Why AI products should work with your existing stack: Anthropic's bias toward integrating with Chrome, Office, and existing workflows instead of rebuilding every app from scratch* Computer use one year later: how much better it has gotten, why vision plus browser context is such a superpower, and why letting Claude see the thing it is working on changes everything* Why many “AI verticals” may get compressed: specialized wrappers may matter in the short term, but better general models and stronger primitives could absorb a lot of narrow use cases* The future of junior work: Felix's concerns about entry-level roles, labor-market disruption, and whether AI can compress early-career learning into denser simulated experience* Why Waterloo grads stand out: internships, shipping experience, and learning how real teams build products versus purely theoretical academic preparation* The agentic future of the desktop: what it means for Claude to have its own computer, whether AI should act on your machine or a remote one, and how intimacy with personal data changes the product design space* Why Electron still mattered: shipping Chromium as a controlled rendering stack, the limits of OS-native webviews, and why browser engines remain one of the great software abstractions* Anthropic's Labs mentality: wild internal experiments, half-broken future-looking prototypes, and the broader effort to move users from asking questions to delegating increasingly long and valuable tasks* Why the endgame is not just more capability, but more independence: teaching users to trust AI with bigger scopes of work, for longer durations, with fewer interventionsFelix Rieseberg* X: https://x.com/felixrieseberg* LinkedIn: https://www.linkedin.com/in/felixrieseberg* Website: https://felixrieseberg.com/Anthropic* Website: http://anthropic.comFull Video PodTimestamps00:00 — Cheap execution and building all the candidates00:44 — Intro in the new Kernel studio02:47 — What Claude Cowork is04:18 — Why user-friendly can be more powerful05:33 — How Anthropic built Cowork07:09 — Prototype-first product development08:00 — Why local computers still matter09:20 — Skills, primitives, and platform leverage12:13 — Cowork's architecture: VM + Chrome + system prompt15:38 — Felix's own bug-fixing Cowork workflows17:38 — Local-first agents20:16 — Evals, planning, and knowledge-work optimization23:14 — What Anthropic means by evals24:21 — Scaffolding, tools, and why skills matter27:44 — Demo: YouTube uploads and self-generated skills31:03 — Calendar automation and cleaning your desktop34:47 — Browser context and why DOM access matters37:47 — Skills portability and plugins44:36 — Which AI categories survive?46:19 — Junior jobs, simulated work, and labor disruption52:00 — Gradual takeoff vs big-bang takeoff53:42 — Finance, taxes, and enterprise verticals56:24 — Vision and the improvement in computer use57:31 — Why Claude writes its own scripts58:06 — Should Claude have its own computer?1:01:26 — Windows 95 in JavaScript1:03:19 — VM tradeoffs and sandbox design1:07:23 — Approval fatigue and safe delegation1:11:18 — The future of Cowork1:12:27 — What comes next for agentic knowledge work1:15:13 — Electron, Chromium, and desktop software lessons1:22:16 — Multiplayer agents and coworker-to-coworker workflows1:26:05 — Anthropic Labs and closing thoughtsTranscriptAlessio: Hey everyone. Welcome to the Latent Space Podcast, our first one in the new studio. This is Alessio, founder of Kernel Labs, and I'm joined by swyx, editor of Latent Space.swyx: Yeah, so nice to be here. Thanks to, uh, TJ, Alessio, Allen helping to set everything up. It looks beautiful. We even have the logo outside.Yeah, kind.Felix: It's like really nice, right? When you walk in here as a guest, you're like, ah, this is a serious production. You're like, feel it immediately.swyx: Yeah. Felix, you've been, you're, you're currently a product manager of Cowork or,Felix: uh, really Technicswyx: Eng. Yeah. The, the identities are kind of vague member technical staff.Felix: I know member staff is like, the official title will carry around forever.swyx: Yeah. I basically kind of wanted, like we've been. Kinda obsessed. I, I've been using it a lot, even for managing latent space. Like, uh, cowork helps me upload videos and like title things and like edit and everything. It's, it's like really amazing.Alessio: Cool. He said multiple times Cowork has said gi in the group track.swyx: Yeah, yeah, yeah. So, so we have a second, uh, we have a second channel, uh, for latent space tv. Uh, and I, uh, and uh, we basically, this is our Discord meetup. Um, and I I, we have like Claude Coworks, it might be a GI, I don't know if we, we have, uh, uploaded it yet, but one of the sessions was like a, like a Claude cowork thing.Felix: I, you have to see, I would love to see it. Like, I'm so curious, like one of the most fun parts of my job is like constantly see the weird things people use Cowork for because it's obviously like very hard for us to actually design for specific use cases we do. But like every single person who's like most amazed is usually amazed about a thing that I didn't even expect cowork would be good at.Um, we have a new designer and it's one of the first small tasks. I was like, Hey, we need like a new emoji for cowork for our internal stock. It's like a pretty small thing. I like, can you please do it? And he drew an SVG and just gave it to coworker was like, can you animate this emoji? And now it has like this beautiful loopy animation.Um, and I mean, I think obviously this goes down to like, it turns out you can do more things with code than you expected, but it, it's like that kind of stuff that is really fun to me. So, long story short, I would love to see like, the kind of things you're doing.swyx: I'll pull it up. I'll pull it up.Felix: Yeah. Yeah.swyx: Uh, but before we get into it, I, I think always wanna start with like a top level. What is Claude Cowork for people who haven't heard of it? Haven't tried it out.Felix: Okay. Uh, real quick, Claude Cowork is a user friendly version of Claude Code. So the way it basically works is we have Claude Code and for us, fairly impressive agent harness that over December we noticed more and more people are using either, even though they're not technical, they, they're not at home in the terminal or they are at home in the terminal, but they started using Claude Code for non-coding workloads, right?Like managing expenses or like filling out receipts or organizing a knowledge base. Like there was a big obsidian moment that a lot of people liked and we wanted to capitalize on that, but also bring, bring this capability to people who are not terminal native and who might not know how to like brew and store something.So cowork is Claude Code running in original machine with a little bit of padding, a little bit more guardrails, making it a little safer and a little bit more convenient for people who don't wanna first open up the terminal when they go to work.swyx: It's interesting, uh, that is kind of. Pitch that way as a more user friendly thing because I always feel like it, it, to me, I I treat it as like why I'm familiar with Claude Code.Like we, we did a Claude Code episode Yeah. A year ago. But this one is like even more power user tools ‘cause it, uh, it kind of integrates much better with like clotting Chrome and, uh, in all the, all the other tooling. But like, maybe, maybe that's like a perception thing, right? LikeFelix: No, honestly, I don't think you're wrong.This is like a, a thing I've been thinking a lot about for like the last two weeks. So,swyx: but when they say user friendly, it's like, oh, it's the dumb down version. But no, actually this is the superset.Felix: Yeah. Like, I think a similar thing happened, A similar thing happened to me about 10 years ago, like maybe 12 years ago when I was at Microsoft and we started working on, on Electron and like browser-based technologies and cross-platform stuff.And one of the first use cases was Visual Studio Code, which used to be a website. And the initial narrative was, or Visual Studio Code is, is like a more user-friendly version of Visual Studio. But in a similar vein, I think there was some voices saying, oh, this is. For serious developers, like, we're not gonna use this.Right? For like anything. And I think in the end what happened is people have different stories about why Visual Studio Code became such a big thing. But my personal, my personal belief is that the Hackability and the extendability has like played a pretty big role, right? You can hook in Visual Studio Code that like almost any workload, it's so easy to hack on, so easy to put extensions for it.And I think cowork might be hitting a similar thing where it's very easy to extend and it's very easy to bring into your workflows. Uh, so the convenience I think is a bit of a, it's obviously the thing we strive for as developers, but I think the way people find value in it then is by probably mapping it onto whatever they actually have to do in their job.Alessio: So end of last year, you see the spike of like non-technical usage and clock code. What's the design process to say we should make clock code work? Because I mean, you built it in only 10 days. Um, I'm sure there was some discussion before on whether it's easier to use mean. You know, like making, making like a desktop GUI is obviously one way to do it, but like there's a lot of nuance in the product.Like maybe talk people through what was like the trigger of like, we should build a separate thing. We should not build like a different plot code thing. And then maybe some of the more interesting design decisions that maybe you didn't take.Felix: Yeah, I think philanthropic, we've been thinking about ways to move people who are comfortable with using Claude to answer questions and bring more of the power of like this thing to now like, execute tasks for you.I can like solve problems for you can like build things for you. How do we bring that capability to people who are currently mostly comfortable with like a like question answer paradigm within the chat. And we've had a lot of prototypes around that. Just going back as far as like easily a year and a half.Like we had a lot of people working on that. Um, and internally philanthropic is a very prototype demo, first culture. We have a lot of like internal prototypes that don't reach the public. What Cowork actually became is like we sort of picked the right pieces out of the many prototypes that we had.Right. And that's, that's maybe also like, I think an important qualifier whenever people mention this like 10 day number. I do think it's important to me to mention that within Double Scratch there was like a lot of stuff already happening, right? Like, and I think it's important for people to remember that when you build a website, you use React, you use like a bunch of other things.And this is like a similar scenario with like a lot of pieces we already had. Um, and in terms of decision path, I think we live in like an interesting new world where execution is actually quite cheap.swyx: Mm-hmm.Felix: So maybe, maybe what you would do That's so crazy. The year. I know it's wild.swyx: You should be, ideas are cheap.Execution is the hard part. IFelix: know. And like the, we, we used to live in this world maybe where you would take a product manager and the product manager would go to a number of potential customers and in this like very low bandwidth way, would try to. Try to like tease out what are the problems they're having, what are they willing to buy?Um, and then maybe what can you build to like drive out that need and then you go back and you like draft a spec and you think about it and then like you make a design and you execute it. We internally philanthropic app, not pretty much closer to the point where we're like, don't even write a memo, just like build, like let's build all the candidates very quickly.Let's just build all of them and then pick the best ones. I think the, the decision that is most impactful both for the product as well for the users right now is like the way we put value on your local computer. I think that's a big decision point a lot of people have thought about. Should this thing, whatever it is, should it ultimately run into computer or should it run in the cloud?‘cause they're big trade offs, right?Alessio: I guess like if we solve auth, it would be easy to do in the cloud. But I think like the fact that I can just download any file from anywhere and then put it and cowork there, it's like a big unlock. Um, I mean it's interesting you mentioned reusing certain pieces. I think this is something I've been thinking about even with Claude Code, right?The price of like writing code is going to zero, blah, blah, blah. But it actually seems like the value of having some sort of platform substrate is like increasing because as you build these new things, you can kind of plug them together.Felix: Yeah.Alessio: So I almost feel like when people are saying, oh, the value of a lot of software is gonna zero because you can recreate it, to me it's almost like the opposite.It's like having an existing platform to build on top of. It's like even more valuable because you can kind of bolt things on.Felix: Yeah.Alessio: You have obviously mcps, you have skills, you have like obviously the models, which is a big part. All these things kind of come together. Do you feel like that's a valid way to think about it, where people should invest even more in kind of like primitives.To rebuild on or are you like recreating a lot of it each time because like things change and it's easier to rewrite than reuse?Felix: You know, I think, I think you're right. I think you're right that the holistic platform is really useful. And this is maybe a whole like a somewhat contrarian view to a lot of people in ai.I actually don't think that the future is going to be hyper personalized software down to the point where everyone is running their own version. Like, I actually think it's going to be quite hard for all of us to have our own internal chat tool and like, if I wanna talk to you, likeswyx: howFelix: is that gonna work, right?In the, in the context of cowork and how we build it, I think it's a bit of a combination. Like what the, the execution that gets cheap is not necessarily rebuilding all the primitives. I think our priori, there's also not a lot of value in it. So for instance, my team did not think about rebuilding clock code.We're like very much started with the. The core thesis of this should be Claude Code.Mm-hmm.Felix: And then we'll like build things on top of it. The part of the execution that gets a little cheaper is like, how do you take all of these Lego pieces and put them together in a way that makes sense for users?It's like actually valuable. You have so many different approaches now in terms of what kind of, what kind of things do you actually elevate to a primitive, do you strongly believe that all your products should be built by just combining primitive that the public also has available? Do you keep some things internal?Um, and I think that's still evolving, but I think what's probably gonna go away is like, I'm not sure if it's gonna fully go away, but I'm gonna say, I think for me personally, I will probably no longer try to come up with a really good product without testing up with people. This is not a new concept, but wherever you used to have to make costly decisions around, do we pick technology A or technology B, or do we like, um, build it this way, build it the other way.I really strongly believe now you just build all of them and try them out with a small focus group and then whatever, whatever is better is what you go with. Right. And that, that is probably quite different even from how we maybe worked a year ago. Right. Like, I think, I think this happened very recently.Alessio: Yeah. I started building something in on Electron since you're here. Coincidence. Uh, but then Electron and like SQL Light are like, there's like some issues that like between development and like, uh, building anyway. And I was like, let's just rebuild the whole thing in Swift and just recreated the whole thing in Swift.And it's like, I. It's done.swyx: You know, I didn't take any effort. I, I, I don't even know Swift.Alessio: Yeah, exactly. I was like, I'm the, I'm not reviewing it anyway, whatever. You can write in whatever language you pick, but the important stuff that I did was not write the electron bindings. Yeah. It was like the logic of what happens in the app, you know, and then the model is like, yeah, I can just recreate the same thing as withswyx: Yeah.I, I think you still want, especially for people who are doing like high performance software or like very complex software, uh, you still want like, some view of the architecture. Uh, but you can use markdown for that,Felix: right? Yeah.swyx: Uh, you don't actually have to read the code again. I, I'm still like on a sort of like a definitional thing.Um, can we build a good mental model of Claude Cowork? Um, this is what I have, right? Like you you said it's like fundamentally cloud co. We don't wanna touch it. There's the cloud app, there's clouding Chrome. I think you guys do something different in planning, but, uh, I've been talking with Tariq who is on the cloud co team, and you guys are, he's like, no, we just exposed planning.Maybe we can clarify like, what are the major pieces. That people should be aware. It goes into cowork, like,Felix: okay, I think you basically have them. So really, um, you can, you can take planning more or less out. I think there's a few things that are really valuable in cowork. Um, the virtual machine is probably the most powerful thing.So we currently run like a, we currently run like a lightweight VM and we put clocked out into the vm and we do that for, for, um, a number of reasons. Safety and security is a big one, but even if you, even if you ignore for a second safety and security and you're just like, okay, Yolo, I want this thing to do whatever.It is quite powerful to give Claus on computer that is like generally a good idea. And in terms of architecture and UX and everything else that we've been working on, philanthropic, it often is quite useful for you to like anthropomorphize, um, clot aggressively and just be like, this is a person. What will you do if you give a, if you had a person, right?Yeah. And the analogy I've given my dad this morning who is still like quite insistent on using chat even for like coding things, is if you were a developer and your employer told you that you don't need a computer, they're just gonna like, send you emails with a code and you send emails with code back like that, maybe work for Patrick Miles in the back, but that it's not very effective.Um, so what we can do with the VM is because it's a, it's a Linux system, Claude Code has more or less free reign to install whatever needs to install. It can install Python, it can install no js. We do have strict network ingress and egress controls. So you can still, as, as a user in like plain human language, make it clear to, to the entire system what you're okay with and what you're not okay with.But at no point do we have to ask a real person, like a, like a person who might be in marketing or a lawyer. I'd have to go to a lawyer and be like, are you okay with me installing Homebrew?Alessio: Yeah, yeah.Felix: Right. Because the implications of the question and the answer are complex and nuanced and like, not, not easy to reason about.This gives us a lot of distraction that makes Cloud very powerful. Now then around it, we, we do probably have a number of things that also keeps growing almost every single week that you're probably noticing that make cowork maybe better for certain tasks than just cloud. Cloud on its own. Yeah. But most of those actually live in the system prompt.They're about like, what can we infer about the work that you do? What can we, what can we intru in the system prompt to make that more effective? It's of course the like very tight integration with Cloud and Chrome. You're noticing that a lot of people, especially as the models get better, a lot of people throw up their hands when it comes to MCP connectors in this area.I'm not gonna, I'm not gonna go through like 25 M CCP connectors, click off everywhere and then like half of them don't let me do the things anyway. So Cloud and Chrome is quite powerful because we can just talk to the cloud and Chrome sub agent and that will just do things for you.swyx: Yeah, so, so one example right in MCPI, honestly, I think that the state of MCP is kind of, kind of.Really hard to integrate. Um, I need to, I needed to add, uh, Figma MCP to the coding agent that I use.Felix: Yeah.swyx: Uh, and, but I didn't wanna read the docs, so I just had caught to it. And it's, it's great at reading docs and the same, same way I had to set up like a Google Cloud, um, account for some project I was working on and get some API keys somewhere.And Google Cloud is famously super hard to navigate, so I just didn't wanna deal with any of it. I just used Claude CoworkFelix: within the first week of developing on Core. This happened very, very quickly. Um, I caught myself by starting to use cowork for coding tasks, which is not ostensibly what we built it for, right?We don't need to. But I found myself, um, I found myself like on our internal, internal tool that we have for, to collect crashes and just like debugging information and I found myself sort like picking out the ones that I think we can easily fix versus the ones that might be like kernel corruption or something else on the operating system.And I found myself sort of picking these out and then just telling Clark, go fix this bug. I was like, what am I doing here? Go one level up, tell a cowork, I want you to go to all these crash tools. I want you to find all the bugs that you think are fixable and not like an operating system crash. And then I want you to tell another cloud to like fix all of that.Um, and that's, that's, that's sort of another cloud,swyx: just so it can spin up another instance or,Felix: uh, it, currently what I do is, um, and this is a bit of a hack, but I tell it to use clockwork remote to which website itself? Yeah, that's interesting. So you basically take, if you, if you imagine like a dashboard with like 20 bucks, you, this is remote control or clock or remote, or, sorry, I just wanted to confirm what, the way I'm using it is.I have cowork running and I'm telling cowork, here's where I normally go every morning to find the latest bugs. Go read the entire bug list, separate out which ones are fixable, which ones are, are fixable, and then for the fixable ones, four is this almost loop. For each bug, write a markdown file with a prompt.And then for each markdown v, that is a prompt. Start of a cloud set. So natively Claude Code hasswyx: this concept of subagents. Mm-hmm. And this is basically a subagent, but you're not using the subagent functionality.Felix: I'm not using the subagent functionality. And the reason I'm not is because I'm firing that off as a Claude Code remoteswyx: task.Felix: Yes. That's kind of nice. ‘cause then I can just fire it off. I can go to my next meeting and in Claude Code remote. Now the work is happening.swyx: Mm-hmm. Yeah. You, you see like you're already starting to use the cloud over your local machine. And I think this is one of those things where like. Shouldn't just everything just be cloud first, right?Felix: Ah, this is such a good group. I'm like solely bad about this. I have so many thoughts about that. Okay. So I generally believe that Silicon Valley overall is undervaluing the local computer. And my default argument for that is always how come we're all using MacBooks and not like an iPad or a Chromebook?Um, that there is like still value in, in having a local machine. And now when I think about Clot, it's this entity that is supposed to be very useful to you, like it tremendously useful to you. I think that entity needs to have access to all the same tools you have access to. Otherwise it's gonna be hamstrung in like all these complex ways.And there's, there's sort of two approaches we could take. We could say, okay, we're gonna like one by one chip away at everything that is at your computer and move it into the cloud. That's, that's one way to do it. Um, and I think other products have taken that path. I personally, this is a very personal opinion, but I personally, for the amount of tools that I use.Just don't have the patience to give another tool like permissions to every single thing and keep those permissions up to date. The second thing that I'm still grappling with, and I don't have a good answer for anyone just yet, but the second thing I'm still grappling with is what does it look like for someone to slurp up your entire work and put that in the cloud?Like if I, just as an example, like if you could click a button and it just clone your entire computer into the cloud, is that something that you would want? I'm not totally convinced yet that all everyone will. Mm-hmm. And that is sort of like upstream of all the technical issues we're gonna have. ‘cause like in general, I think the world is not ready for this kind of stuff.Like, I'll give you one quick example that would probably be very easy for us. So as a desktop app, we in theory with your permission, can do a lot of things on your computer, including reading your Chrome cookies. If we really want to do right, we could take your Chrome cookies, you would have to decrypt them for us.We could put those on the cloud if we really felt like it. Pretty easy solution. That would be super cool. We could just be like, oh, we can do all your tasks in the cloud now. Um, a lot of websites, thanks, include it. If, if they see the same authentication from like two different locations, we'll just lock down your account and now you have to go to the branch and be like, okay, I, I'm here with my passport.You actually know that. Wow. Yeah. As tired as well are of the term agent for the age agent future, I think there's a lot of stuff that sort of slowly needs to catch up and until that's the case, the way I, as someone's working on clock and make Cloud most effective is to like put it where you are working.swyx: Anything else? I thought with our mental model, so like, basically like, uh, part of me also just want, like the more I understand how it works, the more I can use it to its full potential. Right?Felix: Yeah.swyx: And so what I'm get hearing from you is you told me to delete the planning thing. You're not doing anything special on, on the, that's only exclusive to Qua cowork.Felix: We have some tricks for this sort of like change week over week. We eval cowork maybe against different use cases than he would evil clock code, right? If you think about it this way. Okay, so like clock code is our eval clock cowork. Yeah. So clock code is like quite optimized for coding tasks and we mostly value it whether or not we're getting better or worse depending on how good it is at like a typical suite job.And Clark Cowork on the other hand, we evaluate more against typical knowledge work, the kind of stuff he would find in finance or in like maybe a, like in like a legal office. Um, my personal use case is always like managing my things, like managing my personal mortgage or something like that, right? Or like wealth planning for me and my family.Those are the kinds of use cases we eval, clock cowork on. And what you might be picking up on is like the subtle changes we make to the system. Prompt what we put in the system, prompt how we steer, clot with the tools we give it. Um, like either it'd be better in one or the other direction and whether there's a trade off, try us exist a lot.CLO code will be better of a code and Claude Cowork will be better. For non-coding tasks, will those gaps still exist in the next three generations of models? It's like a little unclear to me though.swyx: Yeah,Felix: because right now these like hyper optimizations we make, I'm not sure for how long they're still be relevant.swyx: I think what I was referring to was also, it, it just, uh, it qualitatively felt different when I probably, it's just all prompting and I'm reading too much into it, but like the, the fact that it comes out with like a nine step plan, I can edit the plan and give feedback and, and, and see it execute the plan.Yeah. It felt more long range than in Claude Code, but maybe that already existed in Claude Code and you just build a nicer UI for it.Felix: It's kind of both. Um, like if the Clark Code people who build the planning functionalities would city, they probably say yes, we have all of those things in Clark code and they do.Um, I think people tend to give cowork. Tasks that are maybe of longer time horizon, I thought isswyx: so long. Yeah.Felix: That's like one thing, right? It's just like that the, the chunk of work tends to be maybe a little bigger. And then the second thing is that because the work, when it gets longer, it gets a little bit more ambiguous.We do tell co-work to make heavy use of the planning tool or to make heavy use of the ask user question tool, right? We do want it to come up with like. Different scenarios of, okay, tease out what the user actually wants. Don't go off to work for like four hours and then come back with the wrong thing.And you're probably picking up on that.swyx: Yeah.Felix: Um, I wish I could tell you I like built this magical thing and it's like, there's some secret sauce,swyx: but No, no, no. I mean, it's, it's just clarity is good that, you know, engineers just want to know. Yeah. They can, they can plan around it. And then I think also for me, um, I am realizing I have to switch to my, my other machine because this is a new machine that doesn't have my session.But, uh, yeah, the, the, the planning is really important for, for me to like approve or like to see whether it's like, it's right. The ask is, the question is so beautifully presented. I mean, it also, it also available in like cursor and, and in Claude Code. But like, I, I think like it's so nice to see that it, like it's kind of for me like to understand that it gets me, it gets what I want to do.Felix: Yeah.swyx: Yeah.Felix: It probably very hardswyx: just on the topical evals. Mm-hmm. When you say eval, I think people are very vague about what it means. Is it just like vibe testing or do you have like automated programmatic evals of Claude Cowork?Felix: When we say eval, uh, what we really mean is that we essentially take the entire transcript, including all the tools that clot has available ultimately to it, and we then measure what are the outputs, depending on what we tweak, right?So we do run that a lot. We use that in training. Um, we use that in, in like, if you sort of separate out post training from like the scaffolding around it. Cowork sort of exists in the scaffolding space, but obviously we also train on it a little bit. Um, so when we say eval, we mean given the certain transcript, what do the outputs look like?Including the file outputs as well as like the actual token outputs, like the ones that you see in the chat window.Alessio: I'm curious, um, how much of the failure modes are the model intelligence versus like the usage of the end tool to put the intelligence in? Like the well planning is like a good example, right?It's like one thing is to come up with a plan. The other thing is like make a nice spreadsheet. Yeah. That kind of runs you through the plan. Like how have you seen that? Well,Felix: the thing that I grapple with a lot is that whatever scaffolding you come up with, I think we still have a bit of sort of like model overhang where the model is dramatically more capable than right.Users end up using it for. And I think part of that is that we're just not getting the model all the tools to do all the things that's theory capable of, right? There's like one thing, um, however, whenever you do build the scaffolding, I'm sort of wondering at what point, at what point will that scaffolding go away and like how much you invest in figuring out what the right scaffolding is.It's kind of up to, it's a little bit of a bet. And one thing that I as an NJ quite enjoy is that like working in philanthropic and working at a frontier lab, I maybe have a little bit more insight into what's coming, coming down the chute in terms of like, what's the next model, what is the model capable of?What is good at, what is it bad at? And I'm, I'm increasingly wondering, is the right thing for us to like really invest too much in sort of these like scaffolding corrections where the model might otherwise not misbehave, but just not do the thing that you want?Alessio: Yeah.Felix: Or is it to just like give it as many capabilities as possible, try to make those safe so there's the worst case scenarios, likeno status might be otherwise.And then just simply wait a second for the next model drop. I'm personally, currently more leaning into the ladder. I think we're gonna see a lot of like applications and companies that do very impressive things with ai that in the short term might seem very effective ‘cause they're very specialized to individual use cases.But I think once models get better generalization and get better at like those specific use cases without being super guided on those, I'm not sure how long that's gonna stick around. And you can kind of, kind of already see this in like skills and NCP servers, right? Mm-hmm. We've, we've already seen sort of this like slow shift from MCP service to skills.And like, maybe a good example is Barry who made skills. He was initially hacking on something that honestly looked a lot, looked, looked a lot like what Cowork does today. It was sort of thinking about what if cowork, but for like people who don't wanna build code. Mm-hmm. And, um, he too did that as a prototype inside the desktop app.One of the first use cases we thought of were, okay, what, what are like coding like use cases that could really benefit from graphical interfaces and like from being a little separated from the actual underlying code. And everyone comes with the same answers. Data analysis,Alessio: right?Felix: Yeah. Or saying how many users do we have today?How many, like, it's always data analysis. And I think the thing that ultimately led to skills is that we wanted to connect this little prototype to our data warehouse and. The team very quickly discovered that like instead of building a custom tool for the thing to talk our data warehouse, they just like meet and embarked on follow like mm-hmm.Dear Claude, if you want to get data, here's the end point. Here's what the API looks like. You'll figure it out.swyx: Ah.Felix: And then it be hand over control. Yeah, yeah. Also just like maybe go one step up in the layer of abstractions, right. Just, yeah. Instead of, instead of telling the thing, here's ACL I, please call the CLI, or here's an MCP.Please call this ECT shape. Just like this is the end point. If you wanna know something, if you post here, maybe you can do post sql. It's gonna be okay. And that ended up being so effective that they started trying the same pattern of like just giving the model a markdown file that describes whatever it needs to do.That the whole thing eventually became skills and we're like. We should package this up. This is a good idea.swyx: Yeah. Um, we've had Barry Mahesh, uh, on, on our conference and uh, he's uh, definitely got a good idea there.Felix: Yeah.swyx: I wanted to show you the, how I've been using Claude Cowork.Felix: Uh, this is was my favorite part.swyx: This is this. So this is like me, uh, this is how we run the Discord. Uh, we literally, uh, at first I didn't trust Cloud Core. This was my very first usage.Felix: Okay.swyx: Right. So then I was like, okay, I will just try to manually download from Zoom all my recordings and upload it to YouTube. Yeah. Because this is a very laborious process.I got a click, click, click YouTube, um, isn't super user friendly. Uh, and it just did it. And then I was like, actually, you know, even the download from Zoom part, I should also. Put into Claude Cowork, and then I did it right. Here's a bunch of, and it starts compacting here, and it, and it, it starts to even be able to do things like look through the individual frames of the video to name the video so I can upload it auto automatically.Oh, that is, and this replaces my job as a YouTuber. We will forever appreciate your creative Yes. You know, and so that's great. Uh, but then by the way, it compacts and makes, makes like a new thing, right? So I, I don't, I don't have the initial, initial thing, but then I asked it to make its own skills so that it, so that something that's repetitive and one-off and human guided becomes more automated and I can use the skills independently and reuse them.Uh, and it obviously you can write skills and that goes into context and skills at the bottom here, which is, which is so nice. Um, so I have all these skills that, that I now sort of do on a weekly basis. Uh, I know you've released scheduled Coworks, which I haven't done yet, butFelix: course I should try them. I, I think this is like so wonderful and fun for me to see because.One thing that is very fun for me about skills in particular is that they're so easy to make. Like anyone can make a skill, like a text message, could be a skill, and they can be so hyper personalized to you. And this is like sort of the subtraction layer, right? Like, um, I, I'm just guessing, but I assume, heck, you are very good at your job.You're probably given this thing some guidance about how to do it, right? I,swyx: I just said, wrap everything up into, into a skill, right?Felix: Yeah.swyx: And then, uh, and then I was like, actually, sometimes I might need to break, uh, things apart because some parts fail or some parts might be needed in individually. So I told it to split one skill into three skills.So it's like a skill splitting thing, and then there's like a parent skill that just orchestrates all of them if I want to use that. You know, like, um, I think that's, that's like really good. Uh, and, and, uh, there's, there's one more part, which is the, uh, Google Chrome thing that I told you about.Felix: Yeah.swyx: Where I'm like, okay, you know, what's better than uploading, using Claude Coworks to YouTube?Like actually. Looking at the docs to like programmatically upload to YouTube and then putting that in a skill. And I've never done that before. I don't want to deal with Google Cloud. Yeah. So Claude Cowork does it for me.Felix: That is really cool.swyx: So, so I, I just, I don't care. I just, like, I do a thing. I don't, it doesn't really matter.Felix: That is really cool. And then you've, I assume paired the skill just with the script that it's built.swyx: Yeah, no, I just update, update the skills.Felix: Oh, that is beautiful. Yeah. That's wonderful.swyx: It's kind of like a skill, like, uh, uh, basically I think like the way that people ease into Claude Cowork is like take a knowledge work task that you would normally be clicking around for and then, uh, try to turn, turn that, and then you do the, okay, well what if you went further?Okay. And then when, if you went further, when, if you, and it sort of expand the scope of cowork as you gain trust with it and, and also teach it how to replace you.Felix: Yeah. It's like a little bit like playing factorial, but for your own life. Uh, like you say, you start really small.swyx: Yeah.Felix: You start automating something really tiny and like.Once it clicks, you keep adding onto this like automation empire. Just like make your life easier and easier. My favorite skill has been, um, every single morning Kohlberg starts looking at my calendar and make sure that there's conflicts because people tend to schedule a lot of meetings, sometimes last minute, sometimes miss it soft and painful.And a lot of products have existed like that A lot. I've written in the custom prompt there. I haven't made it a skill, um, honestly should.swyx: Yeah.Felix: But I've given it like pretty clear instructions about okay, here are some people, if they book over other meetings, I'm probably gonna go to their meeting. Like if Dario schedules a meeting.swyx: Right.Felix: Not try to reschedule down. Right. Um, and I think there's some other rules in there about like what kind of meetings I care more about what kind of meetings I care less about. What is okay to like, maybe pun like when I want to be, when I want to be working, when I don't want to be working. And it's those really small things that I can think kind of click with people.Right. When we launch co-work, I think one of the US races that went most viral on Twitter. X was clean up your desktop, which is stuff, because silly, that's such a smart thing, right? Like you don't need to model to clean up your desktop. Not really. Um,swyx: like this, like clean up my desktop.Felix: Yeah, exactly. Yeah.swyx: I need to, I need to choose my desktop, right? I guess give it access to my desktop.Felix: Yeah.swyx: Okay. Uh, okay. This is very scary. Oh, we'll do it.Alessio: I did, I did it with my downloads folder. It was like, you have so many term sheets and there's like eight copies of your rental lease for your office. I was like, all right.Like, don't yell at me.Felix: It's like, it's not such a small task. And then like, I, I would never go out there and normally otherwise and tell people I've pulled a product. It can organize your folder. Right. Um, because it feels small. But I think to your point like,swyx: oh, here's, here's the, here's the ask user questions.Felix: Yeah.swyx: Uh,Felix: beautiful. Right. Elite obvious junk. You probably shouldn't click that.Alessio: No.Felix: If he's not done right.swyx: As long as it's reversible, I don'tAlessio: make up blend to,swyx: yeah. Uh, yeah. No, I, I have a, I have a typical, everything is super messy folder. So, yes. I think this, this is super helpful. So this is a pretty simple task.Mm-hmm. But I've, okay, here it is. Right. Here's the progress. I don't see this in, that's why I'm like, this gotta be something different than, uh, than Claude Code, because I'm like, weFelix: do. Yeah. That's, we do system prompt that. We're like, all right. We want you to think about like, this task Yeah. Methodology.Yeah.swyx: And then I can, I can, I can do like little suggestions for, for, for these things. It's beautiful. Look at this. I, I can, I can like say like, oh, don't do that. Don't do this. It's amazing.Felix: I'm so happy. You like it. Um, I mean, the other way around, like we're part of the Clark core team, if you would like this in Clark COVID.swyx: Yeah. Yeah. Yeah. Uh, so, so yeah, I mean, uh, this is really good. Obviously I, I'm like kind of raving about it. Uh, you know, I have other things like sign up for pg e so if you can do phone calls for me, that'd be great. Um, I, I do, peopleFelix: have done that. Obviously you can't do that natively, but people have done that with like, various other providers.swyx: Yeah. Uh, and then this is like signing up for the Figma MCP. Um, I, I really am trying to do like everything, um, data analysis as well. I do think, um, oh, design to code, uh, very, very good. Right? So like, here's a Figma file, take it. And then this is where like a lot of other tasks is like knowledge work, like replace my manual clicking, but this is no, I would normally use Claude Code or uh, Claude Code for this, but because I perceive that you have better Chrome integrationFelix: mm-hmm.swyx: I, I think you can actually do a better job of this. And I, this, this is one shot at my, uh, conference website.Felix: That's pretty cool. Like at some point I would love to like, hear how you feel about code. In the desktop apps, which is like I never use, which is the, the same team. Same team.swyx: So I use the call code in terminal, which I, I perceive to be the default way of cloud coding.Felix: So one thing this has,swyx: sorry, I'm just like, I'm notFelix: here, I'm not here. All products. Can I talk about other stuff? Like I, I'm not sure if people out there wanna like hear me advertise my stuff for like an hour. Please do that. Um, this thing is like a builtin browser, which is a thing a lot of products have said.Yeah, it's a builtin browser. And I think giving cloud eyes into like what you're actually working on makes it so much more effective. And that's probably what you've seen in cohort because it can see Chrome, it can like debug the dom, it can like see things. Um, that does make it more powerful.swyx: Yeah. So, so I think, uh, my mental model was kind broken.‘cause I only use this cowork because I thought it had a, a browser thing in it. But I understand that the Claude Code app. The app version of Claude Code does have a built-in browser. I've seen, I've seen this preview thing.Felix: Yeah.swyx: I just, I've never used it.Felix: But in the end, in the end, you sort of have it by hard.Yeah. You basically get the same thing. Right? Like the, the, the additional skill that you're describing is chart is better if we can see what it's working on. Right. That's, that's sort of like the summary here and like whether it's using your Chromeswyx: Yeah.Felix: Or it's just like making up its own little like browser.It doesn't really make a big difference because either way it's gonna see what it's working on and that just makes it much better. And then you don't have to run QA for your cloud.swyx: Why doesn't it pick up my existing Claude Code sessions? ‘cause I, I mean, obviously I've used Claude Code, but Excellent question.Um, don't have a good answer other than like, we're honest. Just haven't Yeah. This is what the Open AI team does. Okay. Uh, cool. I I I don't have other, like, I, I just, I, I do wanna expand people's minds and also maybe show people if they haven't really done it, but like, I, I think it's very interesting how I sometimes use this more than I use, I mean, I use dia, right?Yeah. Um, I, and I use, uh, I've used like all the other agentic browsers and philanthropic didn't have to build an agentic browser because you just had Claude Cowork and that's enough.Felix: Yeah. I also think like maybe integrating with number of excellent browsers out there, it's like currently on my personal priority list, a little higher than like trying to rebuild a browser from scratch.Yeah. You know, never say never, but I think going back to this idea of like, we wanna plug this into an entire existing workflow, I think our goal is actually to not replace any of the applications we have in your computer. But instead of like, work really well within a new workflow,Alessio: make the new one. Yeah.Are, it seems that nowadays, especially on the browser, most of the innovation is like user ergonomics. It's not really like the underlying browser engine. So I feel like to call it, it doesn't really matter if it's like the, uh, or Chrome or Alice, whatever.Felix: Yeah. We wanna, we wanna meet you wherever you are.Which is like, like obviously I would say that, but it's also just generally true because I don't wanna shrink my potential user base artificially by saying, okay, like, I'm gonna start building for the people who are willing to switch browsers.Alessio: Right.Felix: That's such a, like, you know, like many lawsuits have been filed over who gets to review the browser and like a lot of money has switched hands over the question of like, which browser is default and which search engine is default within the browser.Um, I just wanna build for, yeah, I wanna build for swyx essentially. Like, I wanna, I wanna, I wanna build for people who have a number of annoying tasks that they feel like. Maybe clock could do it. Could do it for them.Alessio: Yeah. What do you think about skills portability? I think there's been one thing, I use another thing called zo, which is kinda like a cloud computer plus agent.And I have a skill to add visitors to the office. Yeah. So whenever somebody has to come in after hours, they need to check in downstairs. Um, but I wanna like text the thing, so it doesn't really work in, in cowork, but now that skill is in the zone harness and it's not in my cowork thing. And then if I make a change, it's gotta, I gotta sync them.How do you see that going? Like I see memory as like. Cloud personal, kinda like, I don't necessarily want my memories to be cross thing.Felix: Yeah.Alessio: But I do want my skills to be cross agent that I use. I think with MTPs, people do the same thing. It's like, oh, Mt. P Gateway. Mt P registry. I don't really know if that's like a business.So I'm curious like if you've had any thoughts in the area.Felix: I think for me, this is sort of where I go back to the really basic primitives for our skills are file-based instead of like this complicated thing that exists inside a place somewhere that is like super proprietary. I'm really leaning into the idea of like, it's all just files and vultures, and that makes it very portable on its own.Right. We do have skills as part of this container format, which was just called plugins.Alessio: Mm-hmm.Felix: And plugins are available both for Claude Code and Claude Code work the same format, and you can install plugins. This works in cowork today. You can basically say, I'm gonna add a whole, like just a GitHub repo as a.Skills marketplace or like a plugin marketplace. And that's how we're doing portability. I think we have a lot of room left to grow in. How do we make it easy for people to know that they can write skills? How do we make it easy for them to just like, share a skill with you? Because obviously all the words I just said, right?Like I'm losing most of the knowledge worker base out there, right. And start by saying, oh, you can connect to GitHub repo. It's not exactly how most people will end up working in like a general knowledge worker space. Um, but I think there's something there. And another thing that's there that I think has not really been properly explored is the, the, the combination of which part of the skill is very portable and then which part of the skill is like very personal to you.Right. And I think that's something we haven't really solved as an industry. Hmm.swyx: It's like, which, how you wanna introduce more structure to the skill or have always have like. Public skill, private skill, you know, pair. Yeah, yeah. Kind of. I think there'sFelix: like a, like the easiest way to do this, which is we do like use string interpolation or something.Right, right. Yeah, yeah. Insert username here, insert like phone number, insert, like known folder, locations, that kind of stuff. Um, that's probably clunky. That's why we haven't built it. Um, but I do think someone is going to come up with like an interesting way to keep everything we like about skills. The portability is just a file, it's just marked down.It's just text, honestly. Right. Like a text file words. The complete lack of structure, which means you don't need any kind of tutorial to write a skill. Just like explain it to Claude the way he would explain it to me and Claude will probably get it before I work. Mm-hmm. Right? You're just like, for booking a flight, tell Claude how to book a flight the same way we tell him somewhere.I just started working here today. But combine that with a very like, personal thing. Um, maybe we'll stick with a booking a flight example. I don't actually think. AI should be booking flights. I think the tools we have is yes.swyx: Yeah. Finally, somebody says it. It's the default demo that everyone's making.Felix: I'mswyx: like, I even against like booking demos, it is not a good showcase.Felix: Yeah. I'm like, I just wanna book my flight myself. But, um, I think there's a lot of things that have a personal and a non-personal component and that's maybe why people reach for flight booking because some things are very universal. Yeah. Super flight is usually better, right? Like few people try to book the most expensive flight.And then some things are quite personal about like what times you prefer, which seat you prefer, which airports you prefer. Combining that and like a skill format that is actually portable, compatible, easy to understand for people. I think that would be very exciting. We just haven't figured it out yet.Alessio: Yeah, I think the text part every, I think everybody by now has some sort of like cloud file thing. Either Dropbox, Google Drive, whatever. So it feels like in a way it should basically like sim link. My skills into all my agent harnesses. Yeah. Just keep those ing like we have internally this like valuable tokens repo, which is like all the commands sub agents.It's good. Uh, and then I build like a TUI where you can start it and be like, you know, install this command and this three sub agents into this agent in this folder and just copy paste this. It doesn't do anything. It literally cp the file into that. But I feel like there should be something similar where like whenever I go into a new thing, it's like, hey, here's like the link to exactly the cloud folder and just bring down these skills into this.Yeah. Like today it doesn't quite work like that. Like if I install a new agent, I cannot, I have to like copy paste all the skills and I don't even know where they are.Felix: Yeah.Alessio: That's like the big problem. It's like where do I find them?Felix: Yeah.Alessio: Um, so I'm curious like in the future like that, that almost feels like my personal productivity thing will be my skills.Felix: Yeah.Alessio: Is not really the product that I use. Everybody has access to the same product. But today there's, that just looks like copy pasting ME files, IFelix: think so many things I, I really like thinking about agents and LLMs just as like another coworker. So many attempts have made to build documentation companies that are like, oh, we're gonna solve oil documentation problems.Um, I myself, like spend a little bit of time working in notion, right? I'm like deeply familiar with the concept of let's get everyone on the same page. Mm-hmm. Right? And what you're basically saying here is you want all your agents to be on the same page about your preferences, about the skills, about the way they ought to work and like how they ought to execute.And I'm not sure what the right thing is going to be if it's going to be some, some company that can say, all right, we're as an independent body, we're not trying to like, push into any particular product. It's our job to be like the skill authority, and we provide, I don't know, we're gonna be the Dropbox of skills and we can just sim link us into all the products we want to use.I'm not sure that's gonna be viable business, but as, as an idea, it would be cool.Alessio: Yeah. Yeah. I think so many things are just going away as businesses. It's like, how am I supposed to do it? I'm not even asking somebody to make a product about it. Like yeah. I wanna personally know. And there's things like you said, it's like you almost wanna skill and then interpolate it between personal and work.So if I'm booking a fly for work, it's different than I'm booking a flight personally.Felix: Yeah.Alessio: In some ways, yeah. But like a lot of the scaffolding is the same, you know? Cool.Felix: I mean, as an engineer I will tell you like, you know, technic a person to technic a person. I will just be like siblings.Alessio: Well that's what, that's what I do.We call that MD and agents that MD's just the same how sim length. And so it is like, that works, but it feels like, yeah, I don't know. MaybeFelix: you can always go one, you can always tell cowork problem and then cowork will solve it for you. Just make the siblings. That's like one way to do it.Alessio: That's true.That's true. All right. Everything is called cowork.Felix: Uh, potentially spicy. Question for both of you.swyx: Uh, which of these industries will go away?Alessio: Okay, so what Felix was saying before is interesting. There's busy like. The short term pressure of like, we need to turn these tokens into valuable things, which is I should build the last mile product that harness the model.And then there's the question of like, long term, which ones are gonna still be valuable? And I think you're kind of seeing this today with like, uh, you know, the coding space in a way is kind of like everybody's moving up and up in stack because you need more than just turning tokens into code. I think search, like enterprise search is kind of saying the same thing.Like with G Clean and like all these different companies is like, at the end of the day, if Cowork is the one doing all the work, the search itself is like such a small part that like, I don't know if I'm really gonna pay that much money just to do search. It's almost like everything is like a cowork vertical.So like how much can cowork first party support?swyx: Mm-hmm.Alessio: And how much can it not? I think for a lot of these things, the planning thing that you were showing do Which one? The planning. The planning.swyx: Okay. Yeah. Yeah.Alessio: That's one thing where like most of the value that these agents provide is like they're better at planning for specific tasks.Yeah. And have better tools for it.swyx: Yeah.Alessio: But I think the models are now moving in that direction and they have the right harnesses and they're on your computer. So for me it's almost like if for the end customer trusts your startup to be the provider of that task result, then I think that works. This is, uh, something that, this is a shortswyx: spike that we're, we're working on.Uh, yeah.Felix: I think, look, I'll, I'll, I'll tell you this, like I don't think I'm the best person to like actually estimate which industry is going to be hit the hardest. But I do think that at philanthropic as a group of people, we're deeply worried about the impact. That the tools are going to have on the labor market, especially for like junior employees that, because I think, I think it's only honest to say that when we talk about automating a lot away, a lot of the work that we personally find annoying that we maybe think's not the best use of our time.In a lot of industries, that kind of work would've been given to a junior entry level employee. Yeah. Right. And I think it's, it's only, it's only right to be really worried about that and like worry what that's going to do in particular to people like enter the shop market.Alessio: Mm-hmm. I have a solution for that.Which you make them, you create simulative jobs for them.Felix: Okay.Alessio: So this is, this is like half joke, half true. So if you think about software engineering, when you're like a junior engineer, you work like 1, 2, 3 years. And in those three years there's like maybe like a handful of moments where like you really learn something.And then a bunch of other days where like you're not really progressing.Felix: Yeah.Alessio: I think now we can use AI and these models to actually like shortcut these careers and almost like simulate the early years of your work and like just make them like super dense and like these learnings, it's like, hey, we're working on this feature, which is like a distributed system and you need to learn this thing that might take three months at a company.And so you take three months here, it's like we're just simulating the whole thing. It's actually not a real thing. And in one week we kind of speed run through the whole thing and you kind of learn your lesson from there. And we kind of repeat that in like one year. You basically get like three years worth of like projects and experience.Yeah. I think it's harder for like things like sales or for things like, you know, marketing because you don't really have a way to get the feedback loop. But I think a lot of it, it sounds kind of silly, it's like you're making the new effect job, but it's almost like you go to college, right? People pay to learn how to do it, and this might feel similar where it's like, hey, we have the.Jane Street Simulator is like, you wanna come work at Jane Street? We'll just put you in the simulator for like three months.Felix: Wow.Alessio: And you'll come out of it. It's like, you know, I'm ready.Felix: So there, there is an aspect here. I'm not an expert enough to like actually know what, what is going to happen to marketing or legal or finance, right?Like, I don't work in those jobs and I, I don't think I should talk about them, but I am an engineer and I think I have a pretty good idea of what engineering is like. And I think one thing we're sort of seeing is that as a company and also as, as the public, we're like deeply worried about entry level, but we're also seeing more senior engineers accelerate it.If like they're more productive. They, they actually increase the value they provide. And the thing that I'm thinking about a lot is the fact that even before all of this happened, um, I've always had a lot of respect for the University of Waterloo and the, the new grads that have joined my teams as from coming from the University of Waterloo always felt like.More ready than new grads will like literally spend their entire time at the university regardless of how good, but never actually had to work inside an environment where you have to ship things that eventually will be used by users. And I'm, I'm, I'm German. I like initially went to German University and I think the, the, the like information systems programs, there tend to be very theoretical, right?Like I often give people the example of like trying

My first interview with Peter Beck, Founder and CEO of Rocket Lab.

Новинка! Пабл: vk.com/electron_project_offici… ТГ: t.me/muznov

(0:00) Intro(0:02) Waqia-e-Musa AS ka Baqi Hissa(0:30) Firauon par Allah ke Azab(2:42) Aaj ka Insan aur Scientific Theories(3:29) Surah Yaseen ka Saboot(3:47) Pairing System in Creation(4:32) Electron aur Proton Pairing(5:40) Blood Donation – Indus Hospital(6:26) Jism mein Khoon ka Nizam(7:10) Blood Donation ka Masla(8:25) Pairing System in Plants(8:50) Zameen aur Sooraj(9:57) Firauon ki Namuradi(10:47) Musa AS aur Firauon ka Muqabla(12:19) Firauon ki Tension(12:46) Bachpan ka Waqia(16:17) Haqq Parasti vs Munafiqat(17:23) Firauon ka Ta'ana(18:15) Waldain ke Zulm ka Masla(18:35) Maa ki Wajah se Biwi par Zulm(19:00) Firauon ki Tadbeer(20:00) Karachi Roads(20:17) Musa AS ko Neecha Dikhane ki Koshish(20:38) Jadugaron ka Mashwara(23:41) Hukmaran(24:13) Jadugaron ka Ilzam(25:42) Jadugaron ka Pehla Waar(27:38) Asa ke Mojize ki Hikmat(27:47) Musa AS ka Khauf(28:57) Asa Zameen par Dalna(29:34) Daayein Haath ki Fazilat(30:58) Jadugaron ka Mesmerism(31:43) Asa ka Azhdaha Banna(35:26) Jadugaron ka Iman(38:15) Firauon par Itmam-e-Hujjat(39:13) Allah – Hakim-e-Aala(40:48) Firauon aur Hukmaran(41:32) Malika Saba(41:43) Jadugaron ko Saza(42:43) Jadugaron ka Iman(45:13) Sabr ka Nuskha(45:56) Jadugaron ka Aqeedah(47:37) Jannat ki Abadi Zindagi(48:34) Mujrimon ki Saza(49:07) Mominon ka Thikana – Jannat(49:54) Firauon ka Bani Israel par Zulm(50:37) Zameen ka Waris Allah(51:38) Musa AS ko Hijrat ka Hukm(52:09) Tawakkul(52:32) Firauon ka Aelan(53:13) Sahil Adeem ko Jawab(55:35) Sood aur Zina ki Misal(57:38) Islamic Banking(58:25) Sahil Adeem ko Naseehat(58:56) Musa AS ka Rasta Bhoolna(59:58) Bani Israel ki Nalaiqi(1:00:47) Ghaar-e-Hira ka Waqia(1:02:57) Anbiya ka Pak Kalam Hosted on Acast. See acast.com/privacy for more information.

Sponsor LinkThis episode of SpaceTime is brought to you with the support of Squarespace - your one stop when you're ready to build an online presence with ease. To take up our special offer and help support the show, visit www.squarespace.com/spacetimeSpaceTime Series 29 Episode 30 *Solar superstorm hits the red planet Over the past few years planet Earth has been slammed by a series of violent solar storms erupting from the Sun as it transitioned through solar max the climax of its eleven year solar cycle. But what happens when these same storms hit Mars? *Recent tectonic activity discovered on the Moon Scientists have produced the first global map and analysis of small mare ridges seen on the surface of the Moon. *Repair work underway on NASA's Artemis II manned Moon rocket Work is continuing to repair NASA's Artemis II rocket as mission managers prepare to return humans to lunar orbit for the first time in over 50 years. *The Science Report Kids who consume more ultra-processed foods more likely to have issues with behaviour and emotions. New clues about how primates – including humans – evolved. New hope for banana lovers as the threat of Panama disease continues to challenge the Cavendish variety. Alex on Tech new MacBook Neo.

Astronomy Daily — S05E55 | 6 March 2026 Six stories today covering planetary defence, a cosmic laser record, a solar superstorm on Mars, space debris pollution, a mystery satellite launch, and the most charming farming experiment you'll hear about all year.   Stories This Episode 1. Asteroid 2024 YR4 — Moon Impact Officially Ruled Out NASA has confirmed, using the James Webb Space Telescope, that infamous asteroid 2024 YR4 will not hit the Moon in 2032. The space rock — once the most dangerous asteroid identified in two decades — will instead pass the Moon at a distance of around 13,200 miles. It previously held a 4% lunar impact probability, now fully eliminated thanks to Webb's extraordinary sensitivity pushing it to the limits of what the telescope can observe.   2. MeerKAT Detects Cosmic 'Gigalaser' 8 Billion Light-Years Away South Africa's MeerKAT radio telescope has spotted the most distant hydroxyl megamaser ever detected — a natural 'space laser' in a galaxy undergoing a violent collision more than 8 billion light-years away. The signal is so powerful it qualifies as a gigamaser. Adding to the serendipity, the signal was further amplified by a foreground galaxy acting as a gravitational lens on its 8-billion-year journey to Earth. The discovery points toward the future capability of the Square Kilometre Array (SKA).   3. ESA's Mars Orbiters Record Solar Superstorm Hitting Mars A new Nature Communications study reveals what happened when the record-breaking May 2024 solar superstorm hit Mars. ESA's Mars Express and ExoMars Trace Gas Orbiter recorded unprecedented electron density spikes in the Martian upper atmosphere — up to 278% above normal — and both spacecraft experienced computer glitches from the energetic particles. The study uses a novel spacecraft-to-spacecraft radio occultation technique and highlights how Mars's lack of a global magnetic field leaves it vulnerable to solar events in ways that Earth is not.   4. SpaceX Falcon 9 Re-entry Directly Linked to Atmospheric Lithium Plume For the first time, scientists have directly tied a specific rocket re-entry to a measurable atmospheric pollution event. Researchers at the Leibniz Institute for Atmospheric Physics detected a tenfold spike in lithium vapour in the upper atmosphere — from 3 to 31 atoms per cubic centimetre — in the hours following the uncontrolled re-entry of a Falcon 9 upper stage off Ireland in February 2025. Eight thousand backward atmospheric simulations confirmed the connection. Published in Communications Earth & Environment, the paper raises important questions about the growing chemical footprint of the commercial space industry.   5. Rocket Lab Launches Mystery Satellite — 'Insight at Speed is a Friend Indeed' Rocket Lab completed its 83rd Electron launch from New Zealand, deploying a single satellite for a confidential commercial customer to an orbit 470 km above Earth. The company announced the mission just hours before liftoff, offering no further details on the customer or the payload's purpose.   6. Scientists Grow Chickpeas in Simulated Moon Dirt for First Time Researchers at the University of Texas at Austin and Texas A&M University have successfully grown and harvested chickpeas in simulated lunar regolith — the first time this has ever been achieved. Using a combination of vermicompost (worm castings) and arbuscular mycorrhizal fungi to condition the otherwise toxic, sterile moon dirt, the team produced flowering, seed-bearing plants in soil mixtures of up to 75% regolith simulant. The chickpeas have not yet been cleared for eating pending metal accumulation testing — but the team's goal of 'moon hummus' is, apparently, very much alive.   Find Us:  astronomydaily.io  |  @AstroDailyPod on all platforms Subscribe & Review:  Apple Podcasts · Spotify · YouTube · everywhere you listenBecome a supporter of this podcast: https://www.spreaker.com/podcast/astronomy-daily-space-news-updates--5648921/support.Sponsor Details:Ensure your online privacy by using NordVPN. To get our special listener deal and save a lot of money, visit www.bitesz.com/nordvpn. You'll be glad you did!Become a supporter of Astronomy Daily by joining our Supporters Club. Commercial free episodes daily are only a click way... Click HereThis episode includes AI-generated content.

Wes and Scott talk about building v_framer, Scott's custom multi-source video recording app, and why Electron beat Tauri and native APIs for the job. They dig into MKV vs WebM, crash-proof recording, licensing with Stripe and Keygen, auto-updates, and the real challenges of shipping a polished desktop app. Show Notes 00:00 Welcome to Syntax! March MadCSS 02:28 Why screen recording apps are so frustrating 07:14 The requirements behind Scott's app, v_framer 09:47 Tauri, WKWebView, and blurry screen recording headaches 13:00 Why switching to Electron was a game changer 14:02 Electrobun and the hybrid desktop experiment 16:29 Browser-based capture vs native APIs 18:50 Brought to you by Sentry.io 22:32 Notarization, certificates, and shipping a Mac app 24:52 One-time purchases, trials, and selling desktop software 26:37 Self-hosting Keygen for license keys 30:27 A scrappy Google Sheets-powered waitlist 31:56 Keyboard shortcuts, FPS locks, and app customization 34:50 CI/CD and painless auto-updates with Electron 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

Il piano del governo USA anti-censura. Il papa e le omelie con ChatGPT. MS dice che il lavori da ufficio scompariranno. IA per predire il comportamento criminale dei bambini. L'IA che impersona i defunti. Queste e molte altre le notizie tech commentate nella puntata di questa settimana.Dallo studio distribuito di digitalia:Franco Solerio, Francesco Facconi, Massimo De SantoProduttori esecutivi:Edoardo Volpi Kellerman, Vito Astone, Marco Lorusso, Akagrinta@Fountain.Fm, Giorgio Puglisi, Valerio Galano, Umberto Marcello, Gianfranco Di Summa, Giulio Magnifico, Paolo Bernardini, Gabriele Gambini, Fabio Brunelli, Andrea Bottaro, Fabrizio Reina, Cristian Pastori, Manuel Zavatta, Andrea Malesani, Mattia Vailati, Massimo Pollastri, Antonio Manna, Claudio Galante, Nicola Gabriele Del Popolo, Davide Tinti, Jh4Ckal@Fountain.Fm, Roberto Basile, Valentina Gabasio, Marco Romano, Cristian De Solda, Giuliano Arcinotti, Arzigogolo, Fabio Filisetti, Joanpiretz@Fountain.Fm, Enrico De Anna, Giuseppe Brusadelli, Antonio Gargiulo, Fabio Nascimbeni, Christian Schwarz, Beconsulting, Paola Bellini, Simone Magnaschi, Ligea Technology Di D'esposito Antonio, Fabrizio Mele, Alessandro Grossi, Fabio Zappa, Alessandro Lago, Alessandro Blasi, Isacco Tacchella, Filippo Brancaleoni, Fiorenzo Pilla, Valerio Bendotti, Angelo Travaglione, Federico Dainelli, ArmasauroSponsor:Squarespace.com - utilizzate il codice coupon "DIGITALIA" per avere il 10% di sconto sul costo del primo acquisto.Links:AI Agent Operator Came ForwardCome si insegna a un chatbot a essere buono?Freedom.govI preti devono resistere alla tentazione di scrivere omelie con l'AIEuropean Parliament bars lawmakers from using AI toolsGemini lies to user about health info, to make him feel betterAmazon blames human employees for agent's mistakeSecondo Microsoft i lavori d'ufficio scompariranno in 12-18 mesiWhy is Claude an Electron App?AI utilizzata per prevedere il comportamento criminale dei bambiniSam Altman: "Training a human takes 20 years of food."Pinterest Is Drowning in a Sea of AI Slop and Auto-ModerationWhats Happening to Reading?The Washington Post Leaders Missed the PointJudge warns smart glasses wearers of contempt chargesZuckerberg and his Ray-Ban entourage have their day in courtZuckerberg Testifies on Instagram Child Addiction ClaimsTech billionaires are publicly shielding their children from their products$30 billion to ditch textbooks for laptops and tabletsFrance passes bill to ban social media use by under-15sAustralia: il divieto dei social per i minori di 16 anni si rivela inefficaceMixed results one month in Australia's youth social media banMeta Patented AI That Takes Over Your Account When You DieI Verified My LinkedIn Identity. Here's What I Actually Handed Over.OpenAI considered alerting Canadian policeWikipedia blacklists Archive.todayElon Musk's latest scheme is a satellite catapult on the MoonWhy is Bezos trolling Musk on X with turtle pics?Gingilli del giorno:LosslessCut2025 Train delay wrappedTransdimensional Monster HunterSupporta Digitalia, diventa produttore esecutivo.

People often like to talk down Electron, but it is really that bad? There may be better ways to use Web technologies to make desktop apps, but isn’t having Linux versions of apps a good thing no matter how they are made? We mentioned Tauri and Wails. Support us on Patreon and get an ad-free RSS feed with early episodes sometimes See our contact page for ways to get in touch. Subscribe to the RSS feed

People often like to talk down Electron, but it is really that bad? There may be better ways to use Web technologies to make desktop apps, but isn’t having Linux versions of apps a good thing no matter how they are made? We mentioned Tauri and Wails. Support us on Patreon and get an ad-free RSS feed with early episodes sometimes See our contact page for ways to get in touch. Subscribe to the RSS feed

This is a recap of the top 10 posts on Hacker News on February 21, 2026. This podcast was generated by wondercraft.ai (00:30): I verified my LinkedIn identity. Here's what I handed overOriginal post: https://news.ycombinator.com/item?id=47098245&utm_source=wondercraft_ai(01:57): What not to write on your security clearance form (1988)Original post: https://news.ycombinator.com/item?id=47102576&utm_source=wondercraft_ai(03:25): Why is Claude an Electron app?Original post: https://news.ycombinator.com/item?id=47104973&utm_source=wondercraft_ai(04:52): Andrej Karpathy talks about "Claws"Original post: https://news.ycombinator.com/item?id=47099160&utm_source=wondercraft_ai(06:20): How I use Claude Code: Separation of planning and executionOriginal post: https://news.ycombinator.com/item?id=47106686&utm_source=wondercraft_ai(07:48): AI uBlock BlacklistOriginal post: https://news.ycombinator.com/item?id=47098582&utm_source=wondercraft_ai(09:15): Claws are now a new layer on top of LLM agentsOriginal post: https://news.ycombinator.com/item?id=47096253&utm_source=wondercraft_ai(10:43): Acme WeatherOriginal post: https://news.ycombinator.com/item?id=47098296&utm_source=wondercraft_ai(12:10): EU mandates replaceable batteries by 2027 (2023)Original post: https://news.ycombinator.com/item?id=47098687&utm_source=wondercraft_ai(13:38): What Is OAuth?Original post: https://news.ycombinator.com/item?id=47096520&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

En este episodio hablamos de Electrobun, una alternativa moderna para crear aplicaciones de escritorio usando TypeScript con rendimiento casi nativo. Analizamos cómo combina Bun y el WebView del sistema para ofrecer apps más ligeras, rápidas y pequeñas que Electron, y qué significa esto realmente para desarrolladores que buscan velocidad sin sacrificar experiencia de usuario

Новинка! Пабл: vk.com/electron_project_offici… ТГ: t.me/muznov

Jake and Anthony are joined by noted industry watcher Pat O to talk about Rocket Lab's development of Neutron in the Mid-Atlantic.TopicsOff-Nominal - YouTubeEpisode 226 - Missiles are Rockets (with Pat O) - YouTubeRocket Lab's Electron's First Launch from Wallops Island - YouTubepat o.

Rocket Lab is often labeled the “other SpaceX” — but that misses what actually makes the company interesting. In this weekend deep dive, we break down what Rocket Lab really does, from its Electron rocket to its fast-growing satellite manufacturing business. We dig into CEO Peter Beck's origin story, the company's vertically integrated model, and why its upcoming Neutron rocket could be a game-changer. Plus, the bull and bear case on Rocket Lab's stock as space spending, defense contracts, and competition with SpaceX heat up.

In this episode of PodRocket, Daniel Thompson--Yvetot joins us to break down what's new in Tauri 2.0 and how developers are using the Tauri framework to build desktop and mobile apps with Rust and JavaScript. We discuss how Tauri lets developers use frameworks like React, Vue, and Angular for the UI while handling heavy logic in Rust, resulting in smaller app binaries and better performance than Electron alternatives. The conversation covers Create Tauri App for faster onboarding, the new plugin system for controlling file system and OS access, and how Tauri improves app security by reducing attack surfaces. They also dive into mobile app development, differences between system WebViews, experiments with Chromium Embedded Framework, and why cross platform apps still need platform-specific thinking. Daniel also shares what's coming next for Tauri, including flexibility in webviews, accessibility tooling, compliance requirements in Europe, and the roadmap toward Tauri 3.0. Links Tauri: https://v2.tauri.app LinkedIn: https://www.linkedin.com/in/denjell We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Fill out our listener survey (https://t.co/oKVAEXipxu)! https://t.co/oKVAEXipxu Let us know by sending an email to our producer, Elizabeth, at elizabeth.becz@logrocket.com (mailto:elizabeth.becz@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Check out our newsletter (https://blog.logrocket.com/the-replay-newsletter/)! https://blog.logrocket.com/the-replay-newsletter/ Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Chapters Special Guest: Daniel Thompson-Yvetot.

Laurent and Gerard sit down with Jo-Jo Hubbard, CEO of Electron, to explore why the centre of gravity in the energy transition is shifting decisively toward the distribution grid. Jo-Jo explains why the “last mile” is becoming the true engine of system flexibility, how demand at the edge must become a core resource, and why DSOs aren't confused about flexibility at all — they simply respond to the incentives regulators design. Flexibility, she argues, isn't replacing grid reinforcement but making it smarter, helping utilities target and sequence investments far more efficiently at a time when distribution upgrade costs are rising quickly.We discuss how to escape the sector's obsession with endless pilots, and why real scale only arrives when year-round, rules-based products give suppliers and aggregators the confidence to automate and invest. The conversation then turns to the economics of location — from REMA to zonal pricing — and why congestion at the distribution level is where flexibility competes most effectively with copper. Jo-Jo also lays out what it takes to get millions of households engaged without overwhelming them, making the experience effortless, automated and consistent across retailers.She breaks down the hardest parts of the DER orchestration stack, noting that the real challenge isn't cloud infrastructure but standardising how device capabilities and network constraints are described across a patchwork of utilities. Looking ahead to 2030, Jo-Jo argues that no single asset class “wins”: value depends on time, place and service, with EVs likely providing tens of gigawatts of potential flexibility but orchestration remaining the true hero.We cover the future of interoperability and open data — not via global standards, but through adapters and translation layers similar to those that shaped the internet — and examine the cybersecurity demands of cloud-based orchestration as it becomes critical infrastructure. Jo-Jo also gives a global view of progress, from Australia's rapid adoption to the US's accelerating regulatory push and Europe's mix of strong TSO-level progress but uneven local action. She closes with reflections on whether the centralised grid is dying, who should ultimately control DERs, whether blockchain still has a role, and what a nightmare scenario looks like in a DER-dominated world.A fast, clear, and deeply insightful conversation on the rise of flexibility, the reinvention of the distribution grid, and the technologies and rules needed to orchestrate millions of devices.

Bienvenue dans le trois-centième épisode de CacaoCast! Dans cet épisode, Philippe Casgrain et Philippe Guitard discutent des sujets suivants: electricite-quebec.info - La demande provinciale au bout des doigts Electron Liquid Glass - On n'arrête pas le progrès! Swift concurrency - Enfin un guide simplifié Icônes dans les menus de Tahoe - Vous pouvez les enlever dans votre application Subtext - Un éditeur de texte pour iOS simple et gratuit Unixv4.dev - Unix original dans votre navigateur Sloppy - La nouvelle mascotte IA de Microsoft Drone et ski - Un petit film de Philippe Ecoutez cet épisode

Christina and Jeff kick off the new year of Overtired sans Brett. They delve into Christina's impending cervical spine surgery, ICE raids, and neighborhood signal groups. How do you keep mental health in check when Homeland Security is in your alley? Tune in for a wild start to 2026. Sponsor Copilot Money can help you take control of your finances. Get a fresh start with your money for 2026 with 26% off when you visit try.copilot.money/overtired and use code OVERTIRED. Chapters 00:00 New Year Kickoff 00:41 Personal Updates and Health Challenges 01:49 Surgery Details and Insurance Woes 04:45 Exploring Surgery Options and Recovery 12:44 Journaling and Mental Health 15:40 The Artist’s Way and Creative Practices 24:31 Unexpected Alley Incident 38:10 Family Activism and Signal Setup 38:52 Unexpected End of Year Incident 39:35 Speculations and Concerns 40:13 Dealing with Law Enforcement 45:35 Reflections on Responsibility 54:43 Gratitude for Signal 59:31 Tech Talk: Synology and Backup Solutions 01:03:08 Mac Updater Alternatives 01:10:03 Conclusion and Well Wishes Show Links Journaling – The Artist's Way Signal Synology Updatest Join the Conversation Merch Come chat on Discord! Twitter/ovrtrd Instagram/ovrtrd Youtube Get the Newsletter Thanks! You’re downloading today’s show from CacheFly’s network BackBeat Media Podcast Network Check out more episodes at overtiredpod.com and subscribe on Apple Podcasts, Spotify, or your favorite podcast app. Transcript Promise Not to Whine [00:00:00] New Year Kickoff Christina: Well, happy New Year. You are listening to Overtired and I am Christina Warren, and I’m joined as always by Jeff Severance Zel and, uh, Brett Terpstra couldn’t be, uh, here with us in this, uh, happy early 2026 episode, but I’m, I’m super excited to be able to kick off the, uh, the first pot of the year with you, Jeff, how are you? Jeff: I am good. Happy New Year to you. Christina: Likewise, likewise. Um, oh, here, here, here’s to 2026 being significantly better than 20, 25. So Jeff: So far, not so good, but I’m, I’m really, I’m really excited about 2026. I’m Christina: I was gonna say, like, like globally, globally, so far not great, but, but, Jeff: in here. Good in here. Personal Updates and Health Challenges Christina: So, um, so how are, uh, uh, how, how, how is the, I guess a, I guess we can kind of a drill into like a, a brief kind of mental health or, or just personal update thing if we want. Um, how, um. How are things for you so far? Um, I guess the end of the year. How are things with the kids? Um, the [00:01:00] wife, everything. Jeff: the, how the year ended is, and that gets us back to almost a political level. I will save for a topic ’cause boy do I have a story. Um, but, uh, generally speaking, doing really well. Like we traveled, saw my dad and stepmom in Iowa. Saw my in-laws in Indiana, had a really nice, just like generally had a really nice time off. Um, and despite the fact that I’m under a super stressful deadline over the next few days, I feel good. How about you? You got a lot going on. Christina: I, I do, I do. So I guess just kind of a, a, an, an update on, um, the, uh, the Christina, you know, cervical spine, um, saga since we last spoke a couple of weeks ago. Um, I guess maybe two weeks ago now. Um, uh, it was maybe a week ago. Um, uh, it was two weeks ago, I think. Sorry, it was, it was right before Christmas. Surgery Details and Insurance Woes Christina: Um, I was still awaiting, um, hearing back about when I would be scheduled for, uh, surgery and I’m getting, um, uh, artificial disc replacement in, um, I guess [00:02:00] between like C six, C seven of my cervical spine. And I do finally have a surgery date. Yay. Um, the bad, yeah, the bad news is it’s not until February 2nd, so I’ve gotta wait, you know, a month, which sucks. Um, I would have been able to get in, you know, uh, three weeks ago at this point. Um, had I been able to like, I guess like book immediately, but without insurance, like approval, um, I didn’t really want to do that. Um, I think, I think people, uh, can understand why, like, you know, when the doctor’s like, well, we can book you now, but you’ll just need to sign some forms that say you’ll be responsible for the bill if insurance doesn’t pay. Jeff: Oh fine. Get Where’s my pen? Christina: right, right. And I’m like, yeah, this is, you’re gonna keep me overnight just for, you know, observation to make sure like nothing bleeds or, or, or whatever’s a problem. Um, ’cause they’re gonna go through like the, the, the front of my, of my neck to, to be able to reach, you know, um, things that way and, and, and so, [00:03:00] you know, and be under, you know, anesthesia, you know, it’s, it’s, it’s not like a huge critical procedure, but it’s still neurosurgery. Jeff: is through the front of your neck. Christina: and, and, and, and, and, and again, and it’s a neurosurgeon and it’s like, you know, they’re gonna, you know, take some stuff out and try to make sure that like, you know, very, like they’re gonna be, you know, um, screwing up against my trachea and stuff. And like, yeah. I mean, like, you know, it’s, it’s not, it’s not minor. It’s not like I can just go in in an afternoon and be like, oh, I’m, I’m, I can just like walk out. Jeff: Right. Christina: Um, um, although apparently I will feel better, uh, as soon as it happens, but yeah, I mean, this is probably gonna be a six figure, you know, operation, I’m assuming so. No, I, I, I’m sorry. In, in this climate, uh, I don’t feel comfortable. Just, I need my name to be like, oh, yeah, I’ll, I’ll be responsible for that, and then be responsible for trying to track everyone down to, to pay. So that’s the frustrating thing is that, and now of course, you know, you, you get the beginning of the year, a bunch of people have been waiting, you know, to get, you know, things scheduled, I’m sure, and [00:04:00] whatnot. So I’m grateful that I’m scheduled at all. Um, I’m also grateful that right now I’m not insignificant pain, which is a really good thing because if this had been the pain level that I was in for the first few weeks, then like, I wouldn’t, I, you know, I mean, I would wait. I mean, if, if, if you have to wait, you have to wait. But, um, I, I, I might have like pressed upon them like. Is there any way we can move this up? Um, but I’m not in that position, which is good. The only thing is just that the numbness, um, on both arms. But, but, but primarily, yeah. No, I mean, that’s not gone away and, and it’s, and it’s not going to is the thing, right? Like there are a lot of people and like, and I, I’ve started now that I’ve got, got it like actually like done and like scheduled and you know, I’m going through all like the, you know, um, checklist stuff before you, you go in and whatnot. And I have like my, you know, pre-up appointments and all that stuff scheduled. Exploring Surgery Options and Recovery Christina: Um, I am starting to, to look more into, I guess like, you know, I guess recovery videos that people have put up on YouTube and, and reading a few things on Reddit. Although I’m doing my best to, to stay off the internet with [00:05:00] this stuff as much as possible. Um, just because for me it’s, it’s not beneficial, right? Like, it, it’s, it’s one thing if you know, um, you, uh, you don’t like. If, if you can separate and not kind of go down rabbit holes and like freak yourself out or whatever, sure. Maybe it can be good information, but for me, like I, I know my own kind of, you know, limits in terms of, of how much is good for me. And so I’ve, I’ve tried to keep that in moderation, but I have watched a few, you know, videos of people, you know, kind of talking about their experiences. And then of course then that gets used sent with like videos of like doctors who of course, for their own reasons, like are trying to promote like, oh, well you should do the, the, the fusion versus the, the, the disc replacement and, or you should do this versus that. And I’m like, okay. I actually watched one interesting talk that, that some guy gave it a medical conference and neurologist gave it a medical conference and it was a neurosurgeon, I guess is, is the proper term. But that I think kind of really distinctly a, it was very similar to. Exactly what my surgeon said to me, [00:06:00] um, when he was kind of explaining the differences in the procedures. Um, and, and b but kind of went into, I guess like the, the difference in terms of outcomes and, um, and it made me feel better about like that if I’m a good candidate for this procedure, that, that this is, um, the right thing to, to do and probably will be better for me long term. Um, because the, the results are, are better and, but not by a small portion, not like by like a, a gargantuan portion. But they are, they are, there is like a sizable difference between outcomes in terms of whether like the average person who needs a revision, um. For, you know, cervical spine versus getting, you know, disc replacement versus, um, uh, fusion. Fusion has been around a lot longer, and so insurance companies are a lot more likely to approve that. But in Europe, they’ve been doing the, the disc replacement stuff for 25, 30 years. Um, and so there is a lot of data on it, but it’s been a much more recent thing in the United States because insurance companies didn’t really start to do it until about five or 10 years ago. And so, and so, you know, some people will, [00:07:00] like some doctors who very clearly have an agenda on, on YouTube and like, that’s fine, like your practices, your practice and you’re comfortable with what you’re comfortable with. But they’ll be like, oh, we don’t have enough data on, you know, the types of, um, you know, discs that we’re putting in people’s, you know, necks and, and how, how long they, you know, last and, and there might be some differences in terms of if you’re doing like a multi-step, meaning you’re doing like multiple discs at once. Or if, you know, depending on like what, what, what part of the spine you’re in. And like, I, I think at this point for, for artificial disc replacement in the US they’ll do it two steps. So they can do two at once, but they won’t typically do three, although they will do three in Europe. And so there are people who will go to Europe and get the three Jeff: They’re so liberal in Europe. We’ll do three. Christina: Well, I mean, I think it’s a difference in, in that case, just a matter of like, if they’ve been doing the surgeries there longer, you know, then, then they, you know, and, and, and you know, and, and this is not uncommon in, in various forms of, of medicine, you know, where like you have different, you know, procedures and different exploratory things in different fields, in different areas.[00:08:00] So anyway, so then I get kind of trapped into those rabbit holes. But the interesting, the night, the, the, I guess comforting thing is that like, you know, I’ve been reading, you know, around reading, but watching people who were doing vlogs, like after their surgery and like there was this guy who. I was a few years younger than me, but he, you know, posted some updates. I, I guess he got his in July and he kind of did like, you know, updates, you know, kind of like, you know, this was me right after surgery. This was me, you know, three weeks later. This was me however many months later. And that was really great to see. Um, and, and his, his scar actually healed really nicely, which was encouraging. So, um, yeah, I mean, I’m, I’m, I’m, I’m hopeful. I mean, the one thing that’s interesting that, like almost the universal thing that people say, of course you have a few people who say, this didn’t help or, or, you know, this, this was bad or whatever. And, and obviously like that’s always terrible to see that, but you know, you’d have to kind of like go by law of averages. But the, one of the central kind of things is a lot of people being like, I should have done this earlier. And, and so I’m feeling good about that because that is, I, I, I, I don’t know what this says about me, [00:09:00] but like there’s was never a moment in my mind where I’ve been like, oh, I’m not gonna get the surgery as soon as I can get the surgery. That’s never even been part of my like, thought process. And, and, and, and, and it’s funny because I think that like, that is actually odd compared to almost everybody else. Um, the general public, I guess, who goes into these sorts of things. Um, or at least the people who are vocal on the internet, right? So, so maybe like, maybe there are a lot more people like me who just don’t go to forums and comment on stuff and are just like, yeah, I’m gonna get the surgery because that’s what the doctor says. There’s the right thing to do, and that’s what makes sense to me and I wanna, you know, not be in pain and I wanna be able to feel my arm and all that stuff. Um, but there are a lot of people who, I don’t know why, um, I mean, I guess the idea of surgery is, is really scary. And, and like, I can, I can understand that obviously, but to the point where they’re like, okay, well no, I’m gonna try physical therapy and I’m gonna do everything I can to avoid surgical intervention. And I’m, I’m like, no. Like, like [00:10:00] freaking cut me up, doc. Right? Like, like, like, get me in, get me in. Like, let’s get better, right? Like, I, I’m not, I’m not here to like fuck around with like, ’cause right now, because the immediate pain is not there, I could be okay. Right? Like, I Jeff: Sure. Christina: try steroids, I could try pt, I could try to do other types of therapies and be like, well, maybe that will move the nerve around. Or maybe it can get the disc like UN you know, bolt, whatever the case may be. And maybe I won’t need surgery. Um, or I could let this go on longer and continue to be weakness, you know, and, and, and in, you know, it’s not like I’m not in, I’m, I’m not in active pain, but it’s not, not painful at certain times. Not worrying about is this just going to become like a permanent way that I feel, which would be. Awful. Um, and, you know, and, and, and like, it’s not the most debil debilitating thing, like I said. Um, if, if I was in a position where I, I couldn’t get surgery, obviously I could be okay right now, but you never know. Also, like, when is it going to, to swap again? Right? [00:11:00] Like, and, and, and, and for me, I’m also, I’m like, I, I don’t wanna have to like, live in fear of doing something, you know, to my arm or my neck or, or whatever, and, you know, making things worse. So, Jeff: right. Oh, I’m glad you’re doing it. Christina: yeah, me too. So anyway, that was a long-winded update, but Wow. Jeff: Yeah, that’s intense. So I’m really glad the pain is not what it was ’cause Holy shit. Christina: Yeah, the pain was, was really, really bad. And I, like, I look back now and it’s, you know, I, I guess ’cause it’s been a couple of weeks since it’s been really debilitating and it is, and again, I don’t know like that this is me or this is like just somebody else, but I, or this is me or this is the comment with other people. Sorry. Um, is that. Like when I’m not in pain anymore. It is such, so much like, I mean, depression is like this too. It’s so much like a vacuum. It’s like when you’re in it, that’s all you can see. But when you’re out of it, like it’s so easy to forget what it was like Jeff: Yeah, yeah, totally. Completely. Christina: totally completely right. Yeah. Jeff: Yeah. I can even imagine being in the [00:12:00] situation you’re describing, knowing I have a surgery coming up and being like, well, do I want to? Which, like, to your point now, you make that call and you’re worrying forever. Am I gonna wake up? And this thing’s there. Next time it happens, I gotta wait another God knows how long before the surgery, when I’ll know it’s time. Like, you know it’s time now. Get in there. Christina: No, totally, totally. And and that’s the thing. And I think sometimes it can be. Like I said, like when you’re not in the thick of, of it, whether it’s like, you know, feeling depressed or feeling overwhelmed or, or stressed or, or in physical pain or whatever, like it’s easy for to forget like what that can be like. And so I have to just kind of like remind myself like, no, this was really fucking bad. And yeah, you got through it and now you’re on the other side of it. And so you’re like, oh, okay, well, you know, I, I, I could, you know, do whatever, but you’re like, don’t, don’t forget what that was like. Right. Journaling and Mental Health Christina: Um, sometimes I think like, and, and I, and I’m bad at remembering to do this, but new thing for the new year, I guess is why, um, it is important I think to like write things down, right. Like however we’re feeling, whether it’s, you know, good, bad, whatever. [00:13:00] Sometimes, like for me, like it is Jeff: Just like journal you mean, right? Christina: Yeah, exactly. Yeah. Yeah. Be, because it can be useful just to like look back and like, if you’re in a darker spot to remember, hey, there were times when I felt this way. Right. Might not bring, bring me back to that place. But it’s a good reminder. But also I think almost just, it’s importantly, it’s, it’s, it’s the inverse where it’s like you need to remember when you’re in a good place. What it can be like to be in a worse place. Um, because, you know, I think that’s why sometimes people make decisions they make about what medicines they’re going to take or not take or what therapies they’re going to continue or not continue. And, um, and it’s, and it’s really easy to get into that, you know, cycle of, okay, well I’m fine now, um, because you’re removed enough from what it felt like to be bad, you know? And, and then, and, and, and also I think sometimes like, uh, and this is why I wish that I’ve been journaling more over the last few years. You can really get yourself into a deep depression and not realize it. Jeff: Yes, yes. Yeah. And I feel like journaling too, just like helps you internalize some of the flags and [00:14:00] warning signs, even if you’re never looking back, like, ’cause you’re gonna process them a little bit. Christina: yeah, yeah. Jeff: can’t, I, I’ve journaled over the years for stints of time. I can’t go back into them. I almost like, I almost like bounce off the page when I try. Um, but I really have come to believe that just the act of doing it is the thing. Christina: agree. Jeff: Yeah, Christina: Yeah, I agree. Yeah, I, I usually don’t re reread my old stuff either, and I haven’t journaled regularly in a really, really long time, and I actually would like to get back into that again. I think it would be better for my overall health, but similar to you, it’s one of those things I wouldn’t necessarily revisit, Jeff: But now, you know, you have a document, you have a reason to go back into it. Christina: right. Well, but, but also, I mean, I think to your point, just the act of doing it, um, you know, and this is case, we’re both writers. I think this is the, the case for a lot of, of people who, who write like it, it is one of those things that like, that’s what will almost like cement it in my mind. You know what I mean? Like, as, as, as mattering [00:15:00] like, like even if it’s something innocuous, even if I don’t remember the small details of just that, that the fact that like, I’ve done it, like, like to your point, helps you kind of process things and kind of, you know, act more as kind of a therapeutic place. Jeff: Yeah, I don’t, when I’m writing like that, or just in general, I don’t feel like I’m writing from my brain or feel like I’m writing on my brain. Christina: Yeah, yeah. Jeff: It’s like I am actually putting the information in, not drawing it out weirdly. Christina: Yeah. Yeah. No, I, I know, I, I, I, I love that actually, I’ve never thought of it before. Writing on my brain. I love that. That’s really, that, I think that’s really profound. Jeff: Yeah. So there’s, um, there’s a kind of journaling that I wish I, I, well, I don’t beat myself up at all to be clear about this ’cause that I’m too old to do that anymore. The Artist’s Way and Creative Practices Jeff: Um, but there’s this book I read back in. Oh God, 2019 99 called The Artist’s Way by this woman Julie Cameron. And I don’t remember much about this book except for, and I probably have talked about it on this podcast [00:16:00] years ago at this point, but she has this practice, she calls morning Pages. And the idea is you sit down first thing in the morning, you fill three pages, you don’t think about what you’re writing or why you just keep the pen moving. And, and I, what I have found, that’s the only kind of real regular journaling I’ve ever done. It’s a great, great hack for me. ’cause it, it, I can do that. And I fill, I’ll fill a, you know, big notebook and I have a box full of them from over the years. ’cause again, I’m old. Um, but what is, I have never, I don’t think there’s been a single day that I’ve done those morning pages when I haven’t been a little surprised and something hasn’t emerged that. I’m like, I’ll think to myself, well shit, if I hadn’t have done this, where would that have stayed and lived and, and lodged itself. Right. Like, um, so anyway, I I’m glad you are bringing this up ’cause it’s reminding me of that and New Year is a great time to be thinking about that. Christina: Totally, totally. No, I love that. And I, yeah, I, I found the book The Artist’s Way, a Spiritual Path to Higher [00:17:00] Creativity. Jeff: Yes, Christina: and it’s like this yellow gold book, but like, apparently, and then like they, they, they, they, they sell Morning pages Journal, a Jeff: they do, of course. I Christina: Yeah. Yeah, of course. Jeff: it probably took her two decades to realize she should be cashing in on that, but she did. Christina: No, honestly, so the book, it looks like it was published the first one in 92, Jeff: Yeah. Christina: then they were selling the companion volume to the Artist’s Way as December 29th, 1997. Um, so, so like Jeff: that you’re doing this history. This is delightful. Christina: I, well, I just looked at Amazon is just kind of filling this out for me, so I’m, I’m, I’m, I’m, I’m, I’m, so at least it is possible that, that the, the book pages might have been even earlier than that, but like, good for her on like, recognizing there’s also a Artist’s Way workbook, um, now that was like a decade later, like 2006. Jeff: Yeah, that’s what I, maybe that’s what I’m thinking of. That came much later. Christina: Yeah, yeah. But, but it does seem like she got into that, like a David Allen kind of, you know, like, you know, whatever steps of highly, you know what I mean? Like, like all that kind of like stuff, [00:18:00] which Jeff: You’re letting the publisher have those meetings with you. Christina: Which honestly look good for you if you’re selling that many and whatnot. And, and if you come up with this journaling way, yes, sell the freaking paper. You should be selling PDF copies so that people can have it on their iPads now, like, you know, Jeff: Yeah. Christina: or, or, or on the remarkable tablets or whatever. Jeff: she had another thing actually I haven’t thought about in a long time. It wasn’t as useful to me long term. It helped me in the moment I. In the moment I was in, she called ’em artist dates and the idea was like, ’cause as you said in the title, it’s all about creativity. She was like, you, you take yourself out, go to a, whatever it is, a museum, a art supply shop, something like that. But with intention, like, I am going out to do this thing on my own alone because I know that it has some connection to what feels good to me about art and creativity and expression, whatever it was. That seems like a silly thing. Like it’s basically her saying, go to a museum. There was something about calling it an artist date. I think I was in a relationship too at the time where I was like not, it was not easy for me to [00:19:00] just go do something on my own. It was just a weird dynamic a little bit. So anyway, that was another good thing that came out of it. I mean, I, you don’t really have to work hard to tell me to go do something on my own, but at that time in my life you did. Yeah, she was great. That’s awesome. Christina: Yeah. Yeah. Uh, yeah. No, that is funny. Yeah. So yeah, so apparently that book was published in, in 1992 and, um, you know, uh, was immediately like, well, the first printing was about 9,000 copies. In 1992, the book was published by Jeremy Tarcher. Now part of Pink Wing Group revised and millions of copies have since been sold millions. Jeff: it was total like guru status by the Christina: Oh yeah, absolutely. No, absolutely. You know, and, and in a, yeah, she, she was, uh, she’s a, she was born in 1948, and so, uh, she’s still alive. She’s still kicking it. Um, Jeff: yeah. I think she made some new book that was like kind of a take on it, but it was a different, I don’t remember. Anyway. You’re the Christina: Yeah, no, no. Her, her list of like, of like books that she’s published is, she’s the, the most recent one. So she’s still doing the, the, the [00:20:00] writer’s way thing, living the, the artist’s way. An intuitive path to greater creativity. So I guess they did a 2024 version Write for Life, a toolkit for Writers Seeking wisdom, A spiritual Path to Creative Connection. Six week artist program. Jeff: it’s kind of like David Allen, where it’s like, wouldn’t it be nice to have created something when you were, whatever, reasonably younger, like 20, 30 years ago, that not only that you can ride for a long time, but you probably don’t feel bad about riding it for a long time. Right? Like, ’cause you can create things or have a band or something like that, that like your only choice is to ride that thing, but it gets pretty ugly. I see you Vince Neil. Um, but yeah, anyway, must be Christina: No, it ha it has to be nice, right? ’cause it’s like, okay, well no, and, and then it has all these little spinoff things, so it’s not like you have to feel like, I mean, although th this actually, this would, this would be an interesting idea for like a, a, a novel or a screenplay or something, which would be to be like, okay, you know, and people have have done like riffs on these things before on, on, you know, shows or whatever. But, so this would be an interesting story, I think to kind of focus on where it’s like you have somebody who is like, just famous for like, this, this one thing that they did, [00:21:00] and now their whole life has to revolve around it. But what if it was like, something that they didn’t like actually, like, believe in? Jeff: yes, Christina: what if you have the guru? What if you have the guru who’s like, actually is like, actually I don’t really, you know, I’m, I’m, I’m David Allen, but I, but I can’t actually get anything done. I have to have like a whole, you know, cadre of assistance to actually organize my, my, my, my calendar and my life. For me, you know, I don’t Jeff: Carol and Pluribus, I don’t know if you’re watching Pluribus, but that Yes. Her, her whole like book series. Clearly she was at a point where she’s like, yes, I should still ride this, but I cannot. That’s all right. Things changed for her. Um, okay. I have to tell you about something insane that happened to me at the end of 25. Christina: Okay. Alright. Before, before we do that, let me let Ru first, um, let’s, uh, let’s, let’s go ahead and, and get our, our sponsor read Jeff: Oh, way to remember the sponsor. We remember you sponsor. Christina: We, we, we do. So, um, I, I, I, before we hear about what happened to you at the end of 2025, let’s, uh, let’s go ahead and talk, uh, forward a little bit about 2026. So, are you [00:22:00] ready to take control of your finances? Well meet copilot money, the personal finance app that makes your money feel clear and calm with the beautiful design and smart automation. Copilot money brings all your spending, saving and investment accounts into one place available on iOS, Mac, iPad, and now on the web. And so, as we are entering 2026, it is time for a fresh start. And, you know, with Mint, uh, shutting down last year and rising financial uncertainty, consumers are seeking clarity and control. And this is where copilot money comes in. So, copilot money. Basically helps you track your budgets, your savings goals, and your net worth seamlessly. And with a new web launch, you can enjoy a sending experience on any device. And I, I know that, like for me, like this is a big deal because it’s great to like have the native like iOS and MAC OS apps, but I need to be able to access on a, on a, on a web browser. Um, I, I don’t wanna be tied just into an application model for something like, you know, um, tracking my budget. And guess what? For a limited time, you can get [00:23:00] 26% off your first year when you sign up through the web app. New users only don’t miss out on a chance to start the new year with confidence. With features like automatic subscription tracking, you will never miss upcoming charges again. Copilot money’s privacy first approach ensures your data is secure and that their dedicated to helping you stress less about money. So whether you’re a finance pro or just starting out, copilot money is there to help you make better decisions. Visit, try. Do copilot money slash Overtired and use the code Overtired to sign up for your one month free trial and embrace financial clarity today. That’s try dot copilot money slash Overtired and use that coupon Overtired and you will, as I said, save 26% off your first year. So try copilot money slash Overtired. Use the coupon code Overtired. Thank you very much. Copilot money. Jeff: Bam. Can you hear my Synology? Christina: No, Jeff: Oh, that’s funny. ’cause I, I get this. Hum. I recently com I, I’ll visit this in GrAPPtitude. I, [00:24:00] uh, I completely clean, installed my Synology after like six years. ’cause when I did. Build it. Initially, I actually didn’t really understand how to use it, and I, and I made some mistakes that because of all the stuff I put on, it was hard to sort of, I was treating it like it was gonna be an external drive and I could just kind of work with, you know, which was a huge mistake. Um, but anyway, I, it’s working so hard. It’s working so hard and it’s on my desk, which it normally wouldn’t be. So I hear this humming. Didn’t know if you heard it. Christina: I, I did not, I did not, which is a good thing. So, okay, so, all right. Uh, let, let’s, let’s go back. So what, what, yeah, I’m ready. I need to hear what happened to you at the end of 2025. All right. Unexpected Alley Incident Jeff: All right, so, um, my boys are out. They’re almost never out, but they’re both out with friends, different places. My wife and I we’re home and we were eating dinner and I got an alert from my back door ring camera, and. That almost never happens. It’s only exists to, to notify me of like alley shoppers. We’re in, in the city. We have an alley behind us and, and we get a fair amount of pretty [00:25:00] harmless alley shopping. Like it’s, is the car unlocked? If it is, you got some change. If not, I’m moving on. Um, but I like to know when they’re there. Christina: yeah, Jeff: We’ve had some bikes stolen and some people go into our garage and stuff like that. It’s very rare that it goes off less than I actually thought it would. Um, and so it goes off and it goes off at around 7:00 PM very unusual. And, uh, and so I, I, I pull it up and I look and, and I, all I can see is there’s two cars parked in the alley. I have this weird view where, um, it’s kind of a fence and then our garage. So I can see between those two things to the alley basically. So there’s two cars. That’s weird actually. And when I see some of people’s like videos about folks breaking into their cars, there’s often two that come. And so I was like, oh, okay, well it’s, I should just like go out and look. So we go and we kind of look at our, at our back window to see if we can see anything. And we’re just like, yeah, it’s weird. They’re not only parked but the headlights are off. And like, I’m gonna go out and check it out. She’s like, well first, why don’t you look at the video it recorded, which I wasn’t thinking of at all. So I pull up the video, it recorded, and I see these [00:26:00] cars park, but it’s like three or four of them come through the two that I can see park. And all of a sudden there are probably seven or eight figures running down the alley from these cars. Okay? And I’m like, well, that’s crazy. And so I walk out there and I go up to the first car and it’s got Texas plates. And around here where we have a little bit of an ice invasion, Texas plates are reported a lot. I look at the next car and it’s got no plates at all. And I look at the car after that and it’s got vanity plates, specifically chosen one with a Z. Um, and, and I’m like, oh my God. It’s the thing like ice is in my alley. And, uh, and so I come back in, I I’m like, you tell my wife, like, should probably get your coat on. I think it’s the thing is what I said. And, and we go out and sure enough, like at the end of our alley where there is a family and, and they are, um, US citizens, they’re Mexican immigrants, um, that’s where I see all these officers sort of, or these agents sort of coalescing and um, I’m gonna leave some aspects of this out. They were [00:27:00] actually, they were serving, uh, uh, narcotics warrant that ended up being totally misguided. Nothing happened of it. Um, but it was super scary. But I kind of don’t wanna say more than that because I wanna be really clear that as everyone should know about policing, a search warrant is not an indictment. Um, and oftentimes search warrants are so searching and, and, and often come up with. With nothing. Right? And, and maybe even were targeted at the wrong person. And there’s didn’t even have the name of my neighbor on it. It’s this whole thing. But the point is, it was a little different from what we’ve been hearing because there was a different agency there serving a warrant. It was the airport, airport, police department, ’cause of a package. So there was that piece, there was actually a signed warrant. ’cause everyone’s trained to say, show me the warrant. Show me the warrant. So everyone, you know, my wife and I were the first ones there. Um, and then another neighbor rolled up, and then I’ll get to the rest in a second. Um, so it, it’s shocking that it’s happening in our alley. Christina: in our alley, right? Jeff: just like, Christina: you, yeah. Jeff: what? What the Christina: I, I mean, how [00:28:00] I would feel to a certain extent would be like, I’d be like, am I in Amer in an episode of the Americans? Like, like, you know, Jeff: is, did they have to write it this way? Just ’cause how else are you gonna bring it to the people? You know? It’s, you gotta bring it to the characters. Um, so anyway, we go down there and, and there’s one, so all of the, everyone decides the airport PD guy who has no mask and is kind of like presenting like a pretty normal cop basically. And he is got a badge and a name and a number. But walking in and out of the house, all around us are these guys who are in full battle fatigues. They’ve got masks on, they’ve got ars. Um, they are, they are a weird mix of people. There’s a woman in there who’s like looking like, literally like she was cast for a movie to be, uh, an, an ice person. In this case they were Homeland Security Investigations, HSI. But it’s all intertwined at this point. Um, and then there was a guy that must have been like eight feet. That was crazy. There was a single guy that was wearing a, like a straight up like helmet, uh, for, as if he were going into battle. [00:29:00] Nobody else is wearing a helmet. Um. And none of them were talking. They were just passing through. And, um, and so we tried to engage one of them, talked to them for a little bit, do the thing you do. Hey, why don’t you take that mask off? You know, I don’t wanna get docked. I was like, uh, Christina: around. Jeff: it was like, I both understand why you don’t wanna get docked. I also feel like you’ve got the power here, brother. Um, and which was the conversation we had, um, I was like, you have a mask on. You also have your finger on the trigger of a gun. And he’s like, well, that’s not, it’s not on the trigger. This is how we hold guns, dude. I was like, I understand that, but your finger is itching at the trigger of a gun. And so he put his hands on top of the butt of the gun. ’cause it was kind of, you know, mounted the way it is. Is that better? I was like, no, you’ve still got all the power. Take the mask off. Like, at least. Um, and uh, what, what was really interesting, and I I have this sort of like wrap up that occurred to me later that kind of blew my mind is, you know, in our neighborhood, um, because ice activity has been going on all around our neighborhood, like in. Neighborhoods [00:30:00] surrounding our neighborhood or a little further out, but all within a, I could get in the car and rush out there distance. Basically we have these, we have these neighborhood signal groups. The first one that popped up was actually around my son’s school, which is very close to here and has a lot of East African and Hispanic, um, immigrants and, and, um, and so that we knew that was like, you know, people were scared there. Some kids weren’t coming to school. And so, um, some neighbors organized in such a way that they could a, have a signal, uh, communication channel. But also part of that was planning at the beginning of the day and that release time for enough people to sort of be paired up in areas around the school, but not so close that it freaks the kids out. That like if something happened, there could be sort of a rapid response. So we had that signal group. There’s a broader signal group that probably covers like a four block area, and then there’s a wider one that’s our wider neighborhood basically. And that one’s like a rapid response signal group. So these have been going. Pretty, like consistently [00:31:00] ever since it was announced that we were getting ICE and Homeland Security folks here. Um, so the network was all in place. And, and so I’m out there initially and I see all the cars. I’m like, holy shit. Wife and I go to the end of the block. We start talking to first the airport PD guy who’s there, and then the the one HSI guy who comes out. Then another neighbor, another neighbor. I go back to take pictures of the plates because folks around here are keeping a registry that you can get through the signal group of all of the makes and models of cars that we know have been at these, um, kind of ICE activities or homeland security activities, and then their license plates. And so there’s like a running log, which has happened in other cities too. So I was taking pictures of all the cars. Um, but I was pretty like, I mean, I’ve been through some shit and. Having it in your alley is very different from going halfway across the world as like an activist or something. Um, and having it ha neighbors are people we know and care about. And so knowing that, not knowing what’s happening for them, which I don’t mean to bury that lead [00:32:00] ’cause I’m kind of getting to that part, but I also want to just respect their privacy. Um, so like the thing I should have mentioned at the top is like, we know these folks and it was fucking terrifying to be standing there arguing with these HSI guys knowing that at some point, or just assuming at some point these people we know are gonna be dragged outta the house in front of us. And then it was just like this constant question of what the fuck will we do? Then? It did not happen to be really clear, uh, ahead of time. So I’m taking pictures of these cars, I’m like, oh shit. I’m supposed to notify like the signal group, but I’ve got, I’ve got all the presence I need to take pictures of cars. I’ve got the presence I need to engage these guys, which my wife was doing plenty good job of, so I could just like walk away and do the license plate thing. But when I pulled up my phone. To open signal. I opened Slack three times, like I could not, I got an S into my search, my app search, and like kept clicking the wrong thing. I was shaking. It was also freezing out and so like I’m shaking and so [00:33:00] thank God it occurred to me. I have one friend I know on this signal group that I, I know would answer the phone, so I called her. I called her and I was like, I need to be quick. Here are like the fundamental details. Can you please notify? The signal group and the rapid response people. So that was great. She did initially, the first group that showed up, which was just incredible, were like all of our neighbors, we all know this family. Like it’s not, they are just neighbors. It’s not like it’s a special offset group or something. Like they’re neighbors. So all of the neighbors show up. We have a really tight block. Um, that was incredible because it’s not like it’s a neighbor of activists. It’s what’s been incredible about this stuff from the beginning, which is like how easy it seems to be for people to pop outta their house and be like, Uhuh. Like it seems like, it seems like a lot of people are not feeling inhibited about that, which I think is really cool. And I totally respect the people that feel inhibited, right? Like, ’cause it’s just, it’s a whole thing to go out there. So we had this great group of neighbors and they were all, we had a public school teacher who was just killing it with this one HSI guy. It was so, [00:34:00] so good to watch and it felt really powerful and I think she was doing a really good job of trying to sort of like. Knock some things into this guy’s head knowing that like, you know, you’re in a dynamic that kind of you, there’s not a lot of room for things to change. Right. But given that she, it was really just inspiring watching her do her thing and then the like rapid response community showed up, which is like a mix of, you know, folks who are kind of just dedicated neighbors and then people who are sort of what you might call the usual suspects, right? Like the people you would expect, especially in South Minneapolis to show up at a thing like this. And I don’t know if you’ve heard about the thing people do with whistles around these things. Christina: Yeah. Well, I, I, all I’ve heard is that, and I ha, so all I know is I think sometimes people have whistles and kind of like, like, like blow them, almost like to alert people like that, that like, like the, like the, the, the, that like ice is there. Jeff: Yes, exactly. And that yes, that’s exactly it. And that’s been going on here and, [00:35:00] and everybody’s getting whistle. You know, sometimes when you get a good, it’s, I’m not calling it a bit, ’cause I’ll tell you in a minute why it was effective, um, in ways that I hadn’t anticipated. But, uh, you know, it’s like a, it’s, I can do this, I can get a whistle, I’m gonna get a whistle, right? Like, that’s something I can do. Like, it’s something that really caught on and there’s all these whistles being passed around and people on the neighborhood group being like, got a bag of whistles if you wanna come by. So I, ima imagine at this point that when these HSI or ICE people roll up to a thing before they get out, they’re like T minus 15 minutes to whistles, right? Like, this is how long we have before everyone shows up. And, and so pretty soon it’s whistles everywhere. I had a neighbor who kept putting off her, um. Car alarm just to make more crazy noise. We had another neighbor next to this neighbor who is a very conservative like Trump guy who, when he doesn’t like the noise that’s happening in the neighborhood sets off fireworks. And for some reason he was like, I’m gonna do the thing I do, even though there’s all these guys with guns and I’m gonna set off fireworks. But in that case, ’cause he is pissed off at all of us, like it was so [00:36:00] fucking chaotic for a minute. Um, but it was, it was an incredible thing to see how quickly people can deploy basically. Um, ’cause we aren’t like Chicago where like we’ve had a lot of activity here, but it’s been pretty quiet activity. Like, it’s like what happened here? It’s like you and your neighbors know about it and maybe 20 people showed up from your neighborhood rapid response. But like, they’re not the kinds of stories that. They’re not landing on rooftops, they’re not showing up with a hundred cars and calling people away. They’re hauling one person at a time away. And you hear about it here and there, but it’s been very quiet, unlike Chicago. Um, and so to have it given that, especially to have it show up just in your alley was like really, really insane. Um, so anyway, so it all, fortunately the, the police HSI, everybody left with nothing. They did not carry our neighbors away. They did not have any, any result of this warrant that we could tell. But of course, we’re not gonna know. Another [00:37:00] theme of this is how, how hard it is for good information to be resilient in a moment like this, right? That’s a whole other theme. And that, that’s one that gets me kinda riled up when people start after the fact or during the fact really kind of shouting out almost things that are wrong. Like the, the call that went out. For people to come. Said there were six cars in my alley with Texas plates, but I was very clear, there are six cars in my alley. One of them has Texas plates, right? So it’s like, that kind of stuff is a little spooky, but here’s what happened. So at the end it was all over. Our neighbors were able to pop out, wave at everybody, thank everybody. They had been handcuffed this family, um, in their living room while HSI figured out if they were citizens. And, um, what had what the whistles meant in this case was that they knew people were all over around the house. And that was, I’m sure, a level of comfort to know that like something’s happening out there. And then we learned later that there was an immigrant family down the block in the [00:38:00] other direction, across kind of a thoroughfare that we’re on the intersection of who heard the whistles and knew like, let’s stay in the house. There’s a lot going on out there. I dunno what it is, but now I hear whistles. Let’s stay in the house. And, um, and so it was quite a, quite a thing. Family Activism and Signal Setup Jeff: And what I kind of realized afterwards. Was we started this year. My family, my in-laws, my in-laws especially, were very, they’re, they’re, they’re very, um, active. They do kind of activist work, but it’s very like, um, service oriented. But they’ll go to an anti-war protest. They’ll go, you know, they’ll do the thing. They’re, they’re lovely people. And my father-in-law, especially at the beginning of the year, I was like, I don’t know what’s coming. Um, I hear that it’s good for everyone to have signal if we wanna be able to communicate to each other. So I wanna learn how to use signal. And so I helped him, my mother-in-law set it up. I created kind of a family group for Signal and everyone was setting up signal, right? Like at that point, not knowing what was gonna come. It wasn’t even January 20th yet. Unexpected End of Year Incident Jeff: And I wrapped up my year activating a signal network for rapid response because I [00:39:00] had masked people in my alley with guns refusing to identify themselves driving cars from out of state. That is insane. And I was like, that looks pretty tight. Season wrap up. Like, what the fuck? Because I kind of had gotten to the point, I guess prior to when ICE got here in, in the first place, I’d gotten to the point where I’m like, I don’t even really think about Signal anymore. Um, but then they came here and it, and it popped up. So that’s what, that’s what happened in my alley. Um, at the end of the year. Christina: And, and, and, and, and, and I mean, and, and, and you said, you said your neighbors are okay. Speculations and Concerns Christina: I mean, do, do you know anything more about like, like what, what happened or like what the, what the situation was? Jeff: I don’t know anymore. And that’s where I’m like a little cautious because since it was like a warrant for something, it was a narcotics warrant, right? Like, I, I have no idea what happened there. I don’t know. I can, I can only speculate. Um, but I know that the, the [00:40:00] name on that warrant was not someone that lives there. Um, so I can tell you that ’cause I saw the warrant. Um, and, and that’s the most I really feel comfortable saying. Christina: Fair enough. Yeah. I, I, I, I, yeah. I’m not, I’m not trying to like, Jeff: No, I get it. I get it. That’s me actually. Dealing with Law Enforcement Jeff: I’ve been wrestling with like, how much, even on the, I kind of like was asking people to be cautious, even on the signal, because they were sharing details about the warrant. I was like, Hey, details in a warrant. Do not share those, because that sticks to people. And like the details in the warrant were just like, no, we’re not gonna do this. Even when the guy read me the warrant, I was like, are you serious about that? He’s like, oh man, for sure. Okay, sounds good. Let’s, we’ll talk in an hour when you’re all done and you don’t have anything. Like I, I’ve been down this road before. I was a reporter for a long time, like I watched The Wire. Um, Christina: exactly. I was gonna say, yeah, I was gonna say the, the sort of reporting I did, like, yeah, I watched the Wire. Um, so would be Jeff: I said that to the guy. I didn’t say I watched the, yeah, I didn’t say I watched The Wire to the guy, but I was like, he [00:41:00] kept gaslighting us and I was like, come on man. Like you and I we’re smart people, you and I, and that was me being generous. But like, we’re smart people. You and I like, we know this thing you’re saying. It’s like, it’s totally not the case. Like when I asked him. The airport PD guy. What’s up with the cars with Texas plates and no plates and vanity plates? I don’t know, I don’t coordinate with those guys. I was like, okay, that’s weird. ’cause like here you are and they’re walking all around you. Surely you coordinated with them enough to get them here. It was just like, what the fuck? Just so much gaslighting that I won’t even get into, but it was just nonstop. But I was so proud watching my neighbors when the rapid responsible showed up. It was a, there’s always like some people in those situations where I, I, I get pretty activated around lack of discipline and I understand how that happens. But having been in like really super high stakes situations where people could, and who this was one, right? Like I don’t, I don’t react well internally to people who I feel like are working out something that’s theirs. Um, [00:42:00] and at the same time, how do we know how to process this, right? Like, I don’t, we, it was something incredible to watch Mask men and one masked woman walking up and down my alley, bumping past me with guns, with masks, with no idea, with no badges, refusing to pro produce any saying, why does it matter anyhow, saying how much threat they’re under, seeing how they get followed, like just, it was, it was an incredible thing. I had my reaction, but my reaction was based on wiring, based on really intense, unusual experiences. Um, other people, this is new to them. This kind of thing is new to me too, but, so anyway, I, I just like, I saved that. I didn’t even tell you guys when it happened. I’m like, I’ll just tell them on the podcast. ’cause Christina: yeah, no, I mean, that’s, that’s wild. I mean, like, and it’s just, it’s just, well, and, and it’s, I don’t know, it’s so dystopic, right? Like, it’s such a, like a, a terrible like thing to like have to like witness part of, right? Because like, look, yeah, there are going to be circumstances when maybe like, you know, Homeland Security or somebody else, like really actually does need to be involved and, you know, [00:43:00] um, you know, at your neighbor’s house. And like, that’s unfortunate, right? But like, there, there are real circumstances where that could be a case. Like I, I, I, I, I mentioned the, the Americans earlier, that was like, based Jeff: I need to watch that. Christina: It’s a great show. But, but the, the, the, uh, a former CIA agent was one of the, the, the, the creators. But the, um, the idea came to like, uh, one of the showrunners basically, he read an article, I think in the New Yorker or something about a, a family that like seemed like, just like the perfect, like normal family next door. And like the kids came home from school one day and the parents had been picked up because it turns out that they had been Russian spies living in the United States for like 20 years. And like, they were like actual Russian spies. And, and then that kind of like went into, okay, well, well, well, what happens then? Like, what happens to that family and, and what happens to get to that point? Like, what happens? Like if your neighbors are those things, right? And so there are those like very much like stranger than fiction. Like, like things, right? But in most cases, that’s not the circumstance. And, and certainly the way that like all this has been handled and the way that they’re doing all of this treat things for, [00:44:00] you know, like whatever the warrants were for whatever the situations are where they’re like, okay, now we’re gonna bring all these other groups in. We’re not going to have any due process at all, and we’re not going to, to bother with any sort of thing of humanity at all and then freak everybody else out, like is just, you know, then, and then it puts you like, as, as the neighbor, like in this position where you’re like, okay, well how do we get the word out? How do we help, how do we, you know, make sure that if’s something, is that if this is something that you know, isn’t what we, what we think that it is or whatever, that we can make sure that they’re not going to be. ’cause we see all the reports all the time. I mean, US citizens are getting arrested for, Jeff: Yeah, totally. Christina: the wrong way, Jeff: Oh yeah, we had a, we had a woman here probably, I think she was like in her sixties, and she walked out of her house ’cause there was something happening across the street. And in moments she was in the car, she was gone. Her husband didn’t know where she was. She was released later that day. Like we’ve had a lot of stories like that. And so that was stressful too, going in, right? Like when my partner and I went, went up to talk to this guy, I, I left down the alley to take pictures, but I [00:45:00] was like looking over my shoulder constantly. ’cause she and I have talked about how, like, can you imagine if one of us was taken and we didn’t know? And I was like, oh, we are in a situation right now where no way can I say, there’s no chance one of us will be taken. Like, no way. And you know, the longer you’re there, the more you push it a little bit, you know, not push it like physically or something, but just like push it a little more people out front. Someone kicked an ice car in, in an HSI car and got like pepper sprayed or whatever. Um, Christina: and it’s, and it’s like, don’t do that. Like, don’t like, Jeff: Well, it’s funny because, it’s funny because that per I, this is, I, I know there are people listening who will think I’m such an asshole for this, but I, to I, I feel zero apologetic for it. Reflections on Responsibility Jeff: So I am, I’m not like a huge fan, like kick the car when there’s a family that we don’t know how they’re doing and these people are around, like, don’t escalate in that way with these people. Don’t set off fireworks behind the guys that have their fingers resting near triggers. Like you Christina: That’s what I’m saying. That, that, yeah. Jeff: yeah, you just don’t do that. Uh, but here’s the part that makes me sound like an asshole and, and I don’t mind at all. [00:46:00] Um, they were, they were the only person that was pepper sprayed. And, and it was this, you know, certain people that come from outside the neighborhood. It was this very dramatic thing, whatever they pepper spray, you know, whatever. And I was like, what, what happened? They kicked the car. I was like, eh, I’m going in like, I mean like, yeah, you got pepper spray because you kicked the car. I assume you were in for that. Like you signed just like the guy with the mask who’s worried about being docked. He signed up for this dude. Christina: I was gonna say, you, you, you, you signed up for this, you, you, you, you’ve signed up because you saw Christina O’s you know, like ridiculous, like, you know, like, come, come join Ice, you know, like, like, you know, freaking social media, you know, posts or whatever, like there ads you’re doing like, yeah. Like you, you know exactly what you’re doing, so fuck off. I don’t, yeah, I have zero. Jeff: I I said you signed up for this. I did not sign up for this. I said you signed up for all of it, dude. Like you Christina: Yeah, absolutely. No, I mean, honestly, well, well look, you know, it’s the same thing like the military, frankly, like, you know, like in the, in, in the seventies and stuff, and we saw, you know, more of it then, like, I’m not saying that it was like the, the right or like nice or like humane thing to spit in the, in their faces. [00:47:00] Right. But like. Especially after the draft was gone. Like, you sign up for that shit, Jeff: It’s a tough man. I, I had that, I, that experience throughout the Iraq war where. I knew. I mean, there’s the economic draft. There’s all right, there’s all these reasons people end up in war. But at the end of the day, when I am walking around a city I love, and other Americans are there in armor and Humvees and they have destroyed a city, I feel like this is what you signed up for. It’s not what you signed up for, but it is literally what you signed. Same with police. It’s a little bit Christina: that’s Jeff: I totally respect the trauma. I respect that you’re in situations where Christina: that’s real. No. Jeff: your values. Like I Christina: Absolutely. Absolutely. And, and, and that, that is real. And, and to your point, there might be like, like economic scenarios, drafts and other scenarios where like you’re like, well, I had a choice, but I didn’t have a choice. Okay, but you knew that this was a trade off. Like you knew that this was a thing that comes with, with, with the territory. If it comes with adulation, but it comes with the bad stuff too. Right. Jeff: And if you’re killing people, I don’t feel super bad about saying that. I feel super bad for you for having to live with that [00:48:00] fact. But like I don’t feel bad for saying, Hey man, Christina: well, I mean, like, and, and it’s a Jeff: have said no. Christina: and it’s a completely different like thing. I’m not even trying to categorize it the same way. ’cause it’s, it’s not. But like, just, just like in, in my life, you know, people oftentimes will like, yell at me about stuff that they don’t like, about, like the companies like that I work for. And you know, what I, I’m, I’m part of my job is to kind of be a public face for, for those things. And that means that I get yelled at and that’s okay. And like that, that I, I quite literally knew that I signed up for that. Does that mean that I always appreciate it? That is, does that mean that I don’t get annoyed sometimes? Does that mean that I like being like tarred and feathered with like mistakes or decisions that like, I had nothing to do with Absolutely not right. But like, that’s quite literally part of my job. So, you know, it, it, it is. So I can’t like turn around and be like, oh, well, you know, you can’t, you know, like. You know, say, say this to me, or whatever. Right. Um, but, and, and again, I realize it’s a completely different scale of things. I’m not in any way trying to equate the, the, the, the two [00:49:00] scenarios, Jeff: No, but it’s, I mean, it is, yeah, Christina: but all of us, but all of us, we have jobs and we do things and like in a case like this, like if you work for those agencies, right. Especially right now, and like I recognize and I can be sympathetic that you may not have signed up. Under these circumstances. Having said that, I will say that if you signed up in the last eight years, you knew that these were things that were going in a certain direction, right? Um, I, I, I, I, I will, I will further say that like I, I’m not gonna say that like every single person is involved, but I will say like in the last eight years, you’ve, you’ve seen which way the wind was going and, and, and, and, and that’s okay. You can make that decision and, and like, I’m not gonna judge you or your character as a person for that decision. I’m, I’m, I’m, I’m not. ’cause we all have to make decisions about where we work. Having said that, that just also means like what we’ve been saying, you’re gonna have to deal with some shit. You’re gonna deal with people recording your face. You’re gonna have to deal with people being angry with you. You’re gonna have to deal with, to your point, people kicking the cop car. And if that’s all that happens and like, and, and, and, and it’s not gonna lead to another escalation point, that’s fine. I, I’m with you. I

In this episode, we explore a diverse array of captivating stories from the far reaches of our solar system to pressing challenges in Earth's orbit. We kick off with a critical discussion on satellite disposal, weighing the merits of designing for demise versus non-demise as mega constellations like Starlink proliferate. The environmental implications of each approach are examined, highlighting the need for a sustainable solution.Next, we journey to the Kuiper Belt, where astronomers from Princeton University have uncovered a new structure known as the "inner kernel" of objects. This discovery challenges our understanding of the solar system's formation and reignites the search for the elusive Planet Nine.We then celebrate Rocket Lab's remarkable achievements over the past year, including 21 successful launches of their Electron rocket and the introduction of their innovative Neutron rocket, designed to compete with industry giants.As we mark the end of an era, we pay tribute to NASA's Terra satellite, which has provided invaluable data on Earth's climate and environment for 26 years.The James Webb Space Telescope surprises us with findings on the super Earth TOI561b, revealing it to be a dynamic volcanic world with a rich atmosphere, defying previous assumptions about such close proximity to its star.Finally, we delve into the unique business of space memorials with Celestis, which is set to launch its most ambitious mission yet—a permanent orbit around the sun for cremated remains and DNA, creating a man-made comet that will journey through the cosmos indefinitely.Join us as we unravel these intriguing stories and more in this episode of Astronomy Daily!00:00 – **Give us 10 minutes to give you the universe00:37 – **With mega constellations launching thousands of satellites, disposal of satellites is critical02:24 – **Scientists at Princeton University have found something new in the Kuiper Belt05:18 – **NASA's Terra satellite has been retired after 26 years of service06:12 – **The James Webb Telescope has turned its gaze to an exoplanet08:19 – **This week's Astronomy Daily features a variety of topics### Sources & Further Reading1. NASA2. Princeton University3. Rocket Lab4. Celestis5. Space.com### Follow & ContactX/Twitter: @AstroDailyPodInstagram: @astrodailypodEmail: hello@astronomydaily.ioWebsite: astronomydaily.ioClear skies and see you next time!

A holiday special! Enjoy this week's episode of Headlines free. It's an absolute monster episode—way longer than usual Headlines episodes, I promise—but it's a great example of what you get when you support the show over at mainenginecutoff.com/support.NASA finally—and we really do mean it this time—has a full-time leader - Ars TechnicaAgencywide Town Hall with NASA Administrator Jared Isaacman, Friday, Dec. 19, 2025 - YouTubeTrump commits to Moon landing by 2028, followed by a lunar outpost two years later - Ars TechnicaNASA Teams Work MAVEN Spacecraft Signal Loss - NASA ScienceNASA Continues MAVEN Spacecraft Recontact Efforts - NASA ScienceSpaceX Sets $800 Billion Valuation, Confirms 2026 IPO Plans - BloombergSpaceX $1.5 Trillion Value Target Hinges on Starlink — And Elon - BloombergSpaceX Said to Notify Employees of Quiet Period Ahead of IPO - BloombergIn a surprise announcement, Tory Bruno is out as CEO of United Launch Alliance - Ars TechnicaSpace Development Agency awards $3.5 billion in contracts for missile-tracking satellites - SpaceNewsChinese astronauts inspect debris-damaged Shenzhou-20 spacecraft during spacewalk - SpaceNewsSpace Station – Off The Earth, For The EarthNASA Astronaut Jonny Kim, Crewmates Return from Space Station - NASAAfter key Russian launch site is damaged, NASA accelerates Dragon supply missions - Ars TechnicaR-7 ICBM/Soyuz rocket launch facilities in BaikonurLaunch Roundup: China, Russia, Rocket Lab, ULA join SpaceX in flying this week - NASASpaceFlight.comLaunch Previews: Ariane 6, Falcon 9, Atlas V, and Electron launches highlight busy week - NASASpaceFlight.comLaunch Roundup: International launches fill manifest during last full week of 2025 - NASASpaceFlight.comChina launches 4 times in 4 days, boosting megaconstellation and surveillance assets - SpaceNewsChina launches new TJS satellite, commercial Kinetica-1 lofts 9 spacecraft - SpaceNewsMichael Nicolls on X: “When satellite operators do not share ephemeris for their satellites, dangerously close approaches can occur in space.   A few days ago, 9 satellites were deployed from a launch from the Jiuquan Satellite Launch Center in Northwestern China. As far as we know, no coordination or…”China launches experimental cargo spacecraft, opaque tech demo mission and remote sensing satellite - SpaceNewsAndrew Jones on X: “Turns out there were two male mice launched on the DEAR-5 cargo spacecraft for neuroscience research. Spacecraft is planned to operate in orbit for one year and is not rated for reentry, so it's game over at some point for the rodents. Video is prelaunch.”Rocket Lab launches JAXA tech demo satellite - SpaceNewsAriane 6 launches Galileo navigation satellites - SpaceNewsThese are the flying discs the government wants you to know about - Ars TechnicaBlue Origin flies first wheelchair user to space - SpaceNewsRocket Lab wraps up record launch year - SpaceNewsJapan's H3 suffers second-stage anomaly, QZS-5 satellite lost - SpaceNewsAndrew Jones on XChina launches new Guowang satellites, Long March 12A launch and landing attempt date set - SpaceNewsKeep an eye on upcoming launches with rocketlaunch.live.

Tell us what you think of the show! Transforming the grid to meet skyrocketing energy demand isn't just about switching generation sources but is instead about fundamentally redesigning the entire energy market. It's going to require unlocking the true potential of every Distributed Energy Resources (DER) that we have, and integrating them seamlessly into a complex, resilient system. That's easy to say but exceptionally complicated to do logistically and in a way that makes sense for a given market, which is why we wanted to talk with someone who isn't just supporting this transformation, but is also actively working with utilities to better understand what's happening at the grid edge to make informed decisions. Jo-Jo Hubbard is the Co-founder and CEO of Electron, which helps network utilities and grid operators adopt and scale flexibility markets to manage grid congestion, improve connection rates, and lower bills. Among other things, we discuss:Why utilities need to shift from a static view of the distribution grid to a real-time, dynamic modelHow smart coordination of DERs creates a resilient and efficient gridWhat it means to make DER orchestration simpler and more compelling to utilitiesHow tiny efficiencies can lead to billions in savings at scale.The single biggest lesson learned that utilities need to have top of mind when designing their own DER aggregation and dispatch programsWant to make a suggestion for an upcoming episode? Get in touch to let us know what people, projects and technology you'd like to see us to further explore. Want to make a suggestion for This Week in Cleantech? Nominate the stories that caught your eye each week by emailing Paul.Gerke@clarionevents.com

Podcast Description: The Missing Piece in Chronic Illness (Electrons + Blood Flow)Schedule a Discovery Zoom Call https://drhughwegwerth.com/discovery-call/If you feel sick all the time and nothing seems to “stick,” this episode is for you. In this talk, Dr. Hugh shares a simple idea: many chronic illness cases are linked to being “electron deficient.” That means your body may not have enough negative charge to run well.In This Episode, You'll LearnWhat “electron deficient” means and why it matters for healingWhy short-term fixes may help for a bit, then stop workingHow the body depends on electrons to support energy and healthWhy tiny blood vessels (capillaries) matter most for real healingWhy blood cells can clump together when charge is lowWhat “zeta potential” means (simple version: the charge around red blood cells)Why smooth blood flow helps deliver oxygen and nutrientsA Simple Picture Dr. Hugh UsesBig blood vessels = about 1% of your systemTiny capillaries = about 99% of your systemThe point: real healing depends on the “small stuff” working wellKey Idea About Blood FlowRed blood cells need the right charge so they don't stick togetherWhen they stay separated, blood can flow better through tiny capillariesWhen they clump, it can slow delivery to tissuesTests and Clues MentionedBlood pH (needs to stay in a tight, healthy range)Sedimentation rate (sed rate/ESR) as a possible sign of clumping and inflammationSolutions Covered in the EpisodeGrounding (“Vitamin G”) to support electron flowPhosphatidylcholine (PC) to support cell membranes and healthy blood cell movementSupport the glycocalyx (a protective lining in blood vessels that has a negative charge)Stabilize blood sugarSupport minerals + hydrationFix the gut (because healing is harder when the gut is unhealthy)Address toxins like mold and heavy metals that may drain the systemWho This Episode Is ForPeople with chronic illness that won't improvePeople with fatigue, inflammation, brain fog, or poor circulationAnyone who feels like they have tried everything and still feels stuckMain TakeawayHealing works better when your body has the charge and support it needs.You don't need to suffer forever. You may just need a guided plan.

Zack Reneau-Wedeen is the Head of Product at Sierra, leading the development of enterprise-ready AI agents — from Agent Studio 2.0 to the Agent Data Platform — with a focus on richer workflows, persistent memory, and high-quality voice interactions.How Sierra Does Context Engineering, Zack Reneau-Wedeen // MLOps Podcast #350Join the Community: https://go.mlops.community/YTJoinInGet the newsletter: https://go.mlops.community/YTNewsletter// AbstractSierra's Zack Reneau-Wedeen claims we're building AI all wrong and that “context engineering,” not bigger models, is where the real breakthroughs will come from. In this episode, he and Demetrios Brinkmann unpack why AI behaves more like a moody coworker than traditional software, why testing it with real-world chaos (noise, accents, abuse, even bad mics) matters, and how Sierra's simulations and model “constellations” aim to fix the industry's reliability problems. They even argue that decision trees are dead, replaced by goals, guardrails, and speculative execution tricks that make voice AI actually usable. Plus: how Sierra trains grads to become product-engineering hybrids, and why obsessing over customers might be the only way AI agents stop disappointing everyone.// Related LinksWebsite: https://www.zackrw.com/~~~~~~~~ ✌️Connect With Us ✌️ ~~~~~~~Catch all episodes, blogs, newsletters, and more: https://go.mlops.community/TYExploreJoin our Slack community [https://go.mlops.community/slack]Follow us on X/Twitter [@mlopscommunity](https://x.com/mlopscommunity) or [LinkedIn](https://go.mlops.community/linkedin)] Sign up for the next meetup: [https://go.mlops.community/register]MLOps Swag/Merch: [https://shop.mlops.community/]Connect with Demetrios on LinkedIn: /dpbrinkmConnect with Zack on LinkedIn: /zackrw/Timestamps:[00:00] Electron cloud vs energy levels[03:47] Simulation vs red teaming[06:51] Access control in models[10:12] Voice vs text simulations[13:12] Speaker-adaptive turn-taking[18:26] Accents and model behavior[23:52] Outcome-based pricing risks[31:40] AI cross-pollination strategies[41:26] Ensemble of models explanation[46:47] Real-time agents vs decision trees[50:15] Code and no-code mix[54:04] Goals and guardrails explained[56:23] Wrap up[57:31] APX program!

Welcome back to Beautifully Broken, where healing meets high performance. Today I'm joined by my friend and returning guest George Wiseman, who last appeared in Episode 141 sharing his extraordinary origin story. This time, we take a more advanced dive into hydrogen medicine—specifically the differences between molecular hydrogen (H₂) and Brown's Gas, a unique blend containing hydrogen, oxygen, water vapor, and an electron-rich plasma known as EEW (electronically expanded water).George breaks down how Brown's Gas delivers not only molecular hydrogen but also bioavailable electrons—fuel your body uses to stop oxidative cascades, rebuild tissue, and restore cellular communication. We talk about why H₂ alone doesn't always create a perceptible effect, why Brown's Gas often does, and how these modalities play distinct roles in the ecosystem of healing tools. He shares incredible user stories—from carpal tunnel relief in minutes to a young woman who beat metastasized cancer using Brown's Gas as part of an integrative healing plan.We also explore the new micro-bubbler attachment that infuses bathwater with micro- and nano-bubbles, dramatically increasing gas absorption and accelerating skin repair. Then George reveals the next frontier: a forthcoming AquaCure add-on that allows users to make their own deuterium-depleted water, a therapy shown to support mitochondrial function and metabolic repair.This conversation is equal parts science, innovation, and lived experience—another perspective-shifting journey with one of the most generous inventors in wellness tech. Episode Highlights [00:00] – Hydrogen research overview: inflammation, oxidative stress, and why H₂ is having a moment[02:22] – The AquaCure's unheard-of one-year money-back guarantee[03:38] – Welcoming George back + reflections on the “Beautifully Broken” ethos[05:26] – No device is a panacea: hydrogen as one tool in a larger healing ecosystem[07:53] – A remarkable cancer remission case and how Brown's Gas supported the process[09:16] – Why hydrogen helps nearly every condition studied (and why side effects are positive)[10:27] – What is Brown's Gas? The six constituent gases and how they're formed[11:56] – Discovery of electrically expanded water (EEW): a third gas with unique properties[14:22] – The role of electrons: inflammation reduction, oxidative damage repair, and immune support[16:47] – Brown's Gas during the pandemic: oxygenation, cytokine storms & rapid recovery[19:14] – Why you must stay below a 2% inhalation threshold for safety[21:40] – Hydrogen's role in regeneration: scars, immune restoration, and organ repair[24:08] – External applications: bags, gloves, spot treatments, and rapid nerve relief[26:10] – Hydrogen vs. methane: how microbiome differences shape individual outcomes[28:27] – Why Brown's Gas feels different than H₂—tingles, energy, and nerve activation[30:32] – EZ water (Pollack): how Brown's Gas increases structured water up to 300%[34:42] – Solving medical mysteries: capillary flow, blood pressure, and nutrient transport[39:12] – The problem with “flagged words” in health conversations (structured water, silver, etc.)[45:17] – Dreaming of an NFL-wide recovery experiment (Buffalo Bills, call us!)[47:13] – The new micro-bubbler: micro/nano bubbles, skin repair, and whole-body absorption[52:24] – Scar regeneration, tingling, and my own early bathtub experiment[53:18] – Comparing Brown's Gas to oxygen, CO₂, and other recovery tools[55:44] – Why hydrogen research has shifted to PEM systems—and their limitations[59:42] – Worldwide accessibility: yes, AquaCure ships to New Zealand (and everywhere else)[01:01:47] – Upcoming release: AquaCure's deuterium-depleted water system[01:04:08] – Why DDW matters for metabolism and mitochondrial repair[01:05:28] – Holiday discount: 25% off until December 15, 2025 + upcoming price increase[01:06:51] – Closing gratitude and reminder to support the showGet the AquaCureGeorge Wiseman's AquaCure: https://eagle-research.com/product/ac50-v2/— Code: BEAUTIFULLYBROKENLinks & ResourcesThe Biological Blueprint Program: https://www.beautifullybroken.world/Beam Minerals: http://beamminerals.com/beautifullybroken— Code: BEAUTIFULLYBROKENSilver Biotics: bit.ly/3JnxyDD— 30% off with Code: BEAUTIFULLYBROKENLightPathLED: https://lightpathled.pxf.io/c/3438432/2059835/25794— Code: beautifullybrokenCathcBio https://www.catchbio.com/beautifullybroken— Code: beautifullybrokenStemRegn: https://www.stemregen.co/products/release?_ef_transaction_id=&affid=52&oid=1— Code: beautifullybroken     CONNECT WITH FREDDIEWork with Me: https://www.beautifullybroken.world/biological-blueprintWebsite and Store: (http://www.beautifullybroken.world) Instagram: (https://www.instagram.com/beautifullybroken.world/) YouTube: https://www.youtube.com/@freddiekimmel Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Hoy hablaremos sobre una de las fuerzas más fascinantes y menos intuitivas de toda la física: la fuerza de degeneración, o como la llaman los físicos, la presión de degeneración de electrones. Esta fuerza no solo mantiene estrellas enteras en equilibrio… también es una consecuencia directa de la mecánica cuántica, de algo tan fundamental como que dos electrones no pueden ocupar el mismo estado cuántico.Curiosidad Científica Podcast (@curiosidacientificapodcast) • Instagram photos and videosHandmade Soap Bars - Natural & Artisan Crafted | Jabonera Don GatoCodigo de descuento: CuriosidadPatreon.com/agustinvalenzuela

Listen to a recap of the top stories of the day from 9to5Mac. 9to5Mac Daily is available on iTunes and Apple's Podcasts app, Stitcher, TuneIn, Google Play, or through our dedicated RSS feed for Overcast and other podcast players. Sponsored by Roborock: Save up to 50% on Roborock's flagship vacuums during their Black Friday event — but hurry, these deals won't last long!  New episodes of 9to5Mac Daily are recorded every weekday. Subscribe to our podcast in Apple Podcast or your favorite podcast player to guarantee new episodes are delivered as soon as they're available. Stories discussed in this episode: Latest macOS Tahoe beta fixes bug with Electron apps that caused widespread performance issues Apple News just lost a major media partner after a decade Apple set to become world's top phone maker once again Listen & Subscribe: Apple Podcasts Overcast RSS Spotify TuneIn Google Podcasts Subscribe to support Chance directly with 9to5Mac Daily Plus and unlock: Ad-free versions of every episode Bonus content Catch up on 9to5Mac Daily episodes! Don't miss out on our other daily podcasts: Quick Charge 9to5Toys Daily Share your thoughts! Drop us a line at happyhour@9to5mac.com. You can also rate us in Apple Podcasts or recommend us in Overcast to help more people discover the show.

Bio: Philip Krim is the Co-Founder and CEO of Montauk Climate. Previously he founded early-stage investment firm Montauk Ventures. He also co-founded, led, and served as Chairman of Casper Sleep, scaling it to over $500M in revenue, taking it public on the NYSE, and overseeing its eventual sale. Mr. Krim is a Director of the Travis Manion Foundation and on the Leadership Council of the Robin Hood Foundation. He holds a B.B.A. in Marketing from the Red McCombs School of Business at the University of Texas at Austin Bio: Evan Caron is Co-Founder and CIO of Montauk Climate with over 20 years of experience in energy, electricity risk, and commodity management. He previously led Venture at Riverstone Holdings, a $40B energy investment firm, and co-founded ClearTrace, an ESG data platform for emissions tracking. Evan is also Co-Founder of Daylight Energy, a community energy software network. He serves on the Board of RPower, a distributed energy platform backed by Isquared, and previously served on MP2 Energy's Board before its acquisition by Shell. Earlier in his career, Evan held senior roles at Deutsche Bank, Mercuria, and Trailstone. Links: Montauk Capital site Clear Current site Haven Energy site Electron X site Phillip's email Phillip LinkedIn Evan LinkedIn

Follow-up: John has some new Vision Pro treats Flight Ready In the defense of the CD-R (via Jonathan Goforth) ATP Tier List: Storage Media Auto-generated chapters in Apple podcasts We’re dummies: ATP has a [chapter-free] bootleg Some more technical details (via Stephen Robles) Subscriber audio chapters are a mess New MacBook Pro design is for M6 Pro & Max only? Mark Gurman’s coverage MD101 Tahoe & Electron app fixes Discord is fixed (via Dayton Lowell) Microsoft Teams Classic is likely to never get fixed (via Adam Wunn) macOS Emoji Picker ⌃ ⌘ Space Rocket Pogo-stick robot Boston Dynamics A butt-dialing theory from Trey Carpenter iPhone Pocket Paul’s analogy Gruber’s post iPod Socks On eBay New Steam Hardware Initial coverage Image of the new devices Announcement video Digital Foundry’s coverage Dave2D’s coverage Steam Controller TMR not Hall Effect Understanding the difference Steam Machine Images on The Verge Steam Frame More photos Post-show: Marco goes to Home Depot Members-only ATP Overtime: Affinity graphics apps go free, and some people are upset Press release Sponsored by: Factor: Healthy Eating, Made Easy. Get 50% off your first box, plus free breakfast for 1 year. Grammarly: A digital writing assistant that ensures your writing and reputation shine. NordLayer: Get 28% off on yearly seats through December 10th with the code ACCIDENTALTECH-28. Become a member for ATP Overtime, ad-free episodes, member specials, and our early-release, unedited “bootleg” feed!

We talk about Electron apps and last week's announcements before getting to the meat of the episode which is, oddly, bagels.Electron apps seem to causing Tahoe to slow down.Amazon is laying off everyone.Jason takes a look at the M5-based iPad Pro and MacBook Pro.The fine Six Colors staff reviewed the new features for the Vision Pro.Apple is adding a toggle to turn Liquid Glass almost off.Lex suggests trying Too Good To Go.If you want to help out the show and get some great bonus content, consider becoming a Rebound Prime member! Just go to prime.reboundcast.com to check it out!Were you aware that you could buy things from us?! That's right! Shirts, iPhone cases, mugs, hats and one other type of thing are all available from our Rebound Store!

Surgical removal has long been the standard for dealing with pre-cancerous skin lesions—but what if there were a less invasive alternative?     On today's show, I'm introducing a little-known option called Electron Beam Therapy (EBT) that's gaining traction for treating early-stage skin cancers like basal cell and squamous cell carcinoma.     We'll cover how EBT works, what types of skin lesions it targets, and who it may be best suited for.     So join me on today's Cabral Concept 3478 to find out if Electron Beam Therapy (EBT) is right for you.     Enjoy the show, and let me know your thoughts!   - - - For Everything Mentioned In Today's Show: StephenCabral.com/3478 - - - Get a FREE Copy of Dr. Cabral's Book: The Rain Barrel Effect - - - Join the Community & Get Your Questions Answered: CabralSupportGroup.com - - - Dr. Cabral's Most Popular At-Home Lab Tests: > Complete Minerals & Metals Test (Test for mineral imbalances & heavy metal toxicity) - - - > Complete Candida, Metabolic & Vitamins Test (Test for 75 biomarkers including yeast & bacterial gut overgrowth, as well as vitamin levels) - - - > Complete Stress, Mood & Metabolism Test (Discover your complete thyroid, adrenal, hormone, vitamin D & insulin levels) - - - > Complete Food Sensitivity Test (Find out your hidden food sensitivities) - - - > Complete Omega-3 & Inflammation Test (Discover your levels of inflammation related to your omega-6 to omega-3 levels) - - - Get Your Question Answered On An Upcoming HouseCall: StephenCabral.com/askcabral - - - Would You Take 30 Seconds To Rate & Review The Cabral Concept? The best way to help me spread our mission of true natural health is to pass on the good word, and I read and appreciate every review!