Podcasts about Specs

Prince Tour racquets have developed a loyal following, but do they deserve more attention from today's players? The playtest is over, but the conversation is just getting started. In this episode of Beyond the Playtest, the team dives deeper into the Prince Tour 2026 racquet lineup, discussing who each frame is best suited for, standout performance characteristics, on-court feedback, and how these racquets compare to other popular player's frames on the market. Whether you're a longtime Prince fan or considering making the switch, this episode offers additional insights to help you find your perfect match. Take a closer look at the Prince Tour Racquets & Specs: https://www.tennis-warehouse.com/Prince_Tour_Racquets/catpage-PRINCETOUR.html Happy Hitting!

THIS EPISODE IS BROUGHT TO YOU BY: GPRS Before you cut, core, drill, trench, or start guessing what is inside the slab, call GPRS. GPRS helps contractors locate what is hidden below the surface with ground penetrating radar, utility locating, concrete scanning, video pipe inspection, leak detection, and mapping services.They help keep your jobsite safer, reduce costly hits, and give your team better information before the work starts.Learn more here: https://www.concretelogicpodcast.com/gprs ON THIS EPISODE OF THE CONCRETE LOGIC PODCASTIs Type IL cement really the reason concrete started acting different, or did it just expose the problems we already had?Type I/II cement may be making a comeback because contractors, producers, and owners want concrete to act like concrete again.But Concrete Bob Higgins says we need to be careful.Because before Type IL showed up, the concrete industry still had scaling, dusting, cracking, bad curing, water problems, surface failures, and specs that cared more about 28-day strength than long-term durability.So if Type I/II comes back, will the problems go away? Or will we lose our favorite excuse?In this episode, Seth and Bob talk about what really changed in cement, why older concrete behaved differently, why today's concrete may be more sensitive than the standards admit, and what the industry needs to fix before it repeats the same mistakes.Type IL may have exposed the problem. But it may not be the whole problem. WHAT YOU'LL LEARN · Is Type IL cement really the problem, or did it expose bad habits? · Why Type I/II cement may be coming back · What concrete problems existed before Type IL became common · Why older cement was coarser, slower, and often more durable · How finer cement changed heat, curing demand, cracking, and permeability · Why Type I and Type III cement are closer than most people realize · What self-desiccation means and why it matters at the concrete surface · Why the top inch of concrete may be the weakest link · What contractors and producers should ask before switching back to Type I/II · Why going back to Type I/II cement does not fix bad concrete habits CHAPTERS 00:00 Is Type IL really the problem? 04:03 Why Bob says the industry needs this conversation 06:07 What cement was like before modern concrete problems 08:17 Same 28-day strength, but more permeability 09:25 Type I vs Type III cement 13:19 Why curing may not be protecting the top inch 16:47 What self-desiccation means in plain English 18:52 Why precast concrete can have a surface problem 21:50 What to ask before switching back to Type I/II 24:07 Bob's Type IL limestone float experiment 25:29 Why the industry cannot waste this opportunity 27:17 Next topic: are admixtures being mishandled? GUEST INFO Bob Higgins, Concrete Bob Concrete chemistry consultant and returning guest on the Concrete Logic Podcast. Guest link: https://www.concretelogicpodcast.com/guests/robert-higgins/ CONCRETE LOGIC ACADEMY The people who understand concrete are the people who get listened to. Not the loudest person in the meeting. Not the guy repeating what he heard ten years ago. Not the person blaming every problem on the latest material change. The person who understands the “why” behind the concrete usually has the most valuable voice in the room. That is what Concrete Logic Academy is built for. You get practical concrete education, PDH courses, and real-world lessons pulled from the same topics we cover on the Concrete Logic Podcast. Cement changes. Specs change. Admixtures change. Owners change their minds. Your knowledge needs to keep up. Start learning here: https://www.concretelogicpodcast.com/concreteschool SUPPORT THE PODCAST If the Concrete Logic Podcast gives you value, send a little value back. You can support the show here: https://www.concretelogicpodcast.com/support/ You can also support the show through our KUIU affiliate link: https://www.concretelogicpodcast.com/kuiu Interested in sponsoring the podcast or working with Concrete Logic Media? Email Seth: seth@concretelogicpodcast.com CREDITS Producers: Jodi Tandett and Concrete Logic Media Music by: Mike Dunton https://www.mdunton.com/ WHERE TO FIND SETH Concrete Logic Podcast: https://www.concretelogicpodcast.com/ YouTube: https://www.youtube.com/@concretelogicpodcast LinkedIn: https://www.linkedin.com/in/seth-tandett/ Concrete Logic Academy: https://www.concretelogicacademy.com/ Until next time, let's keep it concrete.

Daniel and James kick off a packed ADSN rundown by celebrating hitting #1 in Namibia, then dive into Alphabet's staggering $80 billion capital raise arguing it's not just about compute buildout but a strategic move to suck capital away from soon-to-IPO competitors like SpaceX, Anthropic, and OpenAI. From there, they unpack the app distribution crisis created by agentic AI tools: everyone can build now, but the audience, budget, and creative genius to actually get discovered are nearly impossible to find.The back half covers the Substack vs. Beehiiv battle over audience ownership, why ChatGPT is becoming the new Facebook blue app, Apple's potentially risky WWDC AI strategy, and a Northbeam stat showing just 1.4% of Meta ad accounts produce 36% of all creative. They close with a comparison of AI adoption to electricity — the real gains don't come from plugging in, they come from redesigning the entire workflow — and primary posts on the risk of founding and Snap's upcoming Specs launch.Thank you to our sponsors:AdQuick – Making OOH advertising as easy to plan, buy, and measure as digital. ⁠adquick.com⁠⁠Thrad.ai⁠ — Building the advertising infrastructure for AI. ⁠thrad.ai​beehiiv — The all-in-one platform for newsletters, websites, and every tool you need to grow and earn. ⁠⁠beehiiv.com⁠​The Farm — Fraction commercial legal with an in-house approach to outside counsel. thefarmllp.com STAY CONNECTEDJames on Twitter & LinkedIn – /jamesborowDaniel on LinkedIn, Instagram, TikTok – /danieldrugerSubscribe & leave a ⭐⭐⭐⭐⭐ review on Spotify & Apple Podcasts.

Deze week praten Wout Funnekotter, Arnoud Wokke, Jelle Stuip en Willem de Moor over hardwarebeurs Computex, de bal van het WK-voetbal voor mannen, een game in het Amsterdam van 1666, Steve Jobs in de tijd van de NeXT en alle AI-aankondigingen van Apple. 0:00 Intro0:19 Opening1:47 .post6:30 Ramageddon of niet, Computex blijft leuk28:02 Specs achterhalen van de WK-bal37:59 Rondlopen in Amsterdam met verkeerde klinkers43:38 Geoffrey Cain over Steve Jobs in de tijd van NeXT50:08 Apple maakt inhaalslag op gebied van AI1:07:42 Sneakpeek Link:Specs van de WK-balSee omnystudio.com/listener for privacy information.

In this episode, we sit down with Dr. Jay Wiles to unpack the science of nervous system regulation and Heart Rate Variability. Dr. Wiles explains why many popular nervous system tools fail to deliver lasting results, breaks down the role of the vagus nerve, and shares how Heart Rate Variability (HRV) can be used as a personalized metric for resilience and recovery. The conversation dives into resonant breathing, how to find your optimal breathing rate, and why comparing your HRV scores to others can be misleading. He also introduces his Nervous System Resiliency Training (NSRT) framework and discusses the innovative Ohm Health lamp, a device designed to help users train autonomic flexibility and improve stress resilience. Whether you're new to HRV or looking to optimize performance, this episode offers practical strategies for building a more resilient nervous system.Dr. Jay Wiles is a clinical health and performance psychologist, internationally recognized expert in HRV biofeedback and psychophysiology, and Chief Health & Performance Officer at Ohm Health. He has worked with professional athletes and organizations across the MLB, NHL, NFL, NBA, PGA Tour, Formula One, and Fortune 100 companies, helping high performers improve resilience, recovery, sleep, and performance under pressure. He is the originator of Nervous System Resiliency Training (NSRT), a structured, protocol-driven framework for training autonomic flexibility that translates the principles of nervous system regulation into measurable improvements in health, well-being, and human performance.SHOW NOTES:0:39 Welcome to the podcast!3:44 About Dr. Jay Wiles4:46 Welcome him to the show!6:35 Why nervous system tools don't work12:27 The Vagus Nerve explained15:38 Vagal nerve stimulators17:32 How HRV relates to the vagus nerve18:40 HRV 10120:45 Brake vs Gas pedal analogy23:09 Why you shouldn't compare HRV scores28:13 Genetics for HRV30:49 What to do if you're frustrated with HRV!31:47 What is Resonance?36:00 Resonant breathing38:26 Visual of dysregulated nervous system42:29 Optimal breathing rates47:05 How to determine your resonant breath rate!50:01 The Ohm Health lamp56:32 Specs & portability59:24 Recommended usage for benefits1:03:05 Are vagus nerve stimulators a waste?1:05:20 His opinion on other breathing techniques?1:07:00 How to get an Ohm lamp!1:07:49 Thanks for tuning in!RESOURCES:Website: Ohm Health - code: BIOHACKERBABESDr. Jay: www.thrive-wellness.comIG: @ohm.healthIG: @drjaywilesSupport this podcast at — https://redcircle.com/biohacker-babes-podcast/donationsAdvertising Inquiries: https://redcircle.com/brands

In this episode, George talks with Jodi Gottlieb, a voiceover coach with more than 20 years of industry experience and a background working with major networks. Jodi shares how she coaches established voice talent who are ready to raise their game, especially in commercial auditions where subtle, natural choices can make all the difference. George and Jodi discuss common audition mistakes, why dramatic pauses often work against you, how to use two different reads strategically, and what it really means to “show range” without ignoring the specs. They also explore the impact of AI on the voiceover industry — including Jodi's concerns about lost opportunities and her belief that audiences can still hear the difference when a performance is genuinely human.   00:00 Sponsor and Offer 00:31 Booth Mindset Tips 00:56 Meet Coach Jodi 02:56 Audio vs Video Podcasts 04:17 Remote Sessions Connection 08:23 Who Jodi Coaches 11:37 How She Started Coaching 15:46 Commercial Specs Myth 20:26 Disqualifying Reads 25:31 Directed Auditions Help 27:09 Demo Production Process 29:43 What Makes Demos Work 29:51 Demo Spots Under 10 Seconds 31:16 Variety and Money Voice 33:00 Audition Takes and Specs 35:59 Specs vs Reality in Sessions 38:02 Stop Over Editing Auditions 42:02 Separate Roles and Take Breaks 47:03 AI Voices and Industry Shifts 52:12 Calling Out AI and Audience Detection 56:26 Wrap Up and Contact Info  

Discover why GVWR and cubic yard capacity matter more than trailer size alone. Experts break down Maxx-D, Load Trail, Texas Pride, and Hillcrest 7x14 models, revealing payload gaps up to 1,800 pounds and how sidewall height dictates your real hauling power.Info: https://www.poplarblufftrailer.com/blog/7-x-14-dump-trailer-capacity-yards--weight-limits--106964?category=5770 Poplar Bluff Trailer City: Poplar Bluff Address: 135 Hwy T Suite B Website: https://www.poplarblufftrailer.com/

Chris and Amy are getting their own day at Busch Stadium on June 17; what are some good 'call signs' for Chris and Amy when they're at the Air Show tomorrow?; Tom Ackerman called-out Chris over pickleball this morning; Did you see this? Spotify listeners are choosing nostalgia; Lynn Worthy joins from the Post-Dispatch to talk Cardinals; Major Garrett from CBS on the comings-and-goings in Washington, DC; and Bill McDermott previews the men's World Cup tournament,

Eagle Farm plays host to Group 1 racing once again this Saturday with the Fillies to do battle in the QLD Oaks. We take an in depth look at a great day of racing in Queensland as well as previewing all the key races from Flemington, Morphettville Parks and Royal Randwick in this week's SULTS' SPECS.Other segments included in this week's episode:The Sultan's SupperPack Ya Nags2 UNITSOutro: Deadstar - Deeper WaterOur South Australian set is powered by Dare to Dream, a racehorse ownership initiative giving you the chance to own a share in a racehorse with reputable trainers at an affordable price.Head to daretodream.com.au for more information.Imagine what you could be buying instead. For free and confidential support, call 1800 858 858 or visit gamblinghelponline.org.au.

THIS EPISODE IS BROUGHT TO YOU BY: GPRSBefore you cut, core, drill, trench, or start guessing what is inside the slab, call GPRS.GPRS helps contractors locate what is hidden below the surface with ground penetrating radar, utility locating, concrete scanning, video pipe inspection, leak detection, and mapping services.They help keep your jobsite safer, reduce costly hits, and give your team better information before the work starts.Learn more here: https://www.concretelogicpodcast.com/gprsON THIS EPISODE OF THE CONCRETE LOGIC PODCASTThe concrete industry spent the last few years blaming Type IL cement for almost everything.Cracking. Scaling. Low breaks. Slow set times. Higher water demand.Now Type I/II cement may be making a comeback.So what happens when the “bad guy” leaves the room and the same concrete problems are still standing there?Rich Szecsy joins the show to explain what he is seeing in the Dallas-Fort Worth market, why cement suppliers are shifting, and why this move back to Type I/II may expose an uncomfortable truth.Maybe Type IL caused some problems.Maybe it didn't.But concrete was never problem-free before Type IL showed up.WHAT YOU'LL LEARNIs the cement market really shifting back to Type I/II?Why did Type IL become so common after 2020?What happens when one cement type gets blamed for every concrete problem?Will cracking, scaling, low breaks, and set delays disappear?Why the producer-contractor relationship matters more than internet argumentsHow ready-mix producers may handle Type IL and Type I/II at the same timeWhy the market, not the noise, decides which cement gets usedCHAPTERS 00:00 Introduction 01:02 The big topic: Type I/II cement coming back 01:26 How to support the Concrete Logic Podcast 03:34 Rich's view on the Type IL vs Type I/II shift 04:24 Why Type IL became more available after 2020 05:31 Rich's 100% placement rate during the supply crunch 06:44 Concrete complaints blamed on Type IL 07:45 What happens if Type I/II returns and problems continue? 09:33 Contractors adjusting to changing cement types 10:07 Micro business needs vs macro industry needs 10:59 Past material changes that caused industry panic 11:24 Why concrete has always had variability 12:28 The old Type I vs Type II confusion 12:43 What cement suppliers are telling customers 13:05 Is the market asking for Type I/II again? 14:00 Why the market decides which cement wins 14:58 How quickly Texas shifted from Type I/II to Type IL 16:08 How ready-mix producers may handle both cement types 16:47 Submittals that allow either Type IL or Type I/II 17:29 Rich's blunt definition of quality 18:35 Why the producer-contractor relationship matters most 19:51 Jobsite meetings, AI research, and “raspberry” 20:54 Is the Type I/II shift really happening? 21:28 Closing thoughtsGUEST INFORich Szecsy, CEO, Big Town Concrete https://www.concretelogicpodcast.com/guests/rich-szecsy/CONCRETE LOGIC ACADEMYThe people who understand concrete are the people who get listened to.Not the loudest person in the meeting.Not the guy repeating what he heard ten years ago.Not the person blaming every problem on the latest material change.The person who understands the “why” behind the concrete usually has the most valuable voice in the room.That is what Concrete Logic Academy is built for.You get practical concrete education, PDH courses, and real-world lessons pulled from the same topics we cover on the Concrete Logic Podcast.Cement changes. Specs change. Admixtures change. Owners change their minds.Your knowledge needs to keep up.Start learning here: https://www.concretelogicpodcast.com/concreteschoolSUPPORT THE PODCASTIf the Concrete Logic Podcast gives you value, send a little value back.You can support the show here: https://www.concretelogicpodcast.com/support/You can also support the show through our KUIU affiliate link: https://www.concretelogicpodcast.com/kuiuInterested in sponsoring the podcast or working with Concrete Logic Media?Email Seth: seth@concretelogicpodcast.comCREDITSProducers: Jodi Tandett and Concrete Logic MediaMusic by: Mike Dunton https://www.mdunton.com/WHERE TO FIND SETHConcrete Logic Podcast: https://www.concretelogicpodcast.com/YouTube: https://www.youtube.com/@concretelogicpodcastLinkedIn: https://www.linkedin.com/in/seth-tandett/Concrete Logic Academy: https://www.concretelogicacademy.com/Until next time, let's keep it concrete.

Podcast #784 invites you to feel the warmth of The Creepy Jingles, The Now, The Specs, John Hiatt, Brad Marino, Guided By Voices, Franklin, & Maia and the Squires.

The Alan Cox ShowSee omnystudio.com/listener for privacy information.

Are we officially entering the "Eternal Sloptember"? This week on the Friday Deploy, Ben and Andrew unpack the quiet rebellion against skyrocketing API costs as teams transition to fine-tuned local models. They also explore the changing physical architecture of AI data centers, the dangers of using autonomous tools as a crutch for broken workflows, and why spec-driven development is critical for keeping agentic code in check. Finally, the hosts share their latest personal agent experiments, from benchmarking open-source models on a local Mac Studio to taming an AI-generated second brain.Learn why: LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight PlatformsFollow the show:Subscribe to our Substack Follow us on LinkedInSubscribe to our YouTube ChannelLeave us a ReviewFollow the hosts:Follow AndrewFollow BenFollow DanFollow today's stories:Outsourcing plus LocalAI will soon become more economical vs Frontier labsAI Datacenters Were Built for GPUs. What Happens When You Remove the GPUs?"The AI Can Do It" Is Not an Excuse To Tolerate a MessThe Eternal SloptemberI'm tired of talking to AIIf you let AI do your writing, I will come to your house and kill youA Blast from the Past: SDD and the Illusion of Known ScopeAndrew's paper: Mise en Place for Agentic Coding: Deliberate Preparation as Context Engineering MethodologyOFFERSStart Free Trial: Get started with LinearB's AI productivity platform for free.Book a Demo: Learn how you can ship faster, improve DevEx, and lead with confidence in the AI era.LEARN ABOUT LINEARBAI Code Reviews: Automate reviews to catch bugs, security risks, and performance issues before they hit production.AI & Productivity Insights: Go beyond DORA with AI-powered recommendations and dashboards to measure and improve performance.AI-Powered Workflow Automations: Use AI-generated PR descriptions, smart routing, and other automations to reduce developer toil.MCP Server: Interact with your engineering data using natural language to build custom reports and get answers on the fly.

Stop cranking stuff out. That is the first move John Henkel wants every product marketer to make before they touch another asset. In this episode of Content Amplified, John, who leads product marketing for the AV segment at Netgear, shares how he keeps content tied to a real user and a real purpose instead of a list of specs. John walks through where engineering-led companies drift away from the problem they actually solve, how he uses trade-show conversations and weekly sales-team meetings to validate the user before a piece ships, and the trick of picking up the phone to get integrators invested in feedback so they tell you what is wrong instead of saying "looks great." He also shares the simple spreadsheet audit he is running right now at Netgear, mapping every asset to its audience and desired action so the team can see what to keep, kill, or rebuild. If your content calendar is full but your sales team is not asking for what you ship, this one is for you.About JohnJohn Henkel leads product marketing for the AV segment of Netgear's business division, where he has spent the last six and a half years bridging the AV and IT worlds. Before Netgear, John spent roughly fifteen years as a video editor making commercials and longer-form content, then moved to the manufacturer side at a series of AV companies, picking up product management, tech writing, and marketing along the way. He describes himself as a marketer who learned the craft from the user side of the equation, which shapes how he thinks about every piece of content his team ships.Show Notes- Connect with John on LinkedIn: https://www.linkedin.com/in/henkel/Text us what you think about this episode!

Dump trailer prices in Illinois range from seven thousand to over twenty-five thousand dollars. Discover the GVWR sweet spot, CDL thresholds, hoist types, and winter maintenance tips contractors and property managers need to avoid costly mistakes and maximize trailer longevity.Info: https://www.poplarblufftrailer.com/blog/dump-trailers-for-sale-in-illinois-cost--best-dealers--105855 Poplar Bluff Trailer City: Poplar Bluff Address: 135 Hwy T Suite B Website: https://www.poplarblufftrailer.com/

Eagle Farm hosts two massive Group 1s this Saturday and with average weather forecasts right around the country, it shapes as a day where you'll want horses that can get their toe into the ground. We also preview all the key races from Caulfield, Morphettville and Rosehill in this week's SULTS' SPECS.Other segments included in this week's episode:The Sultan's SupperPack Ya Nags2 UNITSOutro: Weezer - Say It Ain't SoOur South Australian set is powered by Dare to Dream, a racehorse ownership initiative giving you the chance to own a share in a racehorse with reputable trainers at an affordable price.Head to daretodream.com.au for more information.Imagine what you could be buying instead. For free and confidential support, call 1800 858 858 or visit gamblinghelponline.org.au.

Specs is back for his yearly appearance!If you'd like to work with us, email the studio on workwithfellas@fellasstudios.comJoin Fellas Loaded: https://fellasloaded.com/explore/Get The Worlds Comfiest Hoodies - http://www.165thfloor.co.ukWatch The Clips: https://www.youtube.com/@FellasLoadedClipsListen on Spotify: https://shorturl.at/xBCPUListen on Apple Podcasts: https://shorturl.at/opIU0Join the Subreddit: https://www.reddit.com/r/FellasPodcastFollow us on Instagram - http://www.instagram.com/thefellasinstaFollow us on TikTok - https://www.tiktok.com/@thefellaspod?lang=enCal: https://twitter.com/Calfreezy https://www.instagram.com/calfreezy/Chip: https://twitter.com/yungchip https://www.instagram.com/theburntchipAB: https://www.youtube.com/@ABvloggin https://www.instagram.com/alfiebuttle

Discover what really drives dump trailer prices in Missouri, from compact 10-footers to heavy-duty goosenecks. Experts break down GVWR math, hydraulic systems, licensing requirements, and the dealer comparison that saves contractors time and money.Info: https://www.poplarblufftrailer.com/blog/dump-trailers-for-sale-in-missouri-sizes-price--where-to-buy--105853 Poplar Bluff Trailer City: Poplar Bluff Address: 135 Hwy T Suite B Website: https://www.poplarblufftrailer.com/

We Sit down and chat with Levi of Prisitne Actions, We talk about how he got into the bussiness. The Features and Specs of the Actions. New projects in the works and much more !

In der aktuellen Folge, die ursprünglich als Livefolge zur Aroweek aufgenommen wurde, sprechen Finn und Chris mit Samu vom Podcast ACE AROund the Cake über ihre Erfahrungen als Bi+ Aros. Sie unterhalten sich darüber, wie ihre Aro*spec und M*spec-Identitäten zusammenhängen und ihre Coming Outs, thematisieren aber auch Überschneidungen in Bezug auf Queerfeindlichkeit und überlegen, was sie sich von Bi+ und Aro-Communitys wünschen würden.Moderation: Finn, ChrisGastperson(en): SamuProduktionsleitung: FinnRedaktion: Samu, Noir, Finn, ChrisSchnitt: FinnQualitätssicherung: Chris, Katharina, Delfin This work is licensed under a Creative Commons Attribution 4.0 International License Content NotesAnmerkung: Je nach verwendetem Player können die Zeitstempel leicht von der tatsächlichen Zeit in der Folge abweichen.00:02:26-00:02:43 | Erwähnung von Amatonormativität, Queerfeindlichkeit, Bi-Feindlichkeit und Aro*-Feindlichkeit im Rahmen der Inhaltshinweise00:10:04-00:10:12 | Gatekeeping (internalisiert), internalisierte Ace*spec-Feindlichkeit00:13:34-00:13:45 | Distanzerfahrung unter allosexuellen Personen00:16:39-00:16:47 | Internalisierte Bi-Feindlichkeit und Gatekeeping00:24:00-00:24:18 | Referenz auf Gewalt (Bedrohung mit einer Waffe) im Rahmen eines Vergleichs00:27:56-00:28:04 | Amatonormative Formulierung (Sprachliche Hierarchisierung von sexuell- und/oder romantischen Beziehungen über Freund*innenschaften)00:29:02-00:29:19 | Referenz auf Polizei (“Labelpolizei”)00:35:13-00:35:42 | Erwähnung von Beziehungsende / Trennung, Eifersucht in Paarbeziehungen, negative Reaktionen von Partnerpersonen auf das Coming Out als polyamor00:38:04-00:38:08 | Binäre Sprache00:43:00-00:44:22 | Queerfeindlichkeit (M*spec-Feindlichkeit, Aro*spec-Feindlichkeit), Vorurteile, Zitat einer aro*spec- und alloaro-feindlichen Aussage, Amatonormativität, Abwertung von Sex außerhalb von Paarbeziehungen00:45:39-00:55:11 | Queerfeindlichkeit (M*spec-Feindlichkeit, Pan*-Feindlichkeit, Aro*spec-Feindlichkeit), Annahme dass M*specs nicht Aro*- und/oder Ace*spec sein könnten, Stereotype queerer Identitäten in z. B. Memes, Besprechung aro*spec- und m*spec-feindlicher Vorurteile, Amatonormativität, Compulsory Heterosexuality/romanticism, Vorurteile gegenüber in Polybeziehungen lebenden Personen, Slut Shaming, Abwertung von Promiskuität, mitunter unangenehme Reaktion auf ein Coming Out als poly(affactionate)00:55:13-00:59:14 | Queerfeindlichkeit, Unsichtbarkeit von Aro*spec- M*spec-Identitäten, Exklusionismus innerhalb von M*spec-Communitys und queeren Communitys (Absprechen von Queer-Sein), Druck / Forderung sein Label beweisen zu müssen, Queer Impostor-Syndrome00:56:45-00:57:03 | Binäre Sprache01:00:28-01:01:21 | Queerfeindlichkeit, Exklusionismus, Annahme Aro*specs könnten nicht bi+ sein, Vorurteile01:02:11-01:03:35 | Gatekeeping, Allonormativität und Amatonormativität in M*spec-Communitys, Unsichtbarkeit von Aro*spec-Identitäten01:04:33-01:06:18 | Bi- bzw. M*spec-Feindlichkeit, Vorurteile, Zuschreibungen, Slut Shaming, Sex-Negativität / Sex-Moralismus01:06:17-01:08:43 | Unsichtbarkeit von Aro*spec-Identitäten, Entfremdungsgefühl, alloromantisch-feindliche Aussage (wird direkt als problematisch eingeordnet), Distanzerfahrung unter alloromantisch-allosexuellen Personen, Sex-Negativität01:09:53-01:10:36 | Entfremdungsgefühl01:11:30-01:12:22 | Gatekeeping, Infighting01:13:46-01:15:25 | Sex-Negativität / Sex-Moralismus, Queerfeindliche Vorurteile (Erwähnung) Kapitelmarken00:00:00 | Intro00:00:24 | Begrüßung und Einleitung00:02:26 | Inhaltshinweise00:03:20 | Definition: M*spec00:04:08 | Aro*spec-Label und Erleben der Moderierenden00:08:08 | Verortung auf dem sexuellen Spektrum00:14:20 | Intersektion: Aromantisches Spektrum und M*spec-Identität00:18:57 | Coming Out00:34:30 | Beziehungsformen00:42:20 | Wahrnehmung von Außen und Queerfeindlichkeit00:59:47 | Aro*spec- und M*spec-Communitys01:10:46 | Bessere Communitys für Bi+ Aro*specs?01:15:35 | Was nehmen wir mit?01:19:03 | Verabschiedung, Dank und Kontaktmöglichkeiten01:21:12 | Outro Erwähnte InSpektren-FolgenInSpektren, Folge 68 – Bi, Pan, M*spec Teil I, https://inspektren.eu/bi-pan-mspec-teil-iInSpektren, Folge 69 – Bi, Pan, M*spec Teil II, https://inspektren.eu/68-bi-pan-mspec-teil-ii Shout-OutsIntrosprecher: KijargoIntro/Outro: John Bartmann – Jazzy DetectiveAudio-Player Uns findet ihr außerdem hierinspektren.euinstagram: inspektren_podcastfacebook: InSpektren.Podcasttwitch: InSpektren_Podcasttwitter: InSpektrenMastodon: chaos.social/@inspektrenDiscord: aspecgerman.deMail: info@inspektren.euYouTubeSpotifyAmazon MusicApple PodcastGoogle PodcastA*spec Vibes zum Anhören findet ihr auf unserer Spotify Playlist

Doomben Cup Day takes centre stage in Queensland this weekend, with racing also at Sandown Hillside, Royal Randwick and Murray Bridge. We've got all the key plays covered across the country, all in this week's SULTS' SPECS.Other segments included in this week's episode:The Sultan's SupperPack Ya Nags2 UNITSOutro: Solitaire - I Like LoveOur South Australian set is powered by Dare to Dream, a racehorse ownership initiative giving you the chance to own a share in a racehorse with reputable trainers at an affordable price.Head to daretodream.com.au for more information.Imagine what you could be buying instead. For free and confidential support, call 1800 858 858 or visit gamblinghelponline.org.au.

Take the 2026 AI Engineering Survey and get >$2k in credits and AIE WF tickets!This was recorded before Railway suffered a major GCP outage on May 19, despite being a multi-AZ, multi-zone mesh ring, with HA fiber interconnects between their Metal GCP AWS, because workload discoverability was unintentionally still tied to GCP. All has been resolved with a post-mortem.Railway did not start as an AI infrastructure company.It was founded in 2020 years before agents became the default way people thought about deploying software. Jake Cooper, formerly at Bloomberg and Uber, started Railway with a simple obsession: the activation energy to ship something to production should be near zero. Push code, get a URL, iterate. No Docker files, no Kubernetes manifests, no Ansible scripts stacked on Ansible scripts.For years, this was a slow grind. Railway spent its first 18 months hand-acquiring its first 100 users with Jake personally greeting every Discord signup on a second monitor.Today, Railway has raised $124m and is growing very fast. A 35-person team supports 3 million users, adding roughly 100,000 signups a week. Their bare metal data centers have a 3-month payback period vs. renting in the cloud, with 70% margins funding aggressive cloud bursting when needed. The servers they own have actually appreciated in value as RAM prices have climbed basically meaning the value of their hardware now exceeds the capital they've raised.From rebuilding Railway's network overlay over a weekend to moving the vast majority of workloads onto its own bare metal data centers, Jake Cooper is trying to build a new cloud for an agent-native world. In this episode, Railway's founder and “conductor” joins swyx and Alessio to unpack why the next era of software infrastructure is not just “Heroku but newer,” what agents need that humans did not, and why the old deployment loop of Git, PRs, CI/CD, and static cloud resources may be heading for a rewrite.We go deep on Railway's infrastructure stack: own-metal data centers, three-month cloud payback periods, cloud bursting, data center debt, Railpack, Nixpacks, Temporal, feature flags, Central Station, content-addressable filesystems, agent-safe production forks, and why the CLI may become more important than the canvas in an agent world. Jake also shares the founder journey behind Railway, how the company survived losing $500K/month, why it now serves millions of users with only 35 people, and why he believes the pull request is dying.We discuss:* How Railway went from a slow six-year grind to adding 100,000 users a week* How Railway thinks about agents as the next dominant software species* Why agents need version control, observability, compute, storage, and orchestration at 1000x scale* The economics of Railway's own-metal data centers and three-month payback* How Railway uses cloud bursting while scaling its own infrastructure* Why data center debt can be a better tool than venture debt for infra startups* Central Station, Railway's internal system for clustering customer feedback and incidents* Why responsible disclosure and over-communication matter for platforms* Why feature flags, progressive rollouts, and shadow traffic are essential for agents* Temporal's strengths, pain points, and why workflows matter for agents* Railpack, Nixpacks, Nix, and lazy-loaded content-addressable filesystems* Why “cattle, not pets” may change if you can clone the pets* Why Railway is building a new cloud from scratch instead of copying hyperscalers* The solo founder path, focus, writing, and how Jake thinks about company buildingRailway:* Website: https://railway.com/* X: https://x.com/RailwayJake Cooper:* LinkedIn: https://www.linkedin.com/in/thejakecooper/* X: https://x.com/JustJakeTimestamps00:00:00 Introduction: What Is Railway?00:02:07 Jake's Path to Railway00:06:13 Railway's Six-Year Growth Story00:08:52 Rebuilding the Business After the Free Tier00:11:17 Agents as the Next Software Platform00:13:29 Railway's Infrastructure Philosophy00:15:42 Bare Metal, Cloud Economics, and the Compute Crunch00:17:22 Cloud Bursting and Five-Cloud Networking00:20:20 Data Center Debt and Infra Financing00:23:31 Data Centers in Space00:25:24 What Agents Need From Infrastructure00:28:24 CLIs, Canvas, and Agent-Native UX00:35:15 Central Station, Incidents, and Responsible Disclosure00:40:30 Safe Rollouts, SRE Agents, and Production Forks00:45:00 AI SRE, Specs, Code, and Tests00:48:24 Self-Replicating Infrastructure and the New Serverless00:53:18 Heroku, Temporal, and Workflow Engines01:04:07 Railpack, Nixpacks, and Lazy-Loaded Filesystems01:06:01 Coding Agents, Token Spend, and Roadmap Acceleration01:10:56 The Pull Request Is Dying01:12:28 Feature Flags and the Agent-Era SDLC01:16:15 Cattle, Pets, and Cloning Machines01:19:29 Solo Founder Lessons01:24:12 Focus, GPUs, and Building a New Cloud01:28:20 Closing ThoughtsTranscriptAlessio [00:00:00]: Hey, everyone. Welcome to the Latent Space Podcast. This is Alessio, founder of Kernel Labs, and I'm joined by Swyx, editor of Latent Space.Swyx [00:00:10]: Hey, hey, hey. Today we're in the studio with Jake Cooper of Railway.Alessio [00:00:14]: Conductor of Railway.Swyx [00:00:15]: Conductor at Railway. Yeah.Alessio [00:00:16]: Choo-choo.Swyx [00:00:17]: Do you actually have that anywhere, like on your business card?Jake [00:00:20]: We call some of our volunteer moderators conductors. I don't have a business card. We're not that big yet. At some point I will. I got handed a nice business card from the Supermicro folks, and I was like, “Damn, this is pretty official.”Swyx [00:00:30]: Business cards are coming back.Jake [00:00:32]: They're cool. They're hip. The conductor thing is good. We're trying to figure out what we want to call each other internally. Some people think it's super cringe and say, “You don't need a name for people internally.” Some people want to call each other something. We still don't have a really good one.Jake [00:00:55]: We've got New Railcrews, Trainiacs. Nothing has stuck yet.Swyx [00:01:00]: I like Trainiac. Trainiac sounds good. Railwayians. For those who don't know, what is Railway? Let's give people a crisp definition up front.Jake [00:01:09]: Railway is the easiest way to ship anything. You go to the canvas, or you talk with Claude, and you say, “Deploy a Postgres instance, deploy my GitHub repository, run this code,” and you're off to the races.Swyx [00:01:22]: You've got a nice animation on the landing page.Jake [00:01:24]: Thank you. None of my work, by the way. They don't let me touch the design stuff anymore.Jake [00:01:25]: We want to make it trivially easy not just to deploy things, but to evolve applications over time. Most tooling right now stacks entropy on top of entropy: Docker, Kubernetes, Ansible scripts, and all these other things. If we can version all of your software and keep track of all the changes, then we can make it trivial to clone environments, fork into a parallel universe, get copies of production data, get copies of any services, make changes, validate them, and collapse them back in without reproducing everything across a staging environment.The Railway Origin Story: From Uber Systems to a New CloudSwyx [00:02:07]: I was looking at your background: Bloomberg, Uber. Nothing immediately stands out as, “This guy is going to found the next great platform as a service.” What prepared you for Railway?Jake [00:02:21]: It was curiosity to keep going deeper. I started out on front-end stuff, working on Wolfram Mathematica and porting it over. Then I briefly moved to Bloomberg, then toward Uber and distributed systems, taking the Jump Bikes systems and moving them to a distributed system built on top of Cadence, the pre-Temporal Temporal.Swyx [00:02:44]: Which, by the way, I'm happy to talk about, pros and cons.Jake [00:02:48]: Totally.Swyx [00:02:51]: But let's do the Railway story.Jake [00:02:52]: It has been a continual step of wanting an experience. Whether it's walking up to a bike, unlocking it, and having it work frictionlessly, or something else, the depth required to make that happen follows from the experience. A lot of the work I do, and a lot of the team does, is in service of that experience. We fundamentally don't care how deep we have to go. We will swim to the bottom of the swimming pool to get the experience.Jake [00:03:17]: I don't have a physics PhD. I did an EECS degree. It has always been about figuring out the next step: how do we get there? That's what led to starting Railway for that experience and then moving all the way to bare metal data centers. I was adding patches to the kernel this week to get the experience there because I can see how much better it can be.Swyx [00:03:49]: Other patches to the Linux kernel this week?Jake [00:03:51]: Yeah. Not upstream. Our fork.Swyx [00:03:52]: That's a flex. Railpack? No, this is different. This is the OS on top of Railpack?Jake [00:03:57]: No, this is an actual kernel patch. It's always literally: what do we have to do to get that experience? Then figure it out. Anything is figureoutable.Swyx [00:04:10]: Would you send the patch upstream, or does it not fit other use cases?Jake [00:04:13]: Maybe. We have to work out the experience internally. It has to do with the storage layer we're building for some of the agentic stuff. Maybe it'll be useful upstream, but it's deeply useful for us internally.Open Source, Forks, and Non-Deterministic VersioningSwyx [00:04:29]: You mentioned open source before. How do you think about starting from open source, and then coding agents letting you do a lot more from forks of it?Jake [00:04:38]: GitHub's original sin is that it's almost a series of broken pointers. You have this thing, then you clone it, and now you've lost the whole upstream. How do we make it trivial for people to modify really small pieces of it?Jake [00:04:51]: We think of Git in a discrete sense: I've either made a change and merged upstream, or I haven't. What would it look like if it were percentage-based, a little more non-deterministic, or a stream of changes that users traverse as a percentage rolled out in general and then rolled all the way up?Jake [00:05:13]: We have the open-source kickback program and let you deploy templates because we want to make it trivial for people to version these shards over time. It solves a large problem around authentication, authorization, and security. NPM has a way to define, “Don't take any new packages.” The ideal end state is that you roll out progressively to users with the minimum impact zone and continue rolling up. JPMorgan should probably be the last one on the patch line, for all our sakes, because our money and livelihoods are there.Jake [00:05:53]: It's okay if Johnny Vibe Coder gets a broken patch because there's so much entropy in the system that the rubber has to meet the road at some point. You have to test at varying levels.The Long Grind: First Users, Free Tier, and Making the Business WorkSwyx [00:06:13]: I wanted to pull up this glorious chart, which is your usage or number of daily signups?Jake [00:06:22]: Daily signups, I think.Swyx [00:06:24]: You started six years ago. It was a slow grind, and now you're on a rocket ship. You say, “Don't doubt your fight and don't quit.” Maybe pick out certain points that were key inflections for the company.Jake [00:06:40]: At the start, it's about getting your first 100 users, hell or high water. We had a website and a support link. The support link was the Discord channel. I had notifications on with two monitors: the monitor I was working on and the other monitor with Discord. If anybody came in, I was immediately like, “Hey, how's it going?” It was rare, so getting those first 100 users to come back was the start.Jake [00:07:14]: Then you build a consultancy factory because users want all these things. You have to go back to the board and ask, “What is the actual product offering I want to build on top of this?”Jake [00:07:28]: VCs want charts that always go up and to the right, but in reality you don't necessarily want charts that look like that. For us, there have been periods of expansion where we add features to test use cases, and periods of compaction where we ask, “If the experience we have is good, how do we make it significantly better?” Maybe we strip out features that don't fit our ICP anymore.Jake [00:07:57]: The boom from 2022 to 2023 came from the free tier. Everybody under the sun was using it.Swyx [00:08:09]: A lot of Reddit bots and Discord bots.Jake [00:08:12]: And crypto miners. When you build an open product on the internet where anybody can sign up, the internet is a horrible place with so many things. You go through periods of asking, “How do I reach as many people as possible?” Then, “How do I fit the exact use case for the people who really matter and are really excited about this specific thing?”Jake [00:08:39]: Then there was a two-year period of making the actual business work. During the free-tier era, we were losing about half a million dollars a month.Swyx [00:08:59]: On a $20 million bank account.Jake [00:09:02]: On a $20 million bank account with maybe $50,000 a month in revenue. That's a horrible business. I don't know how anybody invested. But you have to go through it and say, “We have an experience people love, but the business has to work.”Jake [00:09:17]: There are two schools of thought. You can run the horrible business all the way up with bad margins, or you can go back and make it work. We've always wanted a super lean team. We're 35 people right now. It's very small.Swyx [00:09:36]: Supporting three million already?Jake [00:09:38]: Yeah. We're adding 100,000 users a week right now, so it's growing fast. We don't want to add headcount for the sake of headcount or throw bodies at problems. We want to build systems. It's hard to build systems during expansion because you're adding things to the system because people are asking for them or things are breaking.Jake [00:10:00]: We had to cut off the free users for a little while, rebuild the business, and make sure it worked. We want to reach as many people as possible because software is important. It's become difficult to create things in the physical world, so it's important to make it easy for people to build in the virtual world and have access to creation. But there are legs to that journey.Jake [00:10:30]: You can see divots in the charts. If you follow between 2025 and 2026, it's either summer or winter. People go on holiday with family.Swyx [00:10:50]: It affects that much?Jake [00:10:51]: Yeah. It's kind of B2C and kind of B2B. People are shipping constantly, then they stop. Our activation curve now shows more people activating on weekdays because we have more business users, so it smooths out over time.Agents as the New Interface to DeploymentSwyx [00:11:17]: Was there a point where you started prioritizing AI development or agent development?Jake [00:11:24]: We've prioritized agentic as a top-of-funnel thing. Over the last six months, we've deeply prioritized agentic as a mechanism to build and deploy things because we believe the curve is so steep and that is how people will build and deploy software.Jake [00:11:42]: It almost fundamentally doesn't matter whether this is dot-com or not because we're all on the internet anyway. If agents are going to deploy a bunch of things and we hit an inference wall at some point, we'll fix those problems. The dominant species over the next 10 years is that we've moved from assembly to C to C++ to JavaScript to words. You're going to need to close that loop.Swyx [00:12:13]: When you say this is dot-com, did you mean buying the domain, or the general case?Jake [00:12:17]: I mean the dot-com era, when companies had a huge run-up because people understood the internet was important. Then they hit bottlenecks, fundamental laws of physics, math didn't work, and everybody came back down to earth. But it didn't matter because the internet became so impactful. If you operate on a long enough time horizon, you should build these things anyway because you can see where it's going.Jake [00:12:45]: That's where I think a lot of agent stuff is. You get to a point where you're running thousands of agents in parallel. What is the inference cost? What is the compute cost? How do you make that efficient? How do you coordinate all this? We have issues coordinating humans; we don't even have good tooling for that. Now we have to figure out how to get agents to coordinate, safely version changes, and know when to raise their hand for someone to intervene. Otherwise it becomes an interrupt factory.Railway's Infrastructure Thesis: Network, Compute, Storage, and MetalSwyx [00:13:19]: Let's go right into the technical side. What are the core infrastructure or architectural beliefs of Railway that allow you to do what you do?Jake [00:13:29]: The primitives matter a lot for us. We need network, compute, storage, and orchestration around it. You need control over a lot of those things. We've talked a lot about how we don't really use Kubernetes because we want higher-order control to place workloads in very specific places.Jake [00:13:48]: The reason is that you have to be very efficient with agents: memory reuse and all these other things, or you're going to massively blow up your cost structure. Being able to rack and stack your own servers and build your own metal unlocks performance and cost. Experiences where you're running 1,000 agents in parallel are not massively cost prohibitive.Jake [00:14:13]: Token use and compute use are blowing up. Over time, those things have to get a lot more efficient. You can get a lot of margin to make those experiences solid by building your own metal. That's all in service of offering a differentiated experience to as many people as humanly possible.Swyx [00:14:51]: You have a data center in Singapore.Jake [00:14:53]: Yeah. We have two in every other region now. In Singapore, we're adding a second one in Q3.Swyx [00:14:58]: What's it like? I've never built a data center. Do you go to Equinix and say, “I want some slots?”Jake [00:15:05]: Yeah. Equinix. You basically go and say, “I want power and I want a cage.” They say, “Great, here's what it's going to be.” You rent the cage for a period of time, fill it with racks and servers, and hook up internet to it. That's all the pieces.Swyx [00:15:36]: Then you handle everything else.Jake [00:15:37]: You handle everything else.Swyx [00:15:39]: What's the math versus clouds doing it for you?Jake [00:15:43]: If we rented in the cloud, our payback period when we go to metal is about three months.Swyx [00:15:50]: Which is crazy.Jake [00:15:51]: It's nuts. That's four years of depreciated hardware. You're going to see a lot of this compute crunch because hyperscalers are buying up a lot of stuff. We're working directly with OEMs, resellers, and people building these machines: Supermicro, Dell, and others.Jake [00:16:11]: Upstream, there's a bunch of supply pressure. When we raised our last round, between deploying capital for servers and now, the amount of money we've raised is less than the amount of money we have in the bank plus the value of the servers because the servers have appreciated as RAM has gone up. It's nuts how valuable hardware has become.Jake [00:16:50]: If you look at hyperscalers, they deployed around $80 billion of capital expenditures this year, and next year will be more. That's a massive infrastructure build-out. You look at that and think it's crazy that they're spending way more than the Manhattan Project. But if every person is going to run dozens or hundreds of agents in parallel, you have no conceptual idea how much compute is required to make that experience happen, even if you're deeply efficient and sharing resources. And that doesn't even count inference.Swyx [00:17:22]: How do you plan the build-out? The growth chart is so vertical. Are you usually at 100% utilization as soon as racks are live? How far ahead are you planning?Jake [00:17:33]: We still maintain cloud presence for bursting. We work with AWS, GCP, and a few other clouds. We can rent, and then the moment we get space or power, we compact those workloads off the cloud. We started on the clouds, then built a system to migrate to our own metal. There's nothing that says you can't continually do that again, and that's exactly what we do. We never want to be compute constrained.Jake [00:18:09]: At the start of the year, we actually became compute constrained because one upstream provider wasn't able to give us quota at the rate we needed, and the hardware was slower. I spent a weekend rebuilding our entire network overlay so we could straddle five clouds: Oracle, AWS, ourselves, GCP, and one other one. We can do more than that now.Jake [00:18:38]: We got into a spot where we were trying to pack instances tight because we couldn't get enough compute. That led to a few reliability issues, which are now past us. I made a tweet pointing out that it's becoming harder and harder to acquire compute at the rate these models need to acquire compute. We got bit by it.Swyx [00:19:15]: How do you think about pricing knowing you might not have your own metal available at all times? Are you pricing assuming you need extra margin if you end up going into the cloud?Jake [00:19:26]: Because we've built out our metal data centers, our margins on metal are around 70%. We can deeply subsidize the cloud business if we want to scale at a reasonable rate. We have a few levers: metal, which makes the margins; cloud burst; debt to buy servers; and venture capital. It's an interesting operational problem: how much cash do we have, how much should we raise, how quickly can we deploy it, and can we scale revenue as quickly as we scale compute?Jake [00:20:05]: If we continue making it trivially easy for people to build and deploy, then the faster we close that loop and the more operationally excellent we are with capital, the faster the business can scale. It's almost a straight linear deployment rate.Financing Infrastructure: Hardware Debt, VC, and Operational LeverageSwyx [00:20:20]: I think infra startups raising debt is a tool people don't utilize enough or know enough about. What can you tell us about that? Is it secured against your CPUs?Jake [00:20:32]: It's secured against our hardware.Swyx [00:20:37]: What rates do you get? Who are the lenders?Jake [00:20:39]: We pay prime plus a spread, and we can refinance any of the debt as rates go down. The terms are pretty good. The unfortunate thing is that Twitter has no nuance, so people say, “Venture debt bad.” But as with all things, there are specific tools and areas where you can be deliberate instead of using one tool as a hammer. Venture capital is not the hammer for everything. You have to explore and figure out what works.Swyx [00:21:12]: VC is usually the most expensive financing you can get.Jake [00:21:15]: Yeah. I also think people think about VC incorrectly from a capital-raising perspective. Most people think, “How do I raise as much money as possible from whoever is probably the best I can get at that time?” That's close to right, but what we've tried to do is figure out what unfair advantage we can buy with that equity.Jake [00:21:34]: It's the most expensive equity you're going to give away at that point in time, assuming the company keeps getting better. How do you use it to work with someone stellar who complements you? In the seed stage, I had never started a company. Ray Tonsing had good advice, and I could text him all the time. He was really fast. Awesome.Jake [00:22:01]: Then with John and Erica at Unusual, they said, “You roughly know what you're doing building a product. We'll mostly leave you alone and be available for advice.” Amazing. Then we got to Series A and the business was an operational tire fire because we didn't know how to scale a business. Work with Erica, and Jordan is over at Redpoint, so bonus.Jake [00:22:28]: Now we've raised from TQ and FPV as we're moving into enterprises. Every step of the way, we've asked: who can we partner with at this specific time to unlock the next section of the journey? I don't know enterprise sales. As an engineer, I can eyeball what features we might need, and we have wonderful people internally who can help. But you want boardroom dynamics where everyone is aligned and asking, “How do we win this?” instead of bickering about strategy.Data Centers in Space and the Physics of ComputeSwyx [00:23:31]: You had a tweet about data centers in space. Why no data centers in space?Jake [00:23:37]: It's not “no data centers in space.” My hot take is that I think it is solvable. I've just never seen anybody solve it.Swyx [00:23:49]: You said, “How are you going to dissipate that much heat in a vacuum?” You're making a physics claim.Jake [00:23:55]: I haven't seen anybody prove how you're going to dissipate that much heat in a vacuum. It doesn't mean it's not possible. It just means nobody has brought it up yet.Swyx [00:24:05]: Astrophage.Jake [00:24:06]: I don't know what that is.Swyx [00:24:07]: The Martian thing. Okay, you're very logical.Jake [00:24:09]: It could work. A lot of people are putting the cart before the horse. They say, “We're going to put data centers in space.” Okay, but how? “We have time to figure it out.” It's like in The Martian where they ask how they're going to intercept something and say, “We'll figure it out.”Swyx [00:24:36]: Making a bet on human invention is weird because you blind trust that it can be solved. But with physics, there are first-principles bounds you can put on it. Maybe not. Maybe you're asking to travel time or break a fundamental thermodynamic law.Jake [00:24:57]: I don't know how VCs do this either. How do you know what's not possible and a grift versus what's possible but sounds completely insane? “We're going to put data centers in space.” Coin flip as to which it is, and I guess you'll know in 10 years. That's one cycle.What Agents Need: Versioning, Observability, and 1,000x ScaleSwyx [00:25:23]: Moving back to agents. The branching, fast spin-up, and orchestration you do feels like pre-work that happened to be exactly what agents want. What do agents want differently than humans?Jake [00:25:37]: They want the ability to version things. It's not that different; it materializes slightly differently. Agents want a way to test changes incrementally. Engineers have feature flags. Is there a reason agents can't use feature flags? I don't think so.Jake [00:25:54]: They want version control. Can we use Git or not Git? That one is up in the air. I think something outside Git will emerge for how we version these things over time. They need observability. You need to query what happened, when it happened, which steps failed, traces, logs, metrics, and all the rest. They need network, compute, and storage. They need to write files, save files, iterate on files, and snapshot file systems.Jake [00:26:25]: A lot of what humans needed is in line with what agents need. Branching and forking are not different; we're just moving 1,000 times quicker. It can look like you need something massively different, but what you need is something massively better than what existed. You need orchestration massively better than Kubernetes. You need networking probably better than Envoy. It goes all the way down the stack.Jake [00:26:55]: If the workload profile doesn't change so much as it gets massively compressed because you need thousands of these things, what assumptions change? etcd is going to melt. You need to replace it with something. You can go all the way down the stack and say, “That part has to change, that part has to change, and that part has to change.”Jake [00:27:19]: The interesting thing about the super-exponential curve is that you have to build systems where you can rip out those parts at any time because a new bottleneck might emerge. You get good at parallel agents, and a different part of the system breaks. So it's similar to what humans needed, but at 1,000x scale.Jake [00:27:55]: How do you do code review in the age of agents?Swyx [00:28:00]: You throw more agents at it.Jake [00:28:01]: You don't. But then who reviews for CVEs and all these other things?Swyx [00:28:07]: More agents.Jake [00:28:08]: And that's how we hit the inference wall. You can continually throw agents at the problem, but I think there's a limit to the number of agents you can throw at a problem.CLI, Agent Handles, and Closing the LoopSwyx [00:28:24]: You already had a CLI before it was cool. How is the shape of what you're exposing changing, if at all?Jake [00:28:28]: CLIs have always been cool. The CLI changes because we think about how to give Claude, Codex, ChatGPT, or any model a handhold.Jake [00:28:50]: A CLI is a single command: deploy, get logs, and so on. Things that were prohibitively annoying to humans are not annoying to agents. They're nice. If I handed you a CLI with 40 arguments and 600 flags, you'd think, “I'm never going to use all of this.” But if you hand it to an agent, it says, “This is excellent. I have so many handles to work with.”Jake [00:29:24]: If you're going to expose things to agents that way, you want as many handles as possible where they can get information, query dynamic information, and close the loop quickly. Most problems right now are about how to close the loop as quickly as possible. Where does the agent get stuck, and how can you remove that?Jake [00:29:49]: Telemetry is important. If you can tell where the agent gets stuck from the CLI and say, “12% of people deviate from the happy path because of this, and now I add this argument and drive it down to 2%,” you massively increase the rate of loop closure.Jake [00:30:03]: That's how we think about not just the CLI, but every point in the dashboard. It's a user journey: I hear about Railway. I get something deployed. I get my first green build or aha moment. I see an endpoint, logs, whatever. Then I iterate. The iteration loop is indefinite. The user wants to deploy a new thing, a Postgres instance, change code, and keep iterating.Jake [00:30:36]: If you focus on the iteration loops and what's blocking them from closing quickly, one thing we say internally is: you never want to be waiting on compute anymore. You always want to be waiting on intelligence. If you're waiting on compute, there's a bottleneck that needs to be destroyed because eventually that bottleneck becomes so large that another workflow emerges to change it.Jake [00:31:04]: We've built a product where you push code, build it, and so on. But I fundamentally believe the push-pull loop is going away. We'll get to a point where you make a small change in production, that change is versioned across your infrastructure, you're working alongside copy-on-write versions of your database and infrastructure, and then you merge it in and it's instantaneously live. That's the holy grail of loops. The push-pull-rebuild thing is a point of friction that we're removing entirely.Canvas as Output: Dashboards, Context Anchors, and HyperstructuresSwyx [00:31:43]: It's incredibly fast. If anyone hasn't tried it, that fast feedback is great. My hot take is that Railway was famous for its canvas, which visualizes your infrastructure and lets you manipulate it visually. But that was for humans. For the next phase of growth, Railway CLI is more important than canvas.Jake [00:32:05]: The canvas is funny because it's a mechanism to show changes over time. You're right that previously we used it a lot as an input. Moving forward, its goal is more like an output. You would go to the canvas, make changes, see them, and watch your infrastructure evolve. Now agents have access to the CLI and can make those changes. So the canvas becomes an output: what information does the human need at this moment to make suitable decisions about control requests? Do I approve this or not?Jake [00:32:57]: It also has to be an anchor for your context, a port in the storm. Think of it like layers in a file system. You start with a project, then drill down into services, then into a function or code, because you want to represent the entire thing not just in your head, but in the canvas. Other people can share that representation, think on the same wavelength, and move quickly.Jake [00:33:33]: A lot of organizations get in trouble as they scale because all the context lives in someone's head. “How does this microservice work?” “I have no idea; go ask this person.” Then you have whole categories of products built around context discovery. A lot of that melts away if you have a solid hierarchy and can infinitely nest services, code, context, and everything else all the way down. That's what lets you build these structures over time.Jake [00:34:18]: It's also what lets us build what I've called hyperstructures: things that are way bigger. You look at the Golden Gate Bridge and ask, “How did we build that?” There's a meme that we lost the technology. To some extent, yes, because the coordination that built those things evolved and changed. We lost some of the art of building structure as we jammed everything into Slack.Swyx [00:34:52]: But you jam everything in Discord.Jake [00:34:53]: Same point. It doesn't matter. It's message passing and interrupts, message passing and interrupts.Swyx [00:35:00]: So you're arguing there should be something better and more structured than Slack?Jake [00:35:04]: Yeah. For sure. I think Slack is awful, and Discord is awful too.Central Station: Context Routing, Support, and Incident ClustersSwyx [00:35:09]: This is the equivalent of my mom test. What have you done that has your solution to this?Jake [00:35:15]: Internally, we've built a tool called Central Station that aggregates all the context from our users. Every piece of feedback, every customer support item, everything gets aggregated into clusters. If an incident is brewing, we can determine how many users are affected and break off a discussion based on that.Jake [00:35:40]: That is more helpful than long-running channels where you're trying to decide which channel to put something in. If you can dynamically aggregate information and dynamically route it to the right person based on context, it works better. We know internally that these four people are close to networking. If we see a networking thing, we can drill it down to those four people. If it's with this part, we can look at the commits. This is no longer a manual process internally.Jake [00:36:13]: If you go to station or help.railway.com, that's why we built it. We wanted to scale with a massive amount of leverage by aggregating feedback.Swyx [00:36:27]: This is built in-house?Jake [00:36:28]: Yep.Swyx [00:36:29]: I remember helping out on this one with Angelo in 2023. You scale a lot with a very small team.Jake [00:36:38]: Yeah. We're about 10 times bigger now.Swyx [00:36:40]: You have your full developer code here? Very cool.Jake [00:36:44]: If you go to railway.com/stats, we expose this as a pub-sub-able thing. It's all real-time metrics. There's a way to get it as JSON somewhere if you care.Jake [00:37:01]: We're big on trying to build everything in public and talk about what we're working on. We've had issues in the past, and we'll say, “Here's how we're fixing these things.” We've gotten compliments and flak for incident reports. We're always trying to make them better and talk with people.Incidents, Disclosure, and Progressive RolloutsSwyx [00:37:20]: You had a big one recently. I liked that it was scoped to 3,000. You presumably used Central Station. Talk through what happened and how you address it internally as a team.Jake [00:37:38]: Internally, this one really sucked. It had to do with an upstream provider that didn't do the behavior it said it documented, which is unfortunate given they wrote the RFC for how the behavior should work. We rolled those things out, and Central Station caught it initially when a couple users said caches weren't invalidating. We turned it off immediately.Jake [00:38:03]: When you roll out to a large user base of three million people, you get a lot of disparate behaviors. We tested in staging and had tests, but we hit an edge case. We've hardened those systems, and now we can make that better. But it was a tough one.Swyx [00:38:39]: I always wonder how private disclosure is supposed to work if people find an issue. Are they supposed to contact you first? When you run a platform, these things will happen. What channels should people pursue to quietly resolve it before it becomes a bigger incident?Jake [00:38:59]: There's responsible disclosure. We err on the side of over-disclosing and letting you know something is wrong versus having your provider gaslight you. We've erred on sharing those things more publicly, even if they impact a small subset of users. That's a decision we've made internally. We have four values. One is honor. The honorable thing is to notify people to the widest degree at which they may have been affected or there was an issue, and then confront it head-on: why did it happen, what can we do better?Swyx [00:39:45]: Not the whole user base. That's because of incremental rollouts and other things?Jake [00:39:50]: Yeah. Progressive rollouts.Swyx [00:39:54]: That should be the norm at all large platforms.Jake [00:39:58]: It should. A variety of companies do this. There's the quote that Meta runs 10,000 different versions of Meta. To our earlier point about agents, they need the same thing. They need shadow traffic and all these other things. We've built so much ceremony around production being sacred that we need to make it trivially easy to test different behaviors in a safe environment. Then you can make mistakes in a safe environment.Safe AI SRE: Customer Agents, Forked Environments, and Production ParityAlessio [00:40:30]: Do you see a world where these things get automatically caught, not necessarily by your agent, but by your customer's agent? The cache invalidation issue seems easy to check if you know to look for it.Jake [00:40:44]: It's hard because to determine it, we almost need to hook into your observability infrastructure. That's why we have the template loop on the platform: so you can roll things out progressively. You can roll out to Johnny Vibe Coder initially, or push a shard that someone consumes at their own leisure. Or you can roll it out over weeks: 0.1% of people, 1% of people, early adopters, then all the way up. That's the non-deterministic version control we talked about earlier.Jake [00:41:30]: I believe that's where most things should go, because most companies end up building staged rollout systems in-house. It's the same thing built again and again at every company. There's a massive opportunity to consolidate developer debt.Alessio [00:41:45]: You should have a free tier. Model providers give free tokens if you let them use the data. You could give free compute if someone is the number-one shard that goes out and lets you plug into their observability.Jake [00:41:55]: We do that. That's why we talked about the impact on 3,000 people. We start with lower-impact people. Larger companies on the platform are last to receive those rollouts so they have a version of the platform that's deeply stable.Alessio [00:42:16]: I have three services, so I'm sure I get the first rollout. You can nuke my thing at any time. There are all these SRE agent companies. Observability people also want agents that fix upstream problems. You have your own agent in the canvas now. How do you see that playing out?Jake [00:42:39]: It's the stacking entropy problem. If you don't have primitives to make iteration in production safe, it becomes difficult. If you're an observability provider saying, “Here's the fix to this error,” assume 80% are good and make sense. But in the last 20% long tail of complex issues, if you let somebody stamp it, you create an opportunity for an incident.Jake [00:43:08]: That's why forked environments are important. People have staging, but it always drifts from production. You need primitives, workflows, and experience built first-party on the platform so you can fork any service at any point in time.Jake [00:43:33]: I think of the canvas as a sheet of transparency paper. The agent is a little guy you push up into the canvas. It should say, “I need to copy that service and that service so I can test these two things.” It gets a read-only copy of production. Anything that's PII gets marked as a transform when we clone the database, create a copy-on-write version, or read from it. Then the agent makes changes and asks, “Does this actually work?” as close to production as possible.Jake [00:44:22]: That's how close you have to be, or you get massive drift. The system becomes unstable. You see this with massive systems built on Docker for local, Kubernetes for production, and a specific thing for something else. That complexity slows developers and becomes unstable at scale, making it hard to iterate. We want to compress that way down and say, “As close to prod as possible is where we want to be.”From AISRE Skeptic to Agent BelieverSwyx [00:45:00]: I was texting Erica for questions, and she says you were originally not a believer in AISRE. Have you come around on it?Jake [00:45:10]: I flipped, but I'm still not a believer in AISRE if you don't have the primitives to make it safe. If you unleash AISRE on production infrastructure without safe primitives for copying volumes and making sure things are fine, it's going to nuke your production database. It's not a matter of if, but when. I'm a big believer in making those loops safe.Jake [00:45:33]: I was a deep AI skeptic until 2023. In 2024, I thought, “Maybe I can roughly make this thing do it.” In 2025, I thought, “Now I can hold this.” Over winter break, everybody came back saying, “It's almost impossible to hold this.”Swyx [00:46:01]: Did you see this on the Claude docs? CloudBot? OpenCloud?Jake [00:46:06]: It's gotten to a point where it's harder to hold it wrong than to hold it right. There's a scene in Avengers where Vision picks up Thor's hammer and says it's terribly well-balanced. It self-balances and works well. I'm a deep believer at this point that this will be the dominant species: assembly, C, C++, JavaScript, words.Swyx [00:46:35]: It feels like a big jump.Jake [00:46:37]: It is. But it's not like you abandon CPU-based discrete logic and move straight to fuzzy logic. You need both. Your skills should call code or applications or some static structure. You can use skills to distill what the procedure should be or how the code should act.Jake [00:47:02]: I'm coming to a thesis: you need three points. You need a clear spec defining the system, the code, and the tests. When you say it out loud, if you've been in engineering long enough, you're like, “Of course. That's an RFC, tests, and code.” But they all matter. Having them together lets them reinforce each other: the spec and tests match, but the code doesn't, so reconcile it. Or the tests and code match but the spec doesn't, so reconcile that. That's the iteration loop.Jake [00:47:41]: That's why you're seeing people talk about software factories, docs, and reconciliation. Some of that is architectural astronomy if you don't implement it, but that loop is where most things will end up.Swyx [00:48:07]: For listeners, we've been talking about this on the pod for three years: the holy trinity of specs and tests. Itamar Friedman from Qodo is the reference if people want to look it up.Self-Modifying Infrastructure and the End of Push-Pull-RebuildSwyx [00:48:18]: One thing I want to mention on the OpenCloud idea is self-modification. I don't know how Railway would support it, but I have my OpenClaw, and I just tell it it has the Railway CLI and can do whatever. In theory, whatever capabilities or new infra it needs, it can call the Railway CLI, provision it, and add it to itself. The agent can modify its own infra.Jake [00:48:45]: It's nuts. I have a loop set up where you put the Railway CLI on top of something that runs on Railway. You're authenticated as whatever the current box is, and you can make any changes to it. Then you call Railway deploy, and it deploys itself.Jake [00:49:04]: It's like: “I need to spin up this instance of this environment. I already exist in this environment. Excellent, I have access to a Postgres instance now.” That's where we want to go with agentic, self-replicating infrastructure. That's your loop: iterate in production. You continue making changes. If it works, merge it upstream. If it doesn't, throw it away.Jake [00:49:37]: How do you make throwaway copies trivial to spin up and super cheap? The era of “I have an AWS instance with four vCPU and 16 gigs of RAM” is going to get destroyed. If you do that for agents, you need a thousand of those machines. It's prohibitively expensive compared with what we've spent a ton of time figuring out: the atomic unit of deploy, whether you call it isolates, sandboxes, or something else. Only pay for what you use, spin up instantaneously, and close the loop as quickly as possible.Jake [00:50:15]: If the system can self-replicate safely and say, “This is my environment, I'm making these changes,” it can come back with, “Does this look good? This is a new state of infrastructure given this prompt. I think I've solved it.” Then you go back and say, “Actually, it looks different.” It does the loop again. Then you say, “Cool. Apply.”Swyx [00:50:38]: That's retroactively obvious, which is the most useful kind. Any other comments on agent deployment on Railway?Jake [00:50:51]: It's getting better every day. I'm on X or Twitter. You can always yell at me about the parts not working as well as they should, because plenty of things should work way better.The New Serverless: Stateful, Long-Running, Pay-for-What-You-Use LinuxSwyx [00:51:04]: At this stage, when people want massively or embarrassingly parallel compute, they usually talk serverless. I feel like there's a new serverless compared to the previous five years of serverless. You're in that new bucket. Do you have comparisons or philosophical differences you want to call out?Jake [00:51:31]: It's somewhere in between. It's the ability to run stateful, long-running workflows or executions.Swyx [00:51:42]: Vercel has Fluid Compute, Cloudflare has some container thing, Google has App Runner and others.Jake [00:51:55]: That's where everything is roughly going, and it's why we've been working on this for six years. We believe users need access to a computer: a box that speaks Linux. They need to deploy what they want. Other systems change the surface area of what you can build. For us, users need a computer and need to deploy anything they truly want. That's why we've focused on the primitives: network, compute, storage. If we give you those and expose them so you can run things indefinitely, that's where we believe it's going.Jake [00:52:43]: Twitter has no nuance, so everyone says “servers” or “serverless.” It's always somewhere in the middle: I want to run it for a long time, but I don't want to provision the resource statically or pay for things I'm not using. That's been our thesis from day one: pay only for what you use, run it indefinitely, and it is full Linux.Swyx [00:53:12]: That's why I like the naming of Fluid. It's fluid. Flexible.Heroku, Focus, and Carrying the Torch Without Becoming the PastSwyx [00:53:18]: Another milestone is the Heroku official deprecation. You're one of the presumptive new Herokus. “New Heroku” has been a category for as long as I've been in developer tooling. It's finally happening. What was that like? Any behind-the-scenes of, “This is the moment”?Jake [00:53:42]: You have people where you're like, “You were running stuff on here? You, as this company?” It's crazy that names you would know are running on it and now coming to us saying, “We want to move a lot of this off.”Swyx [00:54:00]: Any behind-the-scenes on why Salesforce let Heroku stagnate?Jake [00:54:05]: I can only guess. It's hard when it's not your business. Salesforce's business is to build a great CRM. That's their focus. Then you acquire a compute business as an offshoot. A lot of early Meta people talk about focus. Boz has a write-up about how in the early days of Meta they had no money, so they were forced to focus. Then they turned on the money tree and had no reason not to split their focus.Jake [00:54:52]: But that dilutes your product. You get offshoots where you ask, “Is this the focus of the business?” If it's not core, it languishes. A lot of companies get in trouble when they split focus because they're fighting a multi-front war, not just externally but internally for alignment. Where are we going? What are we doing? What is our purpose?Jake [00:55:24]: If you're Salesforce-built and mission-driven, you want to work on Salesforce. Heroku is off to the side. It's not core to the business. Getting resources, budget, focus, and alignment internally becomes hard. It was a matter of time.Swyx [00:56:06]: Kudos for them to call it out instead of leaving it unknown.Jake [00:56:12]: Their release was a little odd. They called it out, but they didn't say they were shutting it down. Behind the scenes, I think they issued messages to people saying they should close accounts and that they were going to deprecate and remove things over time.Jake [00:56:30]: It's crazy because some of my first deployment experiences were on Heroku. You start with dragging things into an FTP server, then you try to get a deploy working, and then it's Heroku. It was the on-ramp for us. But the wheel turns. New things emerge. We're happy to carry the torch for a lot of that. But we don't want to be the new Heroku. We want to be the way people build and deploy software, and ultimately the way people monetize software over time.Swyx [00:57:19]: It's still a big crown to be the new Heroku. There are 50 companies that fought for that.Jake [00:57:23]: Everybody is holding some portion of it. We're happy to support people and companies. The platform works differently. The game loop is similar, but we've been dogmatic about where these things are going: primitives, agents, fan-out. Some things fit; some workflows need to change. We have an approximation of Heroku pipelines with the environment system. It's exciting. We've got a ton of people we can support, and it's growing a lot.Temporal, Workflow Engines, and State MachinesSwyx [00:58:12]: I have one more technical question about Temporal. I've sold my shares. You're a power user and one of our earliest customers. I met you through Temporal. You built on Temporal. You have complaints. This may be the most neutral and informed conversation anyone will hear about Temporal without someone working at the company.Jake [00:58:39]: That's fair. I've used Temporal for almost 10 years because of Cadence at Uber.Swyx [00:58:52]: Give people a sense of what Cadence was at Uber.Jake [00:58:57]: Cadence was the precursor to Temporal. It powers trip actions, rides, when you rent a Jump bike or scooter or car. You're running workflows for a period of time and saying, “This ride will run indefinitely until it finishes.” You attach information: you paused in this zone, so add this charge to the bill. When you end the trip, the workflow is done. That experience was powered by Cadence at the time.Swyx [00:59:34]: I used to say it's like programming the entire user journey top-down as one function.Jake [00:59:39]: It's a powerful idea and important. It's also important for the next phase of the agentic journey. You want an agent to do a specific task, be complete or incomplete on that task, and move on to the next thing. You need a way to manage workflows dynamically.Jake [00:59:59]: Temporal was always great in theory, and great when you got it working the way you wanted in production. But it required you to model the entire journey in your head. If you didn't, you could cause issues where replaying the state of the workflow causes non-determinism.Swyx [01:00:25]: Because it works on deterministic workflow history.Jake [01:00:28]: Exactly. I describe it as a jet engine. If you know how to operate it and run it, it's great. But you can't hand it to people trying to build complicated things if they don't have the whole state in their head.Jake [01:00:48]: We run our whole deployment pipeline on top of it. That's a reasonably complicated workflow: pre-commit hooks, signaling, queuing, and all the rest. We ran into the same thing at Uber. As you express a large workflow, it gets more complicated, with more states in the state machine that you have to map back to the workflow.Swyx [01:01:15]: It's a lot of ifs.Jake [01:01:16]: Exactly. At Uber, we built a system for doing the state machine and testing it. We've started to build some of those things here because it's grown heavily. It's not quite love-hate. When it works well, it works super well. But if someone who doesn't have full context puts something into the system that invalidates state or causes non-determinism, or spins off a ton of activities, you have to keep track of underlying SRE knobs like activity slots. Those should scale with memory, vCPU, and so on. It becomes a bear to scale.Swyx [01:02:10]: You need a capable sysadmin running things behind the scenes. If you moved off, what would you do?Jake [01:02:19]: We'd build our own workflow engine. We have a few internally that we've worked on.Swyx [01:02:27]: This is one of those classes of things you typically wouldn't vibe code, but I'm wondering if you can.Jake [01:02:33]: I still don't think you should vibe code it. You still want to run decent tests to make sure it works.Swyx [01:02:39]: Timo didn't invent that from scratch either. There are libraries you can run. On top of that, it's just a state machine that you have to map out. Ultimately, you define the instructions you want and run them through a state machine.Jake [01:03:00]: It's very doable. Workflow stuff is interesting. Restate is doing neat stuff here.Swyx [01:03:10]: You're tied into JavaScript. Are you a JavaScript maxi?Jake [01:03:13]: Internally, we have TypeScript, Rust, and Go. We don't add more languages. Actually, we have a little C because we write BPF code and hooks. But those are the languages.Swyx [01:03:28]: Is this for sidecars?Jake [01:03:32]: No. It's for the networking stack, volumes, and things like that. We use TypeScript a lot because it powers the dashboard, but we're moving a lot of workflow stuff off the dashboard stack and into the infrastructure stack.Railpack, Nixpacks, and Content-Addressable FilesystemsSwyx [01:04:00]: Cool. Any other technical infrastructure stuff? Railpacks?Jake [01:04:07]: We built an engine for determining dependencies based on source code. It's called Railpack. We built the first version, Nixpacks, on top of Nix, and then we moved.Swyx [01:04:17]: People have been trying to get me to adopt Nix and NixOS for four years. Is it ever going to be a thing?Jake [01:04:23]: I don't know. We're excited about it, but it has pain points. Think of it as a stack of versioned binaries at specific slices in time. If you want version X and version Y, you bloat the package space, which blows up image size and makes real-world workloads difficult.Swyx [01:04:53]: But you content-address it and cache it. In theory, there are optimizations.Jake [01:05:00]: In theory, yes. But with a large enough user base and disparate enough machines, you run into a problem Meta described in the XFAAS paper, their internal serverless system. It becomes difficult at scale unless you break out specific runtimes.Jake [01:05:24]: We didn't want to do that because we wanted to truly allow you to deploy anything. That was our initial thing with Nix. But we've moved toward interesting work around content-addressable file systems that can lazy-load anything from any point and page it into memory.Swyx [01:05:48]: Amazing.Jake [01:05:49]: The future is very bright. It's crazy, and it's going to be nuts.Coding Agent Spend, Roadmaps, and Token ROISwyx [01:05:54]: Founder journey stuff?Alessio [01:05:56]: Your cloud usage: you tweeted you're going to spend $300K this month?Jake [01:06:01]: I think we got to $200K.Alessio [01:06:02]: Coding agents?Jake [01:06:03]: Yeah.Swyx [01:06:04]: Across the company?Alessio [01:06:05]: You only have 35 people, so I'm sure they're not all spending $10K a month. What's the distribution?Jake [01:06:10]: I think I'm at about $25K. We have power users all the way down. We came back from winter break, and I basically said, “If you're writing code by hand, you're doing this wrong.” The tools are good enough now that you can move extremely quickly. There are issues and pain points, but you should be reviewing the code you are writing instead of writing it by hand.Jake [01:06:40]: Architectural patterns matter more now than ever, but you shouldn't spend your time generating code you would write. If you know how to write it, ask the agent to write it and reconcile it until it looks like you would have written it yourself.Jake [01:06:58]: People misconstrue my propensity to push people toward agents as connected to our growth and some reliability bumps. They're not necessarily related. The tools are good enough to move extremely quickly and build things way larger than you could before.Jake [01:07:19]: To the earlier point about cooling data centers in space: I don't know. But with software, you can ask, “How would I build block storage from scratch? How would I do these things?” I have ideas because I have history and have read papers. Let me work them out and build massive test benches with thousands of tests, because those are now free to author. If you're not using AI systems to speed-run your roadmap and reconcile your existing system onto the future, you're missing a large point of what's happening.Alessio [01:08:12]: What's the path to spending $3 million a month? Is it bound by ideas and things customers can absorb?Jake [01:08:19]: For most companies, it's bound by deployment at this point. That's why we've seen a massive boom in users and companies, from Fortune 50s down, asking how to get developers to move faster. You'll probably hit your CFO before any technical limits because they'll look at the eye-watering amount of money spent on tokens. Inference costs have to come down, but we're inference constrained now. There will be price discovery around what makes sense for an org to adopt.Jake [01:09:06]: I think you'll end up with the F1 driver concept. If someone is really adept at these things, it makes sense to put them in a $3 million car. If they're not, it probably doesn't make sense. You'll take a few people and say, “You can drive the F1 car. We need to go in this direction. Figure out if it works and prototype it.”Jake [01:09:33]: We've done some of that and vastly accelerated our roadmap. We thought we'd ship something in a few years; now we can probably ship it in a few months because we validated it and don't have to build it incrementally. We can skip steps and move toward our vision.Alessio [01:09:58]: A lot of people are realizing the roadmap doesn't always have a business impact, so they say tokens are too expensive. But if your roadmap were built to make more money by the time you built it, you'd have token pricing for it, the same way you do with sales. You'd spend a billion dollars on sales if you knew you would get $2 billion of revenue.Jake [01:10:19]: Exactly. A naive way to measure this is the percentage of tokens that end up in production. If you can measure impact because those tokens end up in production, that's awesome. But the burden of proof will rise. Internally, we have a growing number of pull requests that haven't merged. The question becomes: how do you get this into production? It's about how quickly you can build and deploy software, which is exciting because that's our whole thing.The SDLC Shift: Prompt Requests, Feature Flags, and Safe RolloutsSwyx [01:10:56]: The SDLC is changing. One thesis is that the pull request is dying. It's going to be the prompt request. Beyond that, code review is also kind of dying if you have all the other systems in place. What else is changing about the SDLC?Jake [01:11:19]: The AISRE and the tools to make it happen. AISRE is pie-in-the-sky aspirational. What does it take to get an AISRE? What tools do you need to build?Swyx [01:11:32]: You should expose your tooling to customers at some point. The Central Station command center.Jake [01:11:39]: We have it for template maintainers. Template maintainers can deploy and maintain templates, and they get feedback. We're going to expose those things incrementally.Swyx [01:11:51]: Clustering around incidents. Everyone has a version of that, but I don't think anyone has solved it.Jake [01:11:56]: I won't say we've solved it internally, but it's gotten so good that we can see incidents forming pretty quickly. At some point, those will be things either someone else builds or we build. We've always built things purpose-built for us. If it makes sense to make it useful for users, monetize it, or turn that loop into a profit center instead of a cost center, we want to do that.Jake [01:12:28]: Pull request is definitely dying.Swyx [01:12:29]: Do you do first-party feature flagging and incremental rollout stuff?Jake [01:12:34]: We have a feature-flagging engine we built internally and will eventually roll out.Swyx [01:12:38]: I don't see it as a user. How come you didn't give us what you have?Jake [01:12:43]: We have to beta test it. We care a lot about the quality of the things. There's plenty we've used internally that doesn't make it all the way through the journey because it fails. It works for one service but not multiple services. We'd have to build it for multiple services and know that if we released it, we'd rebuild it again and again. Some things are worth that, but many inform the roadmap.Jake [01:13:18]: We don't want to dilute the experience by saying, “This works, but only for this service,” unless it's a core initiative. Over the next few months, we'll roll out things that work for a single service, then multiple services, then multiple services across the environment. You have to be deliberate. Otherwise you create broken disparate experiences and support load because people ask how to use the feature.Jake [01:13:52]: It's the earlier expansion and compaction pattern. You expand the company to get features, then compact and smooth them out so the experience is stellar. You told me in the hallway, “It's gotten so much better.” Internally we're saying, “This part really sucks. We need to make it significantly better.”Swyx [01:14:11]: I can attest to that over the last three years watching you build Railway. For listeners, feature flagging is a huge part of Uber culture. So much so that they have too many feature flags and another thing to remove feature flags. Facebook has Gatekeeper. Agents are going to need this. It's fundamental to incremental rollouts. OpenAI acquired Statsig. GPT-5 is routing and flagging through different models.Jake [01:14:56]: It's super important. If the software development lifecycle is going to change because we're doing things 1,000 times faster and 1,000 times more concurrently, what becomes important at scale?Jake [01:15:16]: Before I started Railway, I built a feature-flagging product and tried to sell it. It was an easier version of LaunchDarkly. I ran into a problem: anyone small enough to adopt your technology doesn't care about feature flags, and anyone large enough to need feature flags needs so much scale that you have to build out all the infrastructure. I scrapped it.Jake [01:15:42]: But what is old is new again. Companies are trying to move quickly, but you can't YOLO a vibe-coded thing straight into production. You need to say, “Here's my blast radius, my impact, and I want to shadow it for these users.” Feature flags. You're going to need the tools larger companies built to maintain their structures. Everything gets compressed by 1,000x so everybody can build those structures quickly.Jake [01:16:07]: That's exactly where we are: compressing the software development lifecycle, then expanding it and adding more new things.Cattle, Pets, and Clonable InfrastructureSwyx [01:16:15]: Another term that comes to mind for newer developers is “cattle, not pets.” People treat production like a pet. It has a name. You baby it and keep it alive. With cattle, you can mass farm, roll out, portion parts out, and kill them.Jake [01:16:37]: I think that might change. You can move toward having pets as long as you have a cloning machine for your pets.Swyx [01:16:52]: Yeah.Jake [01:16:52]: If you can snapshot every single thing at every frame, it doesn't matter if something gets obliterated because you have a snapshot of it. The things we've built right now are designed to block changes from the hermetically sealed DevOps line. You have to write a Dockerfile because you nee

Send us Fan MailAmazon shoppers decide fast, and one weak product image can cost sellers the click before their listing gets a chance. In this video, we break down Amazon main image optimization, why shoppers look at product photos before reading the title, and how small image changes can improve click-through rate in Amazon search results and Sponsored Ads. You'll see real Amazon listing examples, CTR checks, bullet point mistakes to avoid, A+ Content SEO tips, and product photo best practices so sellers can spot what may be hurting their Amazon listing and fix the images, copy, and content that matter most.#AmazonSeller #AmazonFBA #AmazonListing #AmazonSEO #AmazonCTRGet help from My Amazon Guy to grow your Amazon sales: https://bit.ly/4jMZtxuWant free resources? Dowload our Free Amazon guides here:Amazon Receiving Delay Guide: https://hubs.ly/Q04cdD4c0Amazon Catalog Spring Cleaning: https://hubs.ly/Q046BVfp0Amazon Proft Margin Defense 2026: https://hubs.ly/Q042trRH0Amazon SEO Toolkit 2026: https://bit.ly/4oC2ClTAmazon Seller Strategy Report 2026: https://bit.ly/3YN1RME2026 Ecommerce Website & SEO Readiness Checklist: https://hubs.ly/Q04btghf0Amazon 2026 PPC guide: https://bit.ly/4lF0OYXTimestamps00:00 - Why Main Images Get the First Click00:31 - Main Image Hack for Better Product Photos01:18 - Using Empty Space in Product Images01:43 - Adding Top Keywords Through Packaging02:24 - Product Examples With Keyword Packaging03:08 - Text Is for Robots, Pictures Are for People03:45 - Click Through Rate Goals for Amazon Listings04:18 - A+ Content and Crawlable Text04:41 - Bullet Point Rules for Amazon Sellers06:08 - Where to Find CTR and Conversion Data07:27 - Specs, Infographics, and Lifestyle Images08:58 - Amazon Main Image Text Rules-----------------------------------------------------------------------------------------Follow us:LinkedIn: https://www.linkedin.com/company/28605816/Instagram: https://www.instagram.com/stevenpopemag/Pinterest: https://www.pinterest.com/myamazonguys/Twitter: https://twitter.com/myamazonguySubscribe to the My Amazon Guy podcast: https://podcast.myamazonguy.comApple Podcast: https://podcasts.apple.com/us/podcast/my-amazon-guy/id1501974229Spotify: https://open.spotify.com/show/4A5ASHGGfr6s4wWNQIqyVwSupport the show

THIS EPISODE IS BROUGHT TO YOU BY: GPRSBefore you cut, core, drill, or excavate, make sure you know what is inside the concrete.GPRS helps contractors locate rebar, conduit, post-tension cables, utilities, and other hidden hazards before they become expensive problems. Their scans help reduce hits, downtime, expenses, and keep your people safe. Learn more here: https://www.concretelogicpodcast.com/gprs ON THIS EPISODE OF THE CONCRETE LOGIC PODCAST Low-carbon cement sounds good on paper. But can it actually compete in the real concrete market without subsidies, mandates, or customers paying a “green premium”? That is the question Seth gets into with Ryan Gilliam, CEO of Fortera. Ryan explains how Fortera's approach differs from many other low-carbon cement companies by bolting onto existing cement plants, using limestone as the feedstock, and turning CO₂ back into a reactive cementitious product. This conversation gets into the hard part of low-carbon cement: economics, field performance, scaling, ready-mix adoption, policy risk, and whether these products can survive when the market stops caring about the carbon story. Ryan makes the case that the future of low-carbon cement will not be built on guilt, regulation, or good intentions. It has to perform. It has to be cost competitive. And it has to work in the field. WHAT YOU'LL LEARN • Why “green cement” usually makes contractors and producers assume there is a compromise • How Fortera's technology bolts onto existing cement plants instead of replacing them • Why limestone loses roughly 44% of its weight as CO₂ during traditional cement production • How Fortera claims to turn that CO₂ back into cementitious material • Whether Fortera's product should be thought of as an SCM, a cement replacement, or a new cement • Why ready-mix producers are skeptical of alternative cements • What field feedback Fortera has received on finishing, flow, pumping, set time, and cracking • Why Ryan does not believe customers will pay large green premiums • How policy changes could impact demand for low-carbon cement • Why carbon capture usually struggles economically • How Fortera's approach differs from traditional carbon capture and storage • What has to be true for low-carbon cement companies to scale • Why first commercial plants are such a hard step for new cement technologies • Why Ryan believes performance, not carbon marketing, will decide which technologies survive CHAPTERS 00:00 Introduction to Ryan Gilliam and Fortera 03:25 Ryan's background in materials engineering and cement research 05:20 Fortera's approach to low-carbon cement 08:28 Is Fortera's product an SCM or a new cement? 09:23 Blended cement use versus 100% product use 10:33 What is driving demand for low-carbon cement? 13:39 Scaling challenges for new cement technologies 15:43 Field feedback on alternative cement performance 18:58 Type IL rollout, skepticism, and contractor pushback 20:07 Policy risk and whether low-carbon demand depends on regulation 22:18 How Fortera captures CO₂ from limestone 23:07 Why the economics may work 24:41 How this differs from traditional carbon capture 25:45 What cement plants need to adopt the technology 28:07 Fortera's history and lessons from earlier attempts 29:00 How Fortera may go to market 30:20 Ryan's main takeaway for the concrete industry 32:09 How to contact Ryan Gilliam GUEST INFO Ryan Gilliam CEO, Fortera Profile: https://www.concretelogicpodcast.com/guests/ryan-gilliam/ CONCRETE LOGIC ACADEMY If you work in concrete and want practical education that actually connects to the jobsite, check out Concrete Logic Academy. This is not theory for the sake of theory. It is concrete education built around the stuff producers, contractors, engineers, and field leaders deal with every day. Specs. Mixes. Placement. Finishing. Troubleshooting. Materials. Durability. Bad assumptions. Costly mistakes. Get access here: https://www.concretelogicpodcast.com/concreteschool SUPPORT THE PODCAST Concrete Logic runs on a value-for-value model. If this episode helped you think through low-carbon cement, alternative cement technology, or what might actually work in the real market, send some value back. Donate here: https://www.concretelogicpodcast.com/support/ You can also support the show through KUIU: https://www.concretelogicpodcast.com/kuiu For sponsorship or media opportunities, contact: seth@concretelogicpodcast.com CREDITS Producers: Jodi Tandett & Concrete Logic Media Music: Mike Dunton https://www.mdunton.com/ WHERE TO FIND SETH Concrete Logic Podcast: https://www.concretelogicpodcast.com YouTube: https://www.youtube.com/@concretelogicpodcast LinkedIn: https://www.linkedin.com/in/seth-tandett/ Like, subscribe, comment, and share the episode with someone in the concrete industry who needs to hear it.(Correction: At the 33:42 mark, Ryan referenced testing that reported a compressive strength of 10,000 psi. After recording, the testing result was later determined to be incorrect. The corrected result was approximately 6,000 psi.)

  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.

- Federal Judges Rule Trump's Tariffs Illegal - Auto Groups Urge Trump to Save USMCA Deal - Toyota North America Loses Money Despite Record Sales - Tesla Model Y Passes New U.S. ADAS Tests - Tesla China Deliveries Surge 36% In April  - Tesla Semi Official Battery Specs Revealed  - Tesla 4680 Cells Underperform Compared to Supplier Batteries - Porsche Cuts Board Seat and Lays Off Hundreds - Taycan Turbo GT Sets New Nurburgring Electric Record - BMW Introduces Pre-Chamber Ignition to M Series Engines

- Federal Judges Rule Trump's Tariffs Illegal - Auto Groups Urge Trump to Save USMCA Deal - Toyota North America Loses Money Despite Record Sales - Tesla Model Y Passes New U.S. ADAS Tests - Tesla China Deliveries Surge 36% In April  - Tesla Semi Official Battery Specs Revealed  - Tesla 4680 Cells Underperform Compared to Supplier Batteries - Porsche Cuts Board Seat and Lays Off Hundreds - Taycan Turbo GT Sets New Nurburgring Electric Record - BMW Introduces Pre-Chamber Ignition to M Series Engines

FOLLOW UP: MORE APPEAL AGAINST FCA RULINGFollowing the deadline passing for appealing against the Financial Conduct Authority's (FCA) plans for compensation following the car finance industry breaking the law, there are now three lenders fighting back. Mercedes-Benz Financial Services join VW Financial Servcices and CA Auto Finance. The companies have declined to clarify to the public why they have made the move. To find out more, click this link from MoneySavingExpert.TOYOTA SUPPLIERS HIT BY IRAN CRISISToyota has announced that their suppliers have already begun to state they are feeling the effect of the Iran crisis with warnings that parts will not be delivered at the time expected. Toyota and their suppliers have already downgraded their expectations on 2026 production numbers. Click this CBT News article link here for more.LAMBORGHINI GETS A NEW CTOFermín Soneira is leaving heading up of AUDI, the Chinese only off-shoot of Audi, to take up the role as Chief Technology Officer for Lamborghini. Fred Schulze will replace Soneira. For more on this story, click the electrive article link here.EV CHARGING GRID VULNERABILITY DEMONSTRATEDAt BlackHat Asia, a large cybersecurity and research conference, the vulnerable nature of EV charging networks and shared e-bikes was demonstrated. Companies are being accused of putting customer convenience ahead of security. One possible scenario is the ability to remotely disable an entire city's EV charging network. You can learn more by clicking this link, from The Register, here.MG TO BUILD CARS IN SPAINMG has chosen Spain as the location for their European car factory, over Hungary. By doing this they should avoid any tariffs or agreed minimum price requirements that are to apply with cars coming to Europe from China. Click this EVPowered article link here, to read more.HONGQI IN TALKS WITH STELLANTIS ABOUT SPANISH FACTORYThe Chinese car maker, Hongqi, is in discussions with Stellantis about using capacity at their Spanish factory to build their cars in Europe, also taking advantage of avoiding extra financial penalties. Both parties are tight lipped on the matter. If you wish to find out more, click this Carscoops article link here.AUDI RECALLING 96,000 CARS WORLDWIDEAudi is recalling 96,180 e-tron quattros and Q8 e-trons, due to a potential brake issue. The fault is a lose screw that may prevent full braking ability in cars built from the 2 February 2018 until 11 June 2024. To read more, click this electrive article link here.If you like what we do, on this show, and think it is worth a £1.00, please consider supporting us via Patreon. Here is the link to that CLICK HERE TO SUPPORT THE PODCASTNEW NEW CAR NEWS -Freelander 8JRL and Chery have revealed their first concept from their joint-venture for the Freelander brand. Unsurprisingly, this is an electric SUV with a hint or two of the original Freelander and some of the JLR back catalogue. Initially this will be launched in China but then to other international markets, including the UK. We don't really know much about the specs or what the final look will be. Click this Autocar article link to learn more.For information on timings of the Freelander hitting markets outside of China, click this EV Powered article link here.BMW 7 SeriesBMW have given the 7 Series a facelift. Specs have improved with a longer range possible. The interior has also had a spruce up. For more on this, click this Autocar link here.Old Car Dead News: GWM Ora 03The car formally known as the GWM Ora Funky Cat is no longer going to be sold in the UK. Never a big seller, whether it was the looks or name that put people off. GWM is reviewing their strategy in the UK and are looking to bring more offerings here. Click this electrive article link here for more.LUNCHTIME READ: COMPETING CARS FROM THE SAME DESIGNERNot big enough to be a List of the Week it is still a fab article to have a read through and check out some designer's work where they competed against their own designs. Click here to read the Hagerty article.LIST OF THE WEEK: 23 SPACE INSPIRED CAR NAMESClassic & Sports Car provide the slideshow this week, all around the theme of space related car names. Click this link here to see if you agree with the choices made on the show. Thank you to listener, Damien Scully for sending the link our way, very much appreciated.AND FINALLY: HOW TO DRIVE IN JAPAN FROM THE MIDLANDSThe racing game Forza Horizon 6 is about to launch on the Xbox and PC, with Playstation following later in the year. This iteration is set on the roads of Japan and include a lot of JDM cars. In a collaboration with the British Motor Museum there will be a Horizon Festival on 23 May 2026 on site, where there will be live music, food trucks, gaming vans (to try out the game) and drifting demonstrations. Click this Motoring Research article to find out more, including how to book your tickets.

In episode 236, we explore why so many hardware products never make it to market, even when the idea is strong, the team is ready, and the budget is there. In this episode of China Manufacturing Decoded, your host Adrian is joined by Paul Adams from Agilian, part of the Sofeast Group, to break down the real reasons hardware projects stall before they even start, and what you can do to avoid it. They go beyond theory and share practical lessons from real projects, including costly mistakes around missing specifications, bad assumptions, and external pressure to move too fast. You'll learn: Why missing product requirements quietly kill projects The difference between having an idea and being ready to start How assumptions compound into expensive errors The hidden risks in BOMs, components, and compliance Real-world case studies where projects stalled, and why A practical 10-point checklist to validate your readiness before development The goal of this episode is to help you avoid delays, wasted budget, and failed launches when you're launching your product.

Learn how 14-foot gooseneck dump trailers balance maneuverability and high payload capacity, what drives costs from $8,000 to $16,000, and how to choose between various GVWR options, telescopic versus scissor hoists, and top brands like Load Trail and Maxx-D.Info: https://www.poplarblufftrailer.com/blog/14-foot-gooseneck-dump-trailer-for-sale-price-specs--brands--107184 Poplar Bluff Trailer City: Poplar Bluff Address: 135 Hwy T Suite B Website: https://www.poplarblufftrailer.com/

Evan Spiegel, the co-founder and CEO of Snap, is one of the very few people in the world who has successfully built and scaled a lasting consumer social product. Snapchat has nearly 1 billion MAUs, and Evan and his team invented some of the most important consumer products and features, including Stories, AR glasses, swipe-based navigation, the camera as the primary UX, and a lot more.In our in-depth conversation, we discuss:1. Why distribution is now the biggest challenge for creating a consumer technology business2. How Snap innovates at scale with a 9-to-12-person design team: no titles, no hierarchy, hundreds of ideas reviewed weekly with the CEO3. Why a pure software business is no longer a moat, and what actually creates durable competitive advantages today4. How AI is changing the way designers work and why they're now shipping code5. Why every major Snap feature was copied and how that forced the company to work differently6. Evan's prediction that humanity's comfort with AI will be a bigger bottleneck than the technology itself7. This year's crucible moment for Snap—Brought to you by:WorkOS—Modern identity platform for B2B SaaS, free up to 1 million MAUs: https://workos.com/lennyVanta—Automate compliance, manage risk, and accelerate trust with AI: https://vanta.com/lenny—Episode transcript: https://www.lennysnewsletter.com/p/snapchat-ceo-why-distribution-is—Archive of all Lenny's Podcast transcripts: https://www.dropbox.com/scl/fo/yxi4s2w998p1gvtpu4193/AMdNPR8AOw0lMklwtnC0TrQ?rlkey=j06x0nipoti519e0xgm23zsn9&st=ahz0fj11&dl=0—Where to find Evan Spiegel:• X: https://x.com/evanspiegel• Snapchat: https://www.snapchat.com/@evan• LinkedIn: https://www.linkedin.com/in/evan-spiegel• Website: https://www.spiegelfamilyfund.com—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Introduction to Evan Spiegel(02:28) Why consumer social products are so hard to build(04:31) How Snapchat cracked distribution with close friends, not network size(05:50) Why distribution is the new moat in the AI era(08:39) Snapchat's innovation track record (and why software isn't a moat)(11:39) Why Snap is betting on two of the hardest businesses: consumer social and hardware(16:00) Specs use cases(17:56) The innovation process(21:34) The velocity of design work at Snapchat(25:07) Why Evan says you must talk to customers(26:06) The origin story of Stories(28:25) How screenshot detection saved early Snapchat(31:03) Why they waited to hire PMs—and what role they play now(34:41) How AI is shifting the designer-PM-engineer triad(36:10) Design as an intentional bottleneck for product cohesion(37:24) Why staying close to customers matters for any leader(39:39) What Evan looks for when hiring designers(41:57) How to develop young design talent(44:16) Designers shipping code with AI—and the guardrails needed at scale(47:20) Using jobs-to-be-done to organize AI transformation(48:50) How the CEO job has changed over 15 years(51:30) Learning to communicate(54:08) Why this year is Snapchat's “crucible moment”(56:22) Being the “middle child” in tech(57:51) Screen-time philosophy with four kids (ages 2 to 15)(1:01:08) AI Corner(1:04:02) Contrarian Corner(1:06:04) Lightning round and final thoughts—References: https://www.lennysnewsletter.com/p/snapchat-ceo-why-distribution-is—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. To hear more, visit www.lennysnewsletter.com

Julia Alexander joins Peter to discuss YouTube's exclusive Coachella deal and what it signals about the future of live entertainment. They also dig into the smart glasses arms race at Meta and Snap, and why putting cameras on fans at concerts and stadiums raises some genuinely thorny copyright questions. Plus, Julia dishes on the Hasan Piker phenomenon—and what his audience loyalty on Twitch reveals about everything linear TV is getting wrong. To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

Have you ever asked an AI to build something, only to realize it built the exact wrong thing? AI is incredible at generating code, but it lacks human judgment.In this episode, I share the story of building an internal AI coaching bot called "Jugnu." My first attempt failed completely because I relied on the AI's judgment instead of doing the research myself. I quickly learned that the most successful AI developers spend 90% of their time researching, planning, and writing specs before they ever type a prompt.Join me as we explore how the role of the software engineer is merging with the product manager, the death of "un-used software," and the exact frameworks and tools (like NotebookLM and Superpowers) you can use to master AI-assisted development.

Welcome To The Preferred Lines Podcast Masters Recap and Betting Preview for the 2026 RBC Heritage Joe & John go into great detail on how Rory, again, conquered Augusta National. Joe nailed a winner in the first Major of the season at 14/1 on Rory. They talk his strategy, Scheffler's run, and what to expect moving forward from contenders like Cameron Young and Justin Rose. Finally, our exclusive, in-depth course preview, stat analysis, and historical trends data is discussed in great details. We parlay that information into our player profiles and PICKS TO WIN THE RBC Heritage! Enjoy the Show! Skip to the 45 minute mark for RBC Heritage Content!

- Tesla Receives First FSD Approval in Europe - Nio CEO Says Adopting Common Specs Will Save Billions - Foreign Brands Gain Ground as China EV Subsidies Fade - VW Group Sales Slump Amid U.S. Tariff Challenges - Volvo U.S. Sales Plunge as Inventory Levels Rise - Chery Pursues European Production Through Partnerships - BYD Tests New Affordable Plug-In Hybrid Pickup Truck - Ford Uses AI for Real-Time Robot Weld Repairs - Cars.com Shares Jump Following Workforce Cost Cutting

- Tesla Receives First FSD Approval in Europe - Nio CEO Says Adopting Common Specs Will Save Billions - Foreign Brands Gain Ground as China EV Subsidies Fade - VW Group Sales Slump Amid U.S. Tariff Challenges - Volvo U.S. Sales Plunge as Inventory Levels Rise - Chery Pursues European Production Through Partnerships - BYD Tests New Affordable Plug-In Hybrid Pickup Truck - Ford Uses AI for Real-Time Robot Weld Repairs - Cars.com Shares Jump Following Workforce Cost Cutting

- Intel Tesla Terafab - Intel Google CPU IPU - Fujitsu U. Osaka early-FTQC - Caltech data sample streaming for quantum computing in AI - UALink 1.0 Specs vs NVLink [audio mp3="https://orionx.net/wp-content/uploads/2026/04/HPCNB_20260413.mp3"][/audio] The post HPC News Bytes – 20260413 appeared first on OrionX.net.

On this week's show we go beyond the hype to tell you what specs matter most, what specs are mere marketing hype, and we give you some tips for buying your next HDTV. We also read your emails and take a look at the week's news. News: The price of Netflix is set to go up for all users New VIZIO smart TVs to require a Walmart account The latest Matter update improves camera streaming Other: Why Did TV Manufacturers Stop Using 8K Panels? What Specs Matter and What Don't When Buying a New HDTV Last week the Brightside Home Theater Podcast did a panel discussion on the real factors that shape picture quality. Check it out when you have a chance, it's very informative (Beyond Resolution: The Real Factors That Shape Imaging). So this week we are piggybacking on their discussion to tell you what specs matter most, what specs are mere marketing hype, and we give you some tips for buying your next HDTV.  Specs That Matter Most Panel Technology (OLED vs. Mini-LED/QLED): Not really a spec as much as a technology but it is important for making the right decision for your room. This is the single biggest factor to consider. Choosing the right panel really matters. It directly affects how sharp, colorful, and lifelike the picture looks in your room — whether you're watching movies in the dark or enjoying sports during the day. Which technology you choose depends on what and where you watch TV. OLED (including QD-OLED): Perfect blacks, high contrast, excellent viewing angles, and natural motion. Great for dark rooms and movies. Newer 2026 OLEDs are much brighter than older ones so if you are watching sports don't count this out. Just make sure you buy one of the brighter panels like the LG G5/G6 series, Panasonic Z95B, and the BRAVIA 8 II. Mini-LED/QLED: Much brighter overall (can exceed 2,000–3,000+ nits), better for bright rooms with lots of ambient light. Good contrast with enough dimming zones, but blacks aren't as deep as OLED. Choose based on your room: OLED for controlled lighting, Mini-LED for bright rooms.  Brightness (Peak HDR nits): Real measured peak brightness in HDR content (especially small bright areas like highlights). Higher is better for HDR pop and visibility in bright rooms (1,000+ nits is solid; 2,000+ is excellent). Full-screen brightness also matters but is less advertised. Ignore vague "ultra bright" claims—look for review-tested numbers. Contrast & Local Dimming (for LCD/Mini-LED TVs): Native contrast ratio (higher is better). Number and quality of local dimming zones (more zones = better control, less blooming). OLED skips this entirely with per-pixel lighting. Poor dimming creates distracting halos. HDR Support: Dolby Vision, HDR10+, HDR10, and HLG. Dolby Vision and HDR10+ are dynamic (scene-by-scene adjustments) and preferred over basic HDR10. Most good TVs support multiple formats now. Refresh Rate (Native Panel Rate): 120Hz native is the sweet spot for most people—smooths sports, reduces blur in action, and supports 4K@120Hz from PS5/Xbox/PC. 144Hz or 165Hz is a bonus for high-end gaming. 60Hz is fine for casual viewing but noticeable in fast content. Gaming Features (if you game): HDMI 2.1 ports (at least 2–4 for full bandwidth), VRR (Variable Refresh Rate: freesync/g-sync compatible to eliminate tearing), ALLM (Auto Low Latency Mode), low input lag (

In this episode of Engineering Enablement, Jesse Adametz joins Abi Noda, this time to host. Together, they explore how AI is showing up across the SDLC, not just in code generation, and how it is shifting bottlenecks across the development process. They unpack what “AI readiness” actually means in practice, and why it often comes down to developer experience fundamentals like documentation, environments, and feedback loops.They also discuss why enablement matters more than tool choice, how teams are thinking about measuring ROI, and what changes as background agents become more common. Finally, they explore how the role of the engineer may evolve, the open questions teams are still grappling with, and the challenges of non-engineers contributing to codebases.Where to find Jesse Adametz: • LinkedIn: https://www.linkedin.com/in/jesseadametz • X: https://x.com/jesseadametz • Website: https://www.jesseadametz.com/Where to find Abi Noda:• LinkedIn: https://www.linkedin.com/in/abinoda In this episode, we cover:(00:00) Intro(02:12) Where AI is showing up across the SDLC(05:53) AI readiness and its link to developer experience(08:23) Why enablement, education, and experimentation matter more than tool choice(13:05) The case for a dedicated enablement team(14:50) Measuring AI ROI: challenges and tradeoffs(19:46) Background agents and token spend(24:12) Measuring agent output with PR throughput(26:58) How the engineer role might change(31:01) Specs and documentation in the age of AI(33:11) Non-engineers writing code(35:30) What's changing in the SDLC and open questionsReferenced:• Measuring AI code assistants and agents• Lessons from Twilio's multi-year platform consolidation• The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win• How Claude remembers your project - Claude Code Docs• specIsJustCode : r/ProgrammerHumor

In the world of business technology, it is easy to get blinded by glossy brochures and a laundry list of technical specifications. But frequency ranges and battery life mean absolutely nothing if they don't solve a headache for the person on the other side of the desk. In this episode, Chris Black challenges leaders and sales teams to move past the "what" and get straight to the "why" of professional communications.On this episode:The Paperweight Trap: Chris explains why the most advanced radio on the planet is just an expensive paperweight if it doesn't translate into tangible value for a transportation director or a site foreman.The True Currency of Connection: Real value isn't found in a manual; it's found in the quiet moments of a workday—like a fleet manager getting their team home for dinner thirty minutes earlier or a bus driver instantly alerting a dispatcher during a medical emergency.Buying Back Peace of Mind: Learn how to reframe your pitch. We aren't just integrating the Horizon platform; we are eliminating dead zones, ensuring DOT compliance, and buying back the time lost to logistical guesswork.Investment vs. Expense: Chris discusses how to shift the conversation from a "line item on a budget" to a "foundation for growth." When you solve a client's specific pain points—like cellular overages or distracted driving risks—you prove that you value their success as much as your own.Links & Resources:The Home Base: thefamboss.comConnect Your Fleet: dccipro.comListener Line: Call 855-4-PODCAST (855-476-3227) to share how you've shifted your perspective from products to solutions.Stop pushing products and start providing a foundation for others to build their dreams on. If this episode helped you find your "why," make sure to Like, Subscribe, and Share. Go enjoy your family, stay value-driven, and we'll see you on the next one.

We Like Shooting - Ep 655 This episode of We Like Shooting is brought to you by: Gideon Optics (Code: WLSISLIFE) Night Fision (Code: WLSISLIFE) Die Free Co. (Code: WLSISLIFE) Rost Martin (Code: WLSISLIFE) Flatline Fiber Co (Code: WLS15) Second Call Defense Text Dear WLS or Reviews +1 743 500 2171  Public   Show Titles   GunCon.net Tickets on sale now. Use code AGENCY171 GEAR CHAT Tool-Free Modularity on Modern Rifles The article discusses five situations where tool-free modularity enhances modern rifles. It emphasizes quick adjustments without tools for various scenarios. Specific manufacturers, models, prices, or retailers are not detailed. [Springfield Armory] Echelon with Aimpoint COA Springfield Armory's Echelon pistols are 9mm platforms available in 4.5F full-size (4.5-inch barrel), 4.0FC hybrid (full-size frame with compact slide), and 4.0C compact (4-inch barrel) variants, each factory-equipped with Aimpoint COA red dot optic. The optic features a 7075-T6 aluminum housing, 3.5 MOA dot, CR2032 battery with over five-year runtime, multiple brightness settings, and submersion rating to 25 meters. Slide integrates Aimpoint A-CUT interface with front hook and rear wedge mounting for low position and co-witness irons. [Primary Arms] SLx Compact 4-16x44mm FFP Rifle Scope – Illuminated ACSS Deka G2 Reticle (Nick) The SLx® 4-16x44mm FFP Rifle Scope extends the trusted SLx optic line into the mid-power precision space, delivering a versatile magnification range in a surprisingly compact footprint. At just 10.1 inches in length, this scope is purpose-built for agile, low-profile setups—ideal for designated marksman rifles, hunting carbines, or compact bolt guns. Its streamlined form factor doesn't come at the cost of performance, making it an excellent option for shooters who demand long-range capability without adding bulk.0 BULLET POINTS Kinetic Development Group SideLok Optic Mounts Kinetic Development Group reaffirms a disciplined approach to SideLok optic mount development, a quick-detach system for Picatinny rails using a tool-less push-button mechanism that ensures absolute return to zero and rock-solid stability. Made primarily from 6061 aluminum with black anodized finish, the series includes mounts for red dots, scopes (30mm/34mm), and risers, emphasizing precision engineering for reliable field performance. Specs vary by model, such as the 34mm Optic Mount at 9.4 oz or Aimpoint Micro mount at 2.7 oz. PSA Sabre Ultratech OTF The PSA Sabre Ultratech is an out-the-front (OTF) automatic knife manufactured by Palmetto State Armory in collaboration with Microtech, built on Microtech's flagship Ultratech platform. It features a 3.44-inch M390 blade with mixtape finish, lightweight aluminum handle, reversible pocket clip, and integrated glass breaker. Designed and manufactured in the USA, it offers smooth OTF deployment via side switch. Suppressor-Optimized Subsonic Ammunition Suppressor-optimized subsonic ammunition features bullets traveling under ~1,100 fps to avoid sonic cracks, maximizing sound suppression when paired with suppressors on firearms like those with threaded barrels. Key examples include .300 Blackout (subsonic 180-220-grain loads) and .338 ARC (subsonic 307-grain at 1,050 fps), ideal for stealthy or hearing-safe shooting in manually-operated rifles. Suppressors reduce muzzle blast but require subsonic ammo for full effect, with .338 ARC offering superior terminal energy over .300 Blackout out to 500 yards. NRA App The NRA App is a free digital application developed by the National Rifle Association for iOS and Android devices, designed to enhance member engagement through convenient access to resources like news, digital publications, local events, and member benefits. It features a digital NRA ID card for wallet integration, geolocation-based event discovery for training and competitions, and daily content including gun and gear reviews. As a software tool, it supports Second Amendment advocacy and shooting sports information on the go. Kinect Tool-Free M-LOK Mounting System by Kinetic Development Group The Kinect™ Series is a patented tool-free mounting system for M-LOK equipped rifles, utilizing a spring-loaded wedge mechanism for instant accessory installation and removal with a finger press. Internal locking wedges provide a secure, recoil-resistant interface comparable to traditional systems. It enhances modularity for quick rifle configurations without tools. Whiskey Two-Four Backpack 36 Developer's Pattern The Whiskey Two-Four Backpack 36 Developer's Pattern is a $1.00 PDF vector drawing download for a DIY backpack project with an approximate 11″ x 20″ main compartment, where volume depends on chosen depth. It requires user expertise in patterns and sewn products to convert the CAD PDF into a usable format, including decisions on zipper placement, shoulder strap connections, foam laminate strap binding, and load lifter locations. No support is provided with the purchase. GUN FIGHTS No one stepped into the arena this week. THE ALLEY Silencer Central Suppressors Coming Off ITAR Regulatory Win The X post from Silencer Central links to a blog announcing suppressors being removed from ITAR regulations, reducing export restrictions and red tape for manufacturers. This allows focus on innovation and international sales while benefiting traveling hunters and shooters. No specific product model is detailed in the page content. GOING BALLISTIC The Trace Adds New Board Members: Elizabeth Weinreb Fishman, Trymaine Lee, and Julia Turner (Savage) The Trace, an anti-gun media organization linked to Michael Bloomberg's Everytown for Gun Safety, announced three new board members on March 22, 2026: Elizabeth Weinreb Fishman (media strategist with Surgeon General ties), Trymaine Lee (journalist with shared awards), and Julia Turner (former Slate editor and L.A. Material co-founder). The article scrutinizes their backgrounds for credential exaggerations amid The Trace's efforts to expand anti-gun advocacy. No specific legal cases, bills, or jurisdictions are mentioned.0 Shall Not Be Infringed Act (Introduced by Rep. John McGuire) (Savage) The Shall Not Be Infringed Act, introduced by Rep. John McGuire (R-Virginia) on March 16, targets gun-free zones by allowing individuals harmed in such areas to sue the establishing government entities for damages. It defines gun-free zones as areas prohibiting public carry under federal, state, or local law and ties compliance to federal funding like Byrne-JAG and COPS grants. The bill aims to hold states and localities liable if victims were legally authorized to carry in their home state and could have mitigated harm. ATF Admits It's Still Enforcing Pistol Brace Rules — Even After the Rule Was Killed (Mock v. Garland) (Savage) Despite federal courts vacating the ATF's 2023 pistol brace rule nationwide in cases like Mock v. Garland, a recent DOJ filing in Texas v. ATF asserts continued enforcement of NFA short-barreled rifle provisions against certain braced pistols. The ATF claims this aligns with pre-rule statutory interpretations under the National Firearms Act and Gun Control Act. Gun owners face renewed concerns over potential felony prosecutions despite the rule's defunct status.2818 Michigan's Extreme Risk Protection Order Act: Report on 89% Ex Parte Gun Confiscations (Savage) A report reveals that 89 percent of Michigan's red flag law gun confiscations in 2025 occurred via ex parte orders without prior notice to the subject. Ex parte orders increased by more than 30 percent from 2024, with 459 such requests filed in 2025. The law allows seizure from subjects including minors and even third parties under an expansive definition of firearm possession. H.R. 556: Protecting Access for Hunters and Anglers Act – House Passage (Savage) The U.S. House of Representatives passed H.R. 556, the Protecting Access for Hunters and Anglers Act, on March 23, 2026. The bill prohibits the Secretaries of the Interior and Agriculture from imposing blanket restrictions on lead ammunition or fishing tackle on federal lands without scientific support and consistency with state laws. It now advances to the Senate. REVIEWS Before we let you go – JOIN GUN OWNERS OF AMERICA We'd love if you supported the show, join Agency 171 at agency171.com. Lot's of prizes, rewards and kick ass swag. No matter how tough your battle is today, we want you here fight with us tomorrow. Don't struggle in silence, you can contact the suicide prevention line by dialing 988 from your phone. Remember – Always prefer Dangerous Freedom over peaceful slavery. We'll see you next time! Nick – @busbuiltsystems | Bus Built Systems Jeremy – @ret_actual | Rivers Edge Tactical Aaron – @machinegun_moses Savage – @savage1r Shawn – @dangerousfreedomyt | @camorado.cam | Camorado

1 hour and 40 minutes The Sponsors Thank you to Underground Printing for making this all possible. Rishi and Ryan have been our biggest supporters from the beginning. Check out their wide selection of officially licensed Michigan fan gear at their 3 store locations in Ann Arbor or learn about their custom apparel business at undergroundshirts.com. Our associate sponsors are: Peak Wealth Management, Matt Demorest - Realtor and Lender, Ann Arbor Elder Law, Michigan Law Grad, Human Element, Sharon's Heating & Air Conditioning, The Sklars Brothers, Champions Circle, Winewood Organics, Community Pest Solutions, Venue by 4M where record this, and Introducing this season: Radecki Oral Surgery, and Long Road Distillers. 1. Men's Basketball vs Howard and Saint Louis Starts at 0:51 This is part one of a part two podcast! Which Robbie Avila nickname was your favorite? Of the last ten times Michigan has made the tournament they've been in the Sweet Sixteen nine. Were Beilein teams built better for the tournament than for the Big Ten? Howard shot 48% from three, the only reason they were able to get to 80 points. What Wisconsin nonsense is this? Michigan shoots 84% from two, one of those misses was from Oscar Goodman. Roddy Gayle was uninspiring in the Big Ten Tournament but returned to his March form. Moving on to Saint Louis, they're a dangerous offensive team but there was no way they were going to be able to check Michigan. Somehow Saint Louis was the #1 field goal efficiency defense in the country, it's a good sign that Michigan shot 1.35 PPP. Avila fell for Mara's fake pass. Since they started counting blocks Michigan is the first team to have all starters score 10+ points and have a block. The Mara we're seeing now is night and day from what we saw at the beginning of the season. Could you convince him to come back another year? What was up with that non-flagrant foul that ended up being a foul on Burnett? Technically it was a cylinder foul. High Point isn't a real school, you should only schedule real schools.  [The rest of the writeup and the player after THE JUMP]  2. Spring Football Bits Starts at 34:37 There are finally enough bits coming out of the spring! Ron Bellamy is back as director of player personnel, which makes all the sense in the world. Apparently Whittingham wanted to come back to Utah but he wouldn't have as much control over decision making so he left. What exactly happened here? We thought he was retiring but clearly he didn't. Manuel Beigel moved to offensive line, this is concerning because there are plenty of offensive lineman and this team needs defensive tackles. In more positive news, Savion Hiter is already running with the ones. His built is like Jabrill Peppers. The defense will "resemble the 2023 defense" in terms of style, according to Jay Hill. It will depend what they can get out of Zeke Berry and Rod Moore. Injured guys are still injured. Receiver depth is Marsh, Ffrench, Moa, and Buchanon. Defensive tackle tea leaves are... uhhh... concerning? You need four decent defensive tackles, they currently have three and there's no guarantee that any of them are good. Maybe that's why Hiter is getting so many yards in practice. The NDSU linebacker captain needs to simmer for a bit, he just got here. If one of the best offensive line coaches in the country is excited then we're excited. If Babalola actually starts he'll be an All-American. Sounds like they're kicking Link inside?  3. Hot Takes and Hockey Tournament Starts at 1:02:51 Takes hotter than Howard for the last 10 minutes of the first half. Michigan gets the #1 overall seed in hockey, their reward is a game against Bentley in Albany. They also won the Big Ten Tournament after a 7-3 win over Ohio State. They get medals but not stoats. Playing a team with tournament lives on the line was really good practice. They were so excited to win a banner. Did you know Gonzaga used to have a hockey team. Bentley is 23rd in NPI which is better than their conference usually does. Doesn't look like a team that will threaten Michigan but anything crazy can happen in this tournament. The matchup is there against Penn State but the vibes are annoying since Michigan has already played them five times (and lost once). Will the building have 12 people in it? Minnesota-Duluth had a really good nonconference run but fell off towards the end of the season. They swept Minnesota which doesn't mean much this year. Congratulations Western Michigan, you are a #1 seed and you probably get to play Denver at altitude if you win your first game. The committee doesn't want schools to have home games but then they either give schools "home" games or play in empty rinks. This game should be at Yost and it would be nuts, Michigan deserves the home advantage that they earned. If Wisconsin gets goaltending they're a top four team, if not they'll lose in the first round.  MUSIC: "Hard Dreaming Man"—Drugdealer "Honey Drip"—Long Island Railroad, Smushie and Ryan Gebhard “Across 110th Street”—JJ Johnson and his Orchestra   

In Episode 118, we start with news on the new Rivian R2 SUV, its features, price, and where it lands in the EV landscape.We drive into news from Honda and the billions they are set to lose, the incoming Mercedes-Benz minivan, Ferrari announcements, pricing on the new Dark Horse SC, and more!Rounding off this episode with GR Corolla updates and now Land Cruiser updates!Enjoy!-#rivianr2 #rivian #rivianr1s #electricvehicle #carquickspodcast #automotiveindustry #carnews #automotivenews #Honda #ferrariamalfi #darkhorsesc #mustang #grcorolla #landcruiser -00:00 Introduction00:58 Rivian Release the R2 | FULL Price and Specs!13:22 Honda CANCELS All EVs | Losing up to $15 BILLION25:29 Mercedes goes Minivan | 2026 Mercedes-Benz VLE31:52 Ford Mustang Dark Horse SC Price REVEALED37:53 Ferrari announces the NEW Amalfi Spider39:55 What am I driving this week? | 2026 Toyota Corolla Cross XLE AWD47:42 GR Corolla UPDATES!48:37 NEW SEGMENT! Land Cruiser UPDATES!50:16 Channel updates | Upcoming media events53:43 Outro

In this episode we share the specs on the Ducati Desert X V2 and the 2026 Yamaha Tenere 700 World Raid. Then we discuss weights and powers of the midweight ADV segment and ask if they are getting too heavy.Buying Riding Gear? Use our affiliate link and help out the podcast https://imp.i104546.net/3eZdXdHelp us support the pod or buy us a coffee! https://www.buymeacoffee.com/tdtmotorcyclesSpecial thanks to Derek Brown for our new song and logo! Check out his stuff belowdb SPL links:https://www.dbspl.studio/https://www.instagram.com/db_spl_/Glenarvon:https://www.glenarvonmusic.comhttps://www.instagram.com/glenarvonmusic/------------------Send us your questions and comments totdtmotorcycles@gmail.comFollow Us: Instagram: @gleblapham @meech2dbeech YouTube: @gleblapham

After breaking down 11 animals this year, including two bears and a deer, I've spent serious time with the Benchmade Raghorn in the field. In this no-nonsense review, I'll walk you through what this knife does right — and where it falls short. If you're wondering whether the carbon fiber CPM-CruWear version is worth $420, or if the blade shape holds up under real-world use, this review is for you.

Rivian has spent four years and billions of dollars building electric vehicles that most people cannot afford. The R2 — a mid-size SUV that starts at $45,000 and tops out at $57,990 — is the company's answer to that problem. Full pricing and trim details dropped today, 12 March 2026, and deliveries of the first Performance variant begin this spring. If it works, Rivian becomes a proper carmaker. If it does not, the maths gets ugly fast.From Concept to ConcreteThe R2 platform was first announced in 2022, with production originally pencilled in for 2025 at a planned factory in Georgia. That changed in March 2024, when RJ Scaringe, Rivian's founder and chief executive, unveiled the production-ready R2 alongside the smaller R3 and R3X crossovers at a packed event at the Rivian Theater in Laguna Beach, California. Mr Scaringe also confirmed he was scrapping the Georgia plan — at least for now — and would build the R2 at the existing Normal, Illinois plant instead. That decision saved more than $2.25 billion in capital expenditure and, crucially, pulled the launch date forward.Within 24 hours of its unveiling, Rivian had taken more than 68,000 reservations at $100 apiece. By July 2024, the company's VP of manufacturing Tim Fallon said reservations had surpassed 100,000 and were still climbing. Rivian has not updated that figure publicly since.Production began in January 2026. Validation vehicles rolled off the Normal line first, and the factory is now ramping toward a target capacity of 155,000 R2 units per year — alongside the R1 models it already builds there. Each R2 takes roughly 15 hours to assemble, down from 18 hours for an R1.Why the R2 Matters More Than Any Vehicle Rivian Has BuiltThe R1T pickup and R1S SUV earned Rivian a devoted following and the top spot in Consumer Reports owner satisfaction surveys. They also bled money. Rivian posted a net loss of $3.65 billion in 2025, on top of a $4.75 billion loss in 2024. The R1S starts near $75,000 (around £59,000) — a price that limits the addressable market to a sliver of American buyers."R2 is really instrumental for driving the business to positive cash flow and overall profitability," Mr Scaringe told CNBC in February. He was not exaggerating. The bill of materials for the R2 is roughly half that of the R1. Rivian slashed the number of computing units from over 60 in a traditional vehicle to seven, and cut wiring length by about two miles (3.2 km). The result is what Mr Scaringe called "a dramatic reduction in the cost structure to build it."Rivian did scrape together a positive gross profit in the fourth quarter of 2025 — a milestone, though the margin was wafer-thin at around 2%, compared with Tesla's 17%. The R2, with its leaner architecture and lower price, is meant to close that gap at volume. Analysts expect around 15,000 R2 deliveries in 2026, though some believe Rivian could exceed that figure. By 2027, with three full shifts running, the Normal plant could produce roughly 155,000 R2s annually.Today's Pricing: What You GetThe lineup spans four trims, all sharing an 87.9 kWh usable battery and a $1,495 destination charge. Here is how they break down:The Performance trim arrives first, this spring, at $57,990 (around £46,000) including the Launch Package. It runs dual-motor all-wheel drive with 656 horsepower, 609 lb-ft (826 Nm) of torque and a 0–60 mph (0–97 km/h) time of 3.6 seconds. Highway overtaking is savage: 50–70 mph (80–113 km/h) in 1.55 seconds. EPA-estimated range sits at up to 330 miles (531 km). The Launch Package bundles lifetime Autonomy+ access, a tow package rated at 4,400 lbs (1,996 kg) and an exclusive Launch Green paint option.The Premium trim follows in late 2026 at $53,990 (around £43,000). It shares the 330-mile range and dual-motor AWD layout but dials the power back to 450 hp and 537 lb-ft. Zero to 60 takes 4.6 seconds — hardly slow.The Standard RWD Long Range arrives in the first half of 2027 at $48,490 (around £38,500). A single rear motor delivers 350 hp and 355 lb-ft, reaching 60 in 5.9 seconds. Rivian estimates range at up to 345 miles (555 km) — the longest in the lineup, because rear-wheel drive is more efficient.Finally, the Standard RWD variant lands in late 2027 at approximately $45,000 (around £35,700). It uses a smaller battery pack and offers 275+ miles (443+ km) of estimated range. Rivian has shared few other details so far.All trims charge from 10% to 80% in 29 minutes via a native NACS port, which grants access to the Tesla Supercharger network. CCS adapters are supported too.Built Lighter, Built TougherThe R2 rides on an entirely new mid-size unibody platform — a departure from the R1's body-on-frame architecture. The result is a vehicle that weighs nearly 2,000 lbs (907 kg) less than its bigger sibling while sitting on a 115.6-inch (2,936 mm) wheelbase. At 185.9 inches (4,722 mm) long and 75 inches (1,905 mm) wide, it is squarely in Tesla Model Y territory.The weight savings translate directly into agility, but Rivian has kept the off-road DNA intact. Ground clearance of 9.6 inches (244 mm) is best in class — nearly three inches more than a Model Y. Approach and departure angles of 25° and 26° respectively, plus a wading depth of 19.7 inches (500 mm), mean the R2 can do more than look adventurous in a car park. The Performance trim gets semi-active suspension, eight drive modes including Rally and Soft Sand, and a low centre of gravity courtesy of the structural battery pack.Inside, the cabin seats five adults with 40.4 inches (1,026 mm) of rear legroom and headroom — enough, Rivian says, for occupants over six feet (1.83 m) tall. Total enclosed storage is 90.1 cubic feet (2,551 litres), with a front trunk that swallows a carry-on suitcase and a backpack, fold-flat rear seats that create a level loading surface, and dual gloveboxes. The rear drop glass — a powered window that lowers completely into the liftgate — is a genuine talking point, allowing surfboards and other long cargo to slide in or a breeze to sweep through. It is included on Performance and Premium trims.Materials lean sustainable: upcycled Birch wood accents, a headliner made from recycled ocean plastics and Rivian's second-generation Adventex material, which is designed to withstand muddy boots and wet dogs in equal measure.The Technology PlayRivian calls the R2 a "software-defined vehicle," and the specification sheet backs that up. The perception stack comprises 11 HDR cameras with a combined 65 megapixels and a five-radar system — hardware that comes standard on every trim.Rivian Autonomy+, the company's Level 2+ hands-free driver-assist system, covers 3.5 million miles (5.6 million km) of roads across the United States and Canada. It costs $49.99 per month or $2,500 as a one-off purchase. The Launch Package includes it for the lifetime of the vehicle. Every R2 gets a 60-day trial.On-board AI compute runs to 200 TOPS, dedicated to the in-cabin experience. This powers the forthcoming Rivian Assistant — a voice-controlled system that processes complex requests locally, even when offline. The 5G-connected architecture ensures updates arrive over the air, while the offline capability means the vehicle is not hobbled in areas without signal.At the steering wheel, Rivian's in-house Haptic Halo dials replace conventional switchgear. These context-aware controls scroll, push, pull and tilt with distinct tactile feedback for different functions — an attempt to bridge the gap between touchscreen convenience and physical control that many rivals have abandoned entirely. Two digital displays complete the cockpit: one behind the wheel for driving data, and one in the centre for everything else.The Elephant in the Room: TeslaThe R2 lands in the most contested segment of the electric vehicle market. The Tesla Model Y — the best-selling EV on the planet and briefly the best-selling car of any kind in 2023 — starts at $44,000 in the United States and delivers up to 357 miles (575 km) of range. It has a vast Supercharger network, a mature software ecosystem and years of manufacturing refinement behind it.The R2 fights back with 3 inches (7.6 cm) more ground clearance, genuine off-road hardware, a richer interior (Model Y's cabin has always divided opinion) and that distinctive outdoor-adventure identity that Rivian has cultivated since its founding. Whether that is enough to prise buyers away from Tesla — or from the Hyundai Ioniq 5, the Ford Mustang Mach-E and the Chevrolet Equinox EV — remains the central question.Why Failure Is Not an OptionRivian burned roughly $3 billion in the first nine months of 2025 alone. It ended 2024 with about $5.3 billion in cash, a figure being steadily eroded by capital expenditure and operating losses. The Volkswagen joint venture — worth up to $5.8 billion in total — provides a lifeline, as does the potential for Department of Energy loan access. But lifelines do not last for ever.The company's stock tells its own story. Rivian went public in November 2021 at $78 a share, briefly touched $170 and now trades around $15. A 90% decline from the peak concentrates the mind wonderfully.The R2 must do three things at once: attract a materially larger customer base than the R1 ever could, generate a positive gross margin per vehicle and ramp to volumes that spread fixed costs across enough units to bend the loss curve downward. At a planned capacity of 155,000 units per year from Normal alone — with a second factory in Georgia eventually to follow — Rivian has the industrial ambition. The Volkswagen partnership supplies software licensing revenue and engineering credibility.Mr Scaringe has described the R2 as "the most important thing that we've developed as a company." On the evidence of today's specification sheet, it is also the most complete. The range is competitive, the technology is ambitious, the price is within reach of mainstream buyers and the off-road capability gives it a personality that few electric SUVs can match.None of which will matter if Rivian cannot build it at scale, on time and at a cost that leaves room for profit. The company that once dazzled Wall Street with a $170 share price now needs to dazzle customers with a $45,000 truck. That is the harder trick — and the one on which everything depends.

- Volkswagen Reclaims Top Spot in China as BYD Sales Plummet - VW ID.3 Neo Leads Massive China Product Offensive - BYD Eyes Manufacturing Plants to Enter Canadian Market - Samsung Issues Delay Tesla Autonomous AI6 Chip - Used EV Sales Surge as Lease Returns Increase - Rivian Details R2 SUV Specs Before Official Launch - Lucid Unveils New Mid-Size SUV And Robotaxi Plans

- Volkswagen Reclaims Top Spot in China as BYD Sales Plummet - VW ID.3 Neo Leads Massive China Product Offensive - BYD Eyes Manufacturing Plants to Enter Canadian Market - Samsung Issues Delay Tesla Autonomous AI6 Chip - Used EV Sales Surge as Lease Returns Increase - Rivian Details R2 SUV Specs Before Official Launch - Lucid Unveils New Mid-Size SUV And Robotaxi Plans

Gas Gauge Gadgetry: The Flatulence-Focused Fitness Frontier.  Pixelated Pages: Paper-Thin Playable Tetris Turns Print into Play.  Pickle's Peer-to-Peer Parade: Fashion Freedom Without Fast-Fashion Fallout.  Robot Roulette: Rogue Remotes and the Vacuum Vanguard.  Privacy-Preserving Parenting: Smart Sensors Safeguarding Seniors.  Folded Futures: Weave's Whirr into the World of Home Help.  Spatial Specs & Spectacle: Rokid's Reality-Rewriting AR Revolution.  Bot Boosting Blunders: How a Blog Post Bamboozled the Big AIs.  Yoto on the Go: Mighty Mini, Massive Imagination.