Podcasts about Telemetry

Supply chain technology is evolving rapidly, but cargo criminals are moving even faster. In this episode of Supply Chain Now, Scott W. Luton and Scott DeGroot are joined by Krenar Komoni (Founder & CEO of Tive) and Fernando Boom (Director of Transportation at Venture Metals +) to break down the massive shift from physical yard thefts to sophisticated, identity-based freight fraud. Fernando shares a thrilling firsthand account of how a family road trip turned into a real-time recovery mission for a hijacked $240,000 shipment of copper. While the driver successfully bypassed the physical bolt seals, covert tracking technology thwarted the heist and led to a first-degree felony arrest. Krenar pairs this narrative with over a decade of visibility expertise, unpacking how modern criminals leverage AI, chameleon carriers, fraudulent MC numbers, and double brokering to vanish with high-value freight. Moving past a reactive postmortem claims model, the panel outlines a definitive blueprint for proactive, layered defense. They explore how real-time telemetry, including route deviation alerts and light sensors, empowers logistics teams to stop fraud mid-transit. Scott DeGroot concludes by highlighting the critical enterprise costs of cargo loss, challenging shippers to audit their networks, tighten dock-level verifications, and eliminate the weak links that bad actors exploit. Jump into the conversation: (00:00) Intro (02:38) Meet Venture Metals and Tive leaders (03:53) Art shows and World Cup picks (06:04) Venture Metals recycling and logistics role (07:37) Tive delivers real-time shipment visibility (09:28) Fraud tactics driving cargo theft surge (16:29) Layered alerts detect theft in transit (23:03) Prepare before theft happens, not after (24:03) Light alerts trigger copper theft investigation (26:11) Telemetry exposes route diversion and deception (27:52) Alerts only matter when teams respond (30:19) Police intercept truck at Wichita Falls (31:24) Driver bypasses seal but gets caught (32:47) Trust data and involve law enforcement (36:10) Technology helps monitor risky driver behavior (38:16) Build six layers of cargo security (44:29) Use Tive before theft strikes (47:22) Resources for protecting high-value shipments Additional Links & Resources: Connect with Krenar Komoni: https://www.linkedin.com/in/komoni/ Connect with Fernando Boom: https://www.linkedin.com/in/fernando-boom-a06513372/ Connect with Scott DeGroot: https://www.linkedin.com/in/scott-degroot-4600368/ Learn more about Venture Metals +: https://venturemet.com/ Learn more about Tive: https://www.tive.com/ Learn more about our hosts: https://supplychainnow.com/about Learn more about Supply Chain Now: https://supplychainnow.com Watch and listen to more Supply Chain Now episodes here: https://supplychainnow.com/program/supply-chain-now Subscribe to Supply Chain Now on your favorite platform: https://supplychainnow.com/join Work with us! Download Supply Chain Now's NEW Media Kit: https://supplychainnow.com/media-kit/ WEBINAR- AI that moves at velocity: Cut through latency with agentic workflows: https://bit.ly/4x4626t This episode was hosted by Scott Luton and produced by Trisha Cordes, Joshua Miranda, and Amanda Luton. For additional information, please visit our dedicated show page at: https://supplychainnow.com/240k-shipment-saved-venture-metals-realtime-rescue-1599 The content in this episode, including all audio, videos, visuals, and graphics, is the property of Supply Chain Now and is protected by copyright law. Unauthorized use, reproduction, distribution, modification, or re-uploading of this content in any form is strictly prohibited without explicit written permission from Supply Chain Now.For licensing inquiries or permissions, please contact us at production@supplychainnow.com© 2026 Supply Chain Now. All rights reserved. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

In this episode of the Kubernetes Bytes podcast, Bhavin talks to Anthony Woods about all things Grafana Labs, Observability, Telemetry, and how AI impacts both of these ecosystems. The discussion starts off by talking about the early days of Grafana Labs, what is Adaptive Telemetry, and how AI plays a role both in building Observability capabilities in applications, and how it helps perform root cause analysis. Listen to learn more! Check out our website at https://kubernetesbytes.com/ Show Notes: GrafanaCON 2026: https://youtube.com/playlist?list=PLDGkOdUX1UjoSfz1IRj5c0xetw8tl8iin&si=JpT85m4t4bP8ZXgX Grafana Labs Blog: https://grafana.com/blog/ https://www.linkedin.com/in/anthonywoods1/

The following article of the Automotive industry is: 'Mexico Fleet Logistics: How Telemetry Can Cut Transport Costs' by Ernesto del Blanco, President of the Board, ELAM/FAW. 

Today our Packet Pushers team assembles to discuss whether the grass is greener on the NetOps or DevOps side of the telemetry fence. William of The Cloud Gambit, Scott of Total Network Operations, and Ned and Kyler of Day Two DevOps discuss the difficulties and differences of getting telemetry and state from devices across different... Read more »

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

In this sponsored interview James Wilson chats with Push Security's Chief Research Officer Jacques Louw about how the company has integrated an army of AI agents into its threat detection platform. Not only has agentic AI led to the discovery of Install Fix campaigns, but it will help simplify the platform for new customers. Show notes

Send us Fan MailYour employees are already ahead of you on AI. The data is in and the question is no longer whether this is happening, but what leaders choose to do about it.That is one of the key findings from Microsoft's 2026 Work Trend Index, and it is the starting point for this week's special episode. PeopleReign CEO Dan Turchin sits down with Matt Firestone, General Manager at Microsoft leading product marketing for Microsoft 365 Copilot and Agents, to unpack what trillions of anonymized signals across the Microsoft 365 ecosystem reveal about how AI is actually changing work right now.What pairing telemetry with survey responses and in-house research reveals about the gap between where employees actually are and where their organizations think they are is striking. And the numbers on how organizations reward, or fail to reward, the people already doing this work will make most leaders uncomfortable. The bottleneck, it turns out, isn't where most people expect it.In this conversation, we discuss:Why the job of a leader has shifted from designing transformation strategy to changing systems and cultureHow the report reframes agentic AI collaboration, not as a threat to human agency, but as an expansion of itWhat "frontier firms" and "frontier professionals" actually means, and why it's a mental model and rallying cry, not a marketing termHow building in the open, leaders experimenting visibly and removing the stigma of getting things wrong, is one of the most quantifiably impactful things a manager can doWhy agent adoption on the Microsoft 365 ecosystem is growing at a rate that will surprise even the optimistsExplore this conversation:00:00 Intro01:14 Inside Microsoft's 2026 Work Trend Index02:22 Telemetry, Not Just Surveys: What the Data Reveal03:09 Employees Are Ahead of Their Managers on Agentic AI04:37 The Transformation Paradox and Broken Reward Systems06:15 More Agentic AI, More Human Agency: The 49% Finding09:28 How Leaders Should Respond: Build in the Open11:26 Safety, Trust, and Responsible AI at Microsoft Scale13:36 Building a Manager Equity Dashboard in 25 Minutes with Copilot17:31 What Frontier Firms and Frontier Professionals Actually Do20:04 AI, Toil, and the Fear of Becoming Obsolete22:52 The 1 Billion Agents Prediction and What Comes NextResourcesSubscribe to the AI & The Future of Work NewsletterConnect with Matt on LinkedInMicrosoft's 2026 Work Trend Index

SpaceTime Series 29 Episode 52 *Interstellar comet 3i/ATLAS is far more alien than we thought A new study has found that the interstellar comet 3i Atlas must have originated in a much colder star system with lower levels of radiation than our own solar system. *NASA now looking at September to launch its new Roman Space Telescope NASA are now targeting September as the likely launch date for their new Nancy Grace Roman Space Telescope. *The European Space Agency's new Australian dish The European Space Agency has commissioned its second Australian deep space communications dish at its New Norcia complex near Perth. *The Science Report How climate change is affecting the health of people in Europe. Warnings that agricultural soils exposed to glyphosates could be breeding grounds for superbugs. The Pentagon's plans for big a new battleship for the US Navy -- the first since the 1940s. Skeptics guide to the big UFO announcement allegedly coming this year.   Our Guests This Week: Professor Kliti Grice from Curtin University Jan Cami from Western University   And our regular guests: Alex Zaharov-Reutt from techadvice.life Tim Mendham from Australian Skeptics  

Despite Microsoft's promises, real Windows 11 annoyances like forced telemetry, aggressive Edge defaults, and stubborn online account requirements remain unaddressed. Paul Thurrott calls out what isn't changing and why power users should care. Host: Paul Thurrott Download or subscribe to Hands-On Windows at https://twit.tv/shows/hands-on-windows Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

AI agents are moving fast,  but the infrastructure behind them is still catching up. In this episode of Screaming in the Cloud, Corey Quinn sits down with Paper Compute CEO Brian “B Dougie” Douglas to explore building telemetry for AI agents, open-source infrastructure, token economics, and what it takes to create developer tooling in the AI era. From local-first observability to agent runtimes and the future of AI workflows, this conversation dives into what's next for AI-powered development.Show highlights: (00:00) Open Source Trust Signal(00:16) Show Intro and Sponsor(01:07) What Paper Compute Builds(01:55) Telemetry for Agents Explained(04:10) Local First Data and Sharing(06:18) Second Time Founder Story(09:06) Token Costs and Pricing Psychology(14:20) Stereos VM and Safer Runtimes(20:34) Open Source Strategy and Vibe Coding(24:54) Whats Next and Wrap UpAbout Brian: Brian is the founder of the Paper Compute Company, a distributed systems primitives for AI agents.Brian previously founded Open Sauced, a company dedicated to increasing knowledge and insights of open-source communities. In 2024, Open Sauced joined the Linux Foundation, further solidifying Brian's commitment to advancing open-source initiatives. With a passion for open source, Brian has consistently supported and mentored new contributors through Open Sauced, empowering developers to excel in the open-source ecosystem.Previously, Brian also led Developer Advocacy at GitHub, where he fostered a community of early adopters through content creation showcasing the newest GitHub features. His experience spans across notable companies in the tech industry, including Netlify, where he worked as an advocate. Brian's dedication to open source extends beyond his professional endeavors. He currently hosts two podcasts Open Source Ready and The Secret Sauce: A podcast focusing on developer insights and experiences.Through these platforms, Brian continues to share valuable knowledge and promote open-source culture within the developer community.Links: LinkedIn: https://linkedin.com/in/brianldouglasWebsite: https://b.dougie.devSponsored by: duckbillhq.com

Despite Microsoft's promises, real Windows 11 annoyances like forced telemetry, aggressive Edge defaults, and stubborn online account requirements remain unaddressed. Paul Thurrott calls out what isn't changing and why power users should care. Host: Paul Thurrott Download or subscribe to Hands-On Windows at https://twit.tv/shows/hands-on-windows Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Despite Microsoft's promises, real Windows 11 annoyances like forced telemetry, aggressive Edge defaults, and stubborn online account requirements remain unaddressed. Paul Thurrott calls out what isn't changing and why power users should care. Host: Paul Thurrott Download or subscribe to Hands-On Windows at https://twit.tv/shows/hands-on-windows Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Despite Microsoft's promises, real Windows 11 annoyances like forced telemetry, aggressive Edge defaults, and stubborn online account requirements remain unaddressed. Paul Thurrott calls out what isn't changing and why power users should care. Host: Paul Thurrott Download or subscribe to Hands-On Windows at https://twit.tv/shows/hands-on-windows Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free audio and video feeds, a members-only Discord, and exclusive content. Join today: https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

In Asia-Pacific, CISOs are navigating a pivotal shift as organisations operationalise AI across complex hybrid and sovereign environments in 2026-2027. AI has evolved from an innovative layer into a source of profound operational and security complexity, where failures in autonomous systems now trigger systemic business risks rather than contained outages, amplified by geopolitical tensions, supply-chain interdependencies, and regulatory volatility.Ultimately, building digital resilience at scale demands robust governance, continuous monitoring, and sovereign-compliant architectures that safeguard trust, uptime, and compliance—enabling sustainable AI-driven growth without exposing enterprises to unacceptable risk. In this PodChats for FutureCISO, John Morgam, SVP & GM of Splunk Security, reveals how machine data and agentic AI help CISOs operationalise real-time observability, bridge talent gaps, and embed sovereign-compliant resilience. From Singapore to Sydney, discover strategies for secure, scalable AI growth through 2027.John, welcome to PodChats for FutureCISO.Here are 10 key questions for CISOs in Asia in 2026, sequenced to align with the narrative flow:1.       Why has AI transitioned from a supplementary technology to a core driver of operational and security complexity across Asian enterprises? 2.       How are AI-related failures increasingly manifesting as systemic business risks rather than isolated technical incidents? 3.       What machine data strategies have organisations in Asia implemented to create a definitive, auditable record of system, user, and autonomous agent behaviour across hybrid environments? 4.       Telemetry. How are organisations in Asia embedding real-time observability into security architectures to detect anomalies before AI-driven failures cascade across interconnected systems? a.       SIEMs and SOARs have been with us even before AI. What's different today?5.       Given the regional investment in security talent consolidation, what expertise gaps remain in organisations' ability to govern where AI and operational decisions converge? 6.       How does the convergence of automation, human judgement, and unified data enable agentic AI to transform security operations capabilities? 7.       In what specific ways can agentic AI accelerate detection, deepen investigations, and support controlled, proportionate responses to incidents? 8.       What practical strategies allow organisations to operationalise AI at enterprise scale across hybrid infrastructures while sustaining resilience? 9.       How are regional CISOs adapting to sovereignty requirements across Asia—from Singapore's MAS guidelines to Australia's data locality rules—while maintaining unified security visibility? 10.   How can trust, uptime, and regulatory compliance be maintained as AI adoption accelerates in sovereign, multi-cloud Asia-Pacific contexts?11.   What should CIOs and CISOs bear in mind as Agentic AI makes its way in the SOC?

What does sharpening a knife over a case of onions have to do with incident response? For Myke Lyons, CISO at Cribl, the answer is everything. Myke trained at the Culinary Institute of America — learning speed and accuracy under the clock of a professional kitchen — before a summer IT job in Manhattan set him on an entirely different path. In this episode of The New CISO, host Steve Moore traces that journey and the surprising parallels between culinary craft and security leadership.The conversation moves through a career that evolved organically: a summer job moving refrigerator-sized printers in a Manhattan ad agency, a crash course in executive white-glove IT support, a breakthrough moment finally cracking subnetting, and a slow expansion from NOC operator to global security leader. Myke credits the kitchen — its insistence on precision and calm under fire — for instilling an operator's mindset that still defines how he leads through incidents today.Mentorship, both formal and accidental, threads through Myke's story. A curmudgeonly colleague who threatened to "replace him with a script" taught him the value of continuous improvement. A trusted mentor reframed the CISO's role with a single line about house fires and lock changes. And years in executive IT support gave Myke an early education in empathy and knowing when not to fix what wasn't asked.Myke and Steve examine a vendor incident where a product leader's dismissive response to a forensics question destroyed credibility with hundreds of customers. The lesson: saying "I don't know, but we'll find out" is not a weakness — it is the most powerful tool a leader has. The same insight applies to M&A due diligence, where reframing technical conversations as expectation-setting exercises turns adversarial interviews into collaborative ones.For Myke, the new CISO is defined by empathy and culture. Know your audience. Think like your customers. Communicate policy changes as explanations, not mandates. Find your internal advocates and invest in them before you need them. The recipe for great security leadership is less about technology than it is about people — and that lesson translates perfectly from the kitchen to the boardroom.Key Topics• Career pivots: from culinary school to IT and cybersecurity• Speed, accuracy, and craft — what kitchen discipline teaches security professionals• Building an operator's mindset and staying calm during security incidents• White-glove executive IT support and the patience, precision, and empathy it develops• Mentorship — formal and accidental — and the lessons that only land in retrospect• The dangers of filling silence with false confidence vs. the power of saying "I don't know"• Crisis communication best practices and what not to do during a vendor incident call• Managing M&A security due diligence with low-emotion, expectation-setting conversations• Building security culture through empathy, clear communication, and internal advocates• Telemetry, log management, and Cribl's role as the data engine for IT and security Guest BioMyke Lyons is the Chief Information Security Officer at Cribl, the AI platform for telemetry trusted by organizations worldwide — including half of the Fortune 100 — to manage IT and security data at any scale.He trained at the Culinary Institute of America with aspirations of becoming a food critic — until a summer IT job in Manhattan set him on an entirely different course. Myke went on to build expertise across networking, NOC operations, and log management, holding CISO positions at Snyk and Collibra before joining Cribl in 2024.Connect with Myke on LinkedIn and learn more about Cribl at cribl.io.GET A DEMO:

Apple has debunked media reports claiming low adoption of iOS 26. Chuck Joiner, David Ginsburg, Marty Jencius, Web Bixby, Jim Rea, Eric Bolden, and Jeff Gamet discuss the assertion that the data was skewed by Apple's privacy-driven device misreporting. They review how official numbers show strong uptake among eligible devices and debate whether criticisms of the new interface are overblown. While some UI concerns are acknowledged, the group agrees the release offers meaningful improvements and is far from the failure some headlines suggested.  This edition of MacVoices is brought to you by our Patreon supporters. Get access to the MacVoices Slack and MacVoices After Dark by joining in at Patreon.com/macvoices. Show Notes: Chapters: 0:00 iOS adoption controversy introduced0:28 Claims of low adoption challenged2:04 Telemetry and agent string misreporting3:50 Evaluating Apple's official adoption numbers5:13 Privacy-driven device obfuscation explained6:30 Clickbait and misinterpreted analytics reports7:57 Debate over “liquid glass” interface complaints9:03 Objective UI usability concerns raised12:03 Design philosophy and Apple's UI direction13:18 System Settings and long-term interface frustrations15:49 Improvements and benefits in iOS 2618:35 Broader reflections on Apple UI evolution19:12 Overall assessment: not a disaster, but debated Links: Apple Reveals How Many iPhones Are Running iOS 26https://www.macrumors.com/2026/02/13/apple-shares-ios-26-adoption-stats/ Guests: Web Bixby has been in the insurance business for 40 years and has been an Apple user for longer than that.You can catch up with him on Facebook, Twitter, and LinkedIn, but prefers Bluesky. Eric Bolden is into macOS, plants, sci-fi, food, and is a rural internet supporter. You can connect with him on Twitter, by email at embolden@mac.com, on Mastodon at @eabolden@techhub.social, on his blog, Trending At Work, and as co-host on The Vision ProFiles podcast. Jeff Gamet is a technology blogger, podcaster, author, and public speaker. Previously, he was The Mac Observer's Managing Editor, and the TextExpander Evangelist for Smile. He has presented at Macworld Expo, RSA Conference, several WordCamp events, along with many other conferences. You can find him on several podcasts such as The Mac Show, The Big Show, MacVoices, Mac OS Ken, This Week in iOS, and more. Jeff is easy to find on social media as @jgamet on Twitter and Instagram, jeffgamet on LinkedIn., @jgamet@mastodon.social on Mastodon, and on his YouTube Channel at YouTube.com/jgamet. David Ginsburg is the host of the weekly podcast In Touch With iOS where he discusses all things iOS, iPhone, iPad, Apple TV, Apple Watch, and related technologies. He is an IT professional supporting Mac, iOS and Windows users. Visit his YouTube channel at https://youtube.com/daveg65 and find and follow him on Twitter @daveg65 and on Mastodon at @daveg65@mastodon.cloud. Dr. Marty Jencius has been an Associate Professor of Counseling at Kent State University since 2000. He has over 120 publications in books, chapters, journal articles, and others, along with 200 podcasts related to counseling, counselor education, and faculty life. His technology interest led him to develop the counseling profession ‘firsts,' including listservs, a web-based peer-reviewed journal, The Journal of Technology in Counseling, teaching and conferencing in virtual worlds as the founder of Counselor Education in Second Life, and podcast founder/producer of CounselorAudioSource.net and ThePodTalk.net. Currently, he produces a podcast about counseling and life questions, the Circular Firing Squad, and digital video interviews with legacies capturing the history of the counseling field. This is also co-host of The Vision ProFiles podcast. Generally, Marty is chasing the newest tech trends, which explains his interest in A.I. for teaching, research, and productivity. Marty is an active presenter and past president of the NorthEast Ohio Apple Corp (NEOAC). Jim Rea built his own computer from scratch in 1975, started programming in 1977, and has been an independent Mac developer continuously since 1984. He is the founder of ProVUE Development, and the author of Panorama X, ProVUE's ultra fast RAM based database software for the macOS platform. He's been a speaker at MacTech, MacWorld Expo and other industry conferences. Follow Jim at provue.com and via @provuejim@techhub.social on Mastodon. Support:      Become a MacVoices Patron on Patreon     http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Mastodon:     https://mastodon.cloud/@chuckjoiner      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Apple has debunked media reports claiming low adoption of iOS 26. Chuck Joiner, David Ginsburg, Marty Jencius, Web Bixby, Jim Rea, Eric Bolden, and Jeff Gamet discuss the assertion that the data was skewed by Apple's privacy-driven device misreporting. They review how official numbers show strong uptake among eligible devices and debate whether criticisms of the new interface are overblown. While some UI concerns are acknowledged, the group agrees the release offers meaningful improvements and is far from the failure some headlines suggested.  This edition of MacVoices is brought to you by our Patreon supporters. Get access to the MacVoices Slack and MacVoices After Dark by joining in at Patreon.com/macvoices. Show Notes: Chapters: 0:00 iOS adoption controversy introduced 0:28 Claims of low adoption challenged 2:04 Telemetry and agent string misreporting 3:50 Evaluating Apple's official adoption numbers 5:13 Privacy-driven device obfuscation explained 6:30 Clickbait and misinterpreted analytics reports 7:57 Debate over "liquid glass" interface complaints 9:03 Objective UI usability concerns raised 12:03 Design philosophy and Apple's UI direction 13:18 System Settings and long-term interface frustrations 15:49 Improvements and benefits in iOS 26 18:35 Broader reflections on Apple UI evolution 19:12 Overall assessment: not a disaster, but debated Links: Apple Reveals How Many iPhones Are Running iOS 26 https://www.macrumors.com/2026/02/13/apple-shares-ios-26-adoption-stats/ Guests: Web Bixby has been in the insurance business for 40 years and has been an Apple user for longer than that.You can catch up with him on Facebook, Twitter, and LinkedIn, but prefers Bluesky. Eric Bolden is into macOS, plants, sci-fi, food, and is a rural internet supporter. You can connect with him on Twitter, by email at embolden@mac.com, on Mastodon at @eabolden@techhub.social, on his blog, Trending At Work, and as co-host on The Vision ProFiles podcast. Jeff Gamet is a technology blogger, podcaster, author, and public speaker. Previously, he was The Mac Observer's Managing Editor, and the TextExpander Evangelist for Smile. He has presented at Macworld Expo, RSA Conference, several WordCamp events, along with many other conferences. You can find him on several podcasts such as The Mac Show, The Big Show, MacVoices, Mac OS Ken, This Week in iOS, and more. Jeff is easy to find on social media as @jgamet on Twitter and Instagram, jeffgamet on LinkedIn., @jgamet@mastodon.social on Mastodon, and on his YouTube Channel at YouTube.com/jgamet. David Ginsburg is the host of the weekly podcast In Touch With iOS where he discusses all things iOS, iPhone, iPad, Apple TV, Apple Watch, and related technologies. He is an IT professional supporting Mac, iOS and Windows users. Visit his YouTube channel at https://youtube.com/daveg65 and find and follow him on Twitter @daveg65 and on Mastodon at @daveg65@mastodon.cloud. Dr. Marty Jencius has been an Associate Professor of Counseling at Kent State University since 2000. He has over 120 publications in books, chapters, journal articles, and others, along with 200 podcasts related to counseling, counselor education, and faculty life. His technology interest led him to develop the counseling profession 'firsts,' including listservs, a web-based peer-reviewed journal, The Journal of Technology in Counseling, teaching and conferencing in virtual worlds as the founder of Counselor Education in Second Life, and podcast founder/producer of CounselorAudioSource.net and ThePodTalk.net. Currently, he produces a podcast about counseling and life questions, the Circular Firing Squad, and digital video interviews with legacies capturing the history of the counseling field. This is also co-host of The Vision ProFiles podcast. Generally, Marty is chasing the newest tech trends, which explains his interest in A.I. for teaching, research, and productivity. Marty is an active presenter and past president of the NorthEast Ohio Apple Corp (NEOAC). Jim Rea built his own computer from scratch in 1975, started programming in 1977, and has been an independent Mac developer continuously since 1984. He is the founder of ProVUE Development, and the author of Panorama X, ProVUE's ultra fast RAM based database software for the macOS platform. He's been a speaker at MacTech, MacWorld Expo and other industry conferences. Follow Jim at provue.com and via @provuejim@techhub.social on Mastodon. Support:      Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Send a textOn this powerful episode, Cornell Bunting sits down with Darlande Jean-Charles, RN, BSN — National IV Instructor, founder of Nurse U2 Wellness, and a nurse on a mission to redefine personalized care.Darlande's journey is one of resilience and purpose. After immigrating from Haiti to America at 13 — not speaking English and facing bullying while adjusting to a new life with her adopted parents — she found strength through adversity. Caring for her adopted mother during her battle with cancer became the moment that revealed her calling.Her nursing career began in 2013 as a Home Health Aide while pursuing her LPN. She went on to specialize in Alzheimer's and dementia care, earned her RN in 2018, and later became a Director of Nursing leading teams of over 90 staff in Assisted Living and Memory Care. Determined to grow, she expanded into hospital care in Med-Surg, Telemetry, and the Emergency Room, earning her Bachelor of Science in Nursing in 2024. That same year, she became a certified National IV Instructor, blending her love for teaching with clinical excellence.Today, through Nurse U2 Wellness, Darlande provides concierge wellness and IV hydration services that combine professionalism, compassion, and convenience — empowering clients to feel their best wherever they are.This conversation is about faith, resilience, education, and answering your calling. Tune in now — link in bio Listen. Share. Be inspired. Support the showThank you for tuning in with EHAS CLUB - Stories to Create Podcast

In this episode of Gamebird University, James sits down with Dr. Ryan Askren, Director of the Five Oaks Agricultural Research & Education Center, to refocus the lens on the wintering grounds—where habitat configuration, disturbance, and management decisions shape duck behavior long before spring. James and Ryan dig into what modern GPS/GSM telemetry is really telling us about winter movements, night feeding, and sanctuary use—and where tag choice can bias migration inferences. They explore how wetland complexes outperform single units, why scrub-shrub/buttonbush cover may be undervalued for thermal refuge and predator avoidance, and what fecal DNA diet work reveals. The conversation connects science to practice: post-season water on non-timber units, hunt-rest rotations, and coordinating with neighbors to create the mosaic ducks actually select. Ryan also shares insights from comparative studies of backpack vs. implant transmitters (and what that means for estimating timing and survival) and closes with how the Five Oaks certificate program turns ecology-savvy students into equipment-ready managers who can calibrate sprayers, plan drawdowns, and talk shop with farmers.

In this Kitchen Side episode of The Long Game Podcast, Alex and David are joined by Nick Lafferty from Profound to unpack how teams are navigating AI search visibility amid shifting metrics, attribution challenges, and unclear best practices.They discuss how companies choose which prompts to track, why case studies in AI search are hard to define and share, where brand and citations fit into AI-generated answers, and what organizational bottlenecks are preventing teams from acting on AI search insights.Key TakeawaysPrompt selection matters, but most teams underestimate how much customer language and internal feedback should shape what they track in AI search.AI search case studies are difficult to standardize because visibility depends heavily on prompt framing, attribution models, and competitive sensitivity.Revenue and self-reported attribution remain the most reliable signals as clicks, impressions, and rankings become less dependable.Problem-based prompts frequently surface brand recommendations, even when users don't explicitly ask for tools or products.Citation share acts as an influence layer, shaping future AI responses even when a brand isn't directly recommended in the output.Brand-building activities upstream of content can meaningfully impact AI visibility by associating a company with specific problem spaces.AI search ownership is increasingly cross-functional, spanning growth, SEO, PR, comms, and product marketing rather than a single team.Internal resourcing and approval processes are major bottlenecks, especially for off-site efforts like Reddit and YouTube.Show LinksVisit Profound on LinkedInConnect with Nick Lafferty on LinkedInConnect with David Khim on LinkedIn and TwitterConnect with Alex Birkett on LinkedIn and TwitterConnect with Omniscient Digital on LinkedIn or TwitterWhat is Kitchen Side?One big benefit of running an agency or working at one is you get to see the “kitchen side” of many different businesses; their revenue, their operations, their automations, and their culture.You understand how things look from the inside and how that differs from the outside.You understand how the sausage is made. As an agency ourselves, we're working both on growing our clients' businesses as well as our own. This podcast is one project, but we also blog, make videos, do sales, and have quite a robust portfolio of automations and hacks to run our business.We want to take you behind the curtain, to the kitchen side of our business, to witness our brainstorms, discussions, and internal dialogues behind the public works that we ship.Past guests on The Long Game podcast include: Morgan Brown (Shopify), Ryan Law (Animalz), Dan Shure (Evolving SEO), Kaleigh Moore (freelancer), Eric Siu (Clickflow), Peep Laja (CXL), Chelsea Castle (Chili Piper), Tracey Wallace (Klaviyo), Tim Soulo (Ahrefs), Ryan McReady (Reforge), and many more.Some interviews you might enjoy and learn from:Actionable Tips and Secrets to SEO Strategy with Dan Shure (Evolving SEO)Building Competitive Marketing Content with Sam Chapman (Aprimo)How to Build the Right Data Workflow with Blake Burch (Shipyard)Data-Driven Thought Leadership with Alicia Johnston (Sprout Social)Purpose-Driven Leadership & Building a Content Team with Ty Magnin (UiPath)Also, check out our Kitchen Side series where we take you behind the scenes to see how the sausage is made at our agency:Blue Ocean vs Red Ocean SEOShould You Hire Writers or Subject Matter Experts?How Do Growth and Content Overlap?Connect with Omniscient Digital on social:Twitter: @beomniscientLinkedin: Be OmniscientListen to more episodes of The Long Game podcast here: https://beomniscient.com/podcast/

Join us, while we're Waiting For Review... -- We are open for sponsorship! email us at contact@waitingforreview.com The Discord server is open to all, and you can contact us via our social links below. Enjoy the show, Dave ✨ and Daniel

From historic medical evacuations to missing galaxies and stunning new images of the Milky Way, today's episode covers the latest breaking news from space exploration and astronomy. Join Anna and Avery as they discuss six fascinating stories from across the cosmos.---## Episode Timestamps**[00:00]** Intro  **[01:15]** Story 1: ISS Medical Evacuation  **[04:45]** Story 2: The Mystery of Missing Tiny Galaxies  **[08:30]** Story 3: NASA's MAVEN Spacecraft in Trouble  **[11:45]** Story 4: Viruses Behave Differently in Microgravity  **[14:30]** Story 5: Two New Exoplanets and Redefining Habitable Zones  **[17:00]** Story 6: Stunning New Radio Image of the Milky Way  **[19:30]** Outro---## Stories Covered### 1. Historic First Medical Evacuation from ISSFour International Space Station crew members successfully completed the first-ever medical evacuation in the ISS's 26-year history, splashing down safely in the Pacific Ocean off San Diego.**Key Points:**- SpaceX Crew-11 returned early after 5 months in space- Crew included US astronauts Mike Fincke and Zena Cardman, Russian cosmonaut Oleg Platonov, and Japanese astronaut Kimiya Yui- Splashdown occurred at 12:41 AM ET on January 15, 2026- Affected crew member remains in stable condition- Three crew members remain aboard ISS to continue operations- Demonstrates importance of medical protocols in long-duration spaceflight**Read More:**- [Phys.org: ISS astronauts splash down on Earth after first-ever medical evacuation](https://phys.org/news/2026-01-iss-astronauts-splash-earth-medical.html)---### 2. The Universe's Missing Tiny GalaxiesNew research using the James Webb Space Telescope suggests there may be far fewer small galaxies in the early universe than predicted by current models, challenging our understanding of cosmic evolution.**Key Points:**- Study led by Xuheng Ma from University of Wisconsin-Madison- Used JWST's UNCOVER program to study galaxies through gravitational lensing- Observed the Epoch of Reionization (12-13 billion years ago)- Discovery of "faint-end suppression" - galaxy numbers drop off at smaller sizes- Suggests intense radiation from early massive stars prevented small galaxies from forming- May require rethinking models of cosmic reionization- Used Abell 2744 galaxy cluster as a natural gravitational lens**Why It Matters:**This finding has major implications for our understanding of how the universe evolved from the "cosmic dark ages" to its current transparent state.**Read More:**- [Space.com: The universe should be packed with tiny galaxies — so where are they?](https://www.space.com/astronomy/galaxies/the-universe-should-be-packed-with-tiny-galaxies-so-where-are-they)- Research paper on arXiv (preprint database)---### 3. NASA Pessimistic About Recovering MAVEN Mars OrbiterNASA officials acknowledge it's "very unlikely" they'll recover the MAVEN spacecraft, which has been silent since December 6, 2025, marking a potential end to a highly productive Mars mission.**Key Points:**- MAVEN (Mars Atmosphere and Volatile Evolution) launched November 2013, entered Mars orbit September 2014- Last communication: December 6, 2025- Telemetry indicates spacecraft is tumbling and orbit may have changed- Solar conjunction (Mars and Earth on opposite sides of Sun) complicated recovery efforts- Attempts to photograph spacecraft with Curiosity rover were unsuccessful- Other orbiters (Mars Reconnaissance Orbiter, Mars Odyssey, ExoMars Trace Gas Orbiter) can maintain communications relay- Spacecraft studied Mars atmospheric loss and recently observed interstellar object 3I/ATLAS**Mission Legacy:**Despite the likely loss, MAVEN has provided over a decade of groundbreaking data about Mars' upper atmosphere and how solar wind strips away the Martian atmosphere.**Read More:**- [SpaceNews: NASA pessimistic about odds of recovering MAVEN](https://spacenews.com/nasa-pessimistic-about-odds-of-recovering-maven/)- [NASA Science: MAVEN Spacecraft Updates](https://science.nasa.gov/blogs/maven/)---### 4. Space Station Study Reveals Unusual Virus-Bacteria DynamicsUniversity of Wisconsin-Madison researchers discovered that viruses infecting bacteria evolve differently in microgravity, potentially opening new avenues for fighting antibiotic-resistant infections on Earth.**Key Points:**- Study used E. coli bacteria and bacteriophage T7- Parallel experiments conducted on ISS and Earth- Virus infection delayed but not blocked in microgravity- Both viruses and bacteria developed unique mutations in space- Space-evolved viruses showed increased activity against drug-resistant E. coli strains- Findings could lead to improved phage therapy for antibiotic-resistant infections- Published in PLOS Biology journal- Demonstrates ISS value as unique research platform**Scientific Significance:**This research shows how the space environment fundamentally alters evolutionary processes, and how these insights can be applied to solve problems on Earth.**Read More:**- [Space Daily: Space station study reveals unusual virus bacteria dynamics in microgravity](https://www.spacedaily.com/reports/Space_station_study_reveals_unusual_virus_bacteria_dynamics_in_microgravity_999.html)- Research paper: "Microgravity reshapes bacteriophage host coevolution aboard the International Space Station" in PLOS Biology---### 5. Two New Exoplanets Challenge Habitable Zone DefinitionsAstronomers have discovered two exoplanets orbiting red dwarf stars that are prompting scientists to expand the definition of potentially habitable worlds through the concept of "temperate zones."**Key Points:**- Research led by Madison Scott (University of Birmingham) and Georgina Dransfield (University of Oxford)- Introduces "temperate zone" concept: broader than traditional habitable zone- Temperate zone defined by insolation flux range: 0.1 < S/S⊕ < 5 (136-6,805 W/m²)- TOI-6716 b: Earth-sized (0.91-1.05 Earth radii), likely rocky- TOI-7384 b: Sub-Neptune (3.35-3.77 Earth radii), rocky core with thick H/He envelope- Both orbit mid to late-type M dwarfs (red dwarf stars)- Part of TEMPOS survey (Temperate M Dwarf Planets With SPECULOOS)- Good candidates for atmospheric studies with JWST- Paper submitted to Monthly Notices of the Royal Astronomical Society**Why Temperate Zones Matter:**As our understanding of habitability evolves, planets in temperate zones may prove more interesting than initially thought, especially for atmospheric characterization studies.**Read More:**- [Universe Today: Two New Exoplanets And The Need For New Habitable Zone Definitions](https://www.universetoday.com/articles/two-new-exoplanets-and-the-need-for-new-habitable-zone-definitions)---### 6. Most Detailed Radio Image of Milky Way Reveals Hidden StructuresAstronomers in Australia have released the most detailed low-frequency radio map of the Milky Way's southern sky, revealing thousands of previously hidden cosmic structures.**Key Points:**- Created by International Centre for Radio Astronomy Research (ICRAR)- Used Murchison Widefield Array (MWA) telescope in Western Australia- Data collected over 141 nights between 2013-2020- Required over 1 million CPU hours to process- GLEAM-X survey: 2x resolution, 10x sensitivity, 2x sky coverage vs. previous efforts- Cataloged over 98,000 radio sources- Shows supernova remnants (red circles) and stellar nurseries (blue regions)- Helps identify hidden supernova remnants and study pulsars- Led by PhD student Silvia Mantovanini (Curtin University)- First complete low-frequency radio image of Southern Galactic Plane**Future Impact:**This image serves as a foundation for the upcoming SKA-Low array, which will provide even more detailed views of the universe when operational.**Read More:**- [Daily Galaxy: New Image of the Milky Way Reveals Massive Hidden Structures](https://dailygalaxy.com/2026/01/new-image-milky-way-massive-structures/)- [ICRAR: GLEAM-X Galactic Plane](https://www.icrar.org/gleam-x-galactic-plane/)---## Key Terms Explained**Habitable Zone:** The range of distances from a star where conditions might allow liquid water to exist on a planet's surface.**Temperate Zone:** A broader classification than habitable zone, encompassing planets that receive moderate levels of stellar radiation.**Insolation Flux:** The amount of solar energy reaching a planet's surface, measured in watts per square meter.**Epoch of Reionization:** A period roughly 12-13 billion years ago when the first stars and galaxies began flooding the universe with ultraviolet light.**Gravitational Lensing:** The bending of light by massive objects due to gravity, which can magnify and brighten distant objects.**Bacteriophage:** A virus that infects and replicates within bacteria.**Solar Conjunction:** When Mars and Earth are on opposite sides of the Sun, disrupting radio communications.**M Dwarf (Red Dwarf):** Small, cool, dim stars that are the most common type of star in the galaxy.**Supernova Remnant:** The expanding cloud of gas and magnetic fields left behind after a star explodes.**Luminosity Function:** A cosmic census tool showing the distribution of galaxies at different brightness levels.---## Resources & Further Reading**Space Agencies:**- [NASA](https://www.nasa.gov)- [European Space Agency (Become a supporter of this podcast: https://www.spreaker.com/podcast/astronomy-daily-space-news-updates--5648921/support.Sponsor Details:Ensure your online privacy by using NordVPN. To get our special listener deal and save a lot of money, visit www.bitesz.com/nordvpn. You'll be glad you did!Become a supporter of Astronomy Daily by joining our Supporters Club. Commercial free episodes daily are only a click way... Click HereThis episode includes AI-generated content.

Jeff Smith and Carson Odegard welcome Cory Overton, California Waterfowl's new Science Director, for a clear, field-level look at how modern telemetry is rewriting what we know about duck movements—and how that science feeds better habitat work and smarter regs. From the original PINSAT satellite project to today's GPS/cellular tags and emerging smart bands, Cory explains what the data actually show: longer staging in SONEC/Klamath, pintail that roam like “five-year-olds on espresso,” fog-driven chaos that scatters birds, and why some geese will cross wildfires or even sit down on the ocean to ride out smoke. He also digs into CWA's role training the next generation with UC Davis and how new assessment tools will tie real duck use to on-the-ground management.Episode highlightsTelemetry 101 to now — from old VHF triangulation to GPS/cellular tags and first-gen smart bands that could run for decadesWhat PINSAT taught us — SONEC as the spring gas station, and how routes/timing have shifted since the early 2000sFog, storms, and smoke — why pea-soup weeks burn calories, scramble patterns, and sometimes push birds hundreds of miles the “wrong” wayPintail vs. mallards — restless travelers vs. homebodies, and how that plays into the new pintail frameworkKlamath staging — more birds lingering north into winter, with some not dropping to the Valley until late (or at all)What's next at CWA — postseason pintail banding, valley-wide habitat assessment tools, and a UC Davis pipeline for future wetland pros

In this episode of The Broadband Bunch, host Pete Pizzutillo speaks with Dan Siemon, CEO of Preseem, about helping regional broadband providers compete more effectively through proactive network intelligence. Dan shares his path from building early ISP networks to leading Preseem, a solution designed to give operators clear visibility into network performance and customer experience. The conversation explores how telemetry, latency analysis, and vendor-agnostic data normalization enable operators to move beyond reactive troubleshooting and focus on the issues that have the biggest impact. Pete and Dan also discuss AI's emerging role in customer support, the challenges of scaling smaller providers, and why strong local ISPs remain essential to their communities.

This week's episode showcases the result of when two dedicated fisheries biologists and passionate anglers come together to record a podcast. Conrad had the absolute pleasure of interviewing Erin Wilson, an avid multispecies angler and fisheries biologist. Erin has leveraged her passion and skills in her career, discussing how instrumental being an angler has been for her success in the fisheries world. She shared insights from her remarkable master's studies, highlighting her first chapter on muskie movement ecology, and the second chapter focused on the use of biologgers. Additionally, she touched on the power of communication and the valuable lessons learned from engaging with expert knowledge holders in her field. Erin also emphasized the significance of current technologies and her concerns in the fishing world as we move forward. We hope you learn just as much from this conversation as Conrad did this week. Takeaway: Follow what you want to do in life, what you're good at, and what you're passionate about, and don't let anyone deter you along the way.    #muskie #muskellung #acoustictelemetry #movementecology #fisheriesbiology #biologgers #muskiefishing #sciencecommunication “Get in touch with us! The Fisheries Podcast is on Facebook, X, Instagram, Threads, and Bluesky: @FisheriesPod  Become a Patron of the show: https://www.patreon.com/FisheriesPodcast Buy podcast shirts, hoodies, stickers, and more: https://teespring.com/stores/the-fisheries-podcast-fan-shop Thanks as always to Andrew Gialanella for the fantastic intro/outro music. The Fisheries Podcast is a completely independent podcast, not affiliated with a larger organization or entity. Reference to any specific product or entity does not constitute an endorsement or recommendation by the podcast. The views expressed by guests are their own and their appearance on the program does not imply an endorsement of them or any entity they represent. Views and opinions expressed by the hosts are those of that individual and do not necessarily reflect the view of any entity with those individuals are affiliated in other capacities (such as employers).”

The world record for fastest pit stop—a mere 1.8 seconds—was set by the McLaren F1 Team at the Qatar Grand Prix in 2023. It's an incredible feat of speed and choreography; a pit stop that fast can't happen without a team of people operating at peak human performance. But as Dan Keyworth explains, AI plays a crucial role, too. As the Director of Business Technology at McLaren Racing, Dan is responsible for helping the whole team perform at their best—and that starts with having the right tools. Whether it's the firehose of sensor data coming off a race car, video analysis of the pit crew in action, or marketing analytics for the next Grand Prix, AI helps the McLaren F1 Team make the right decisions—and make them fast.On this episode, Dan talks about the importance of getting simple answers from complex data, how they use Dropbox Dash, and why we shouldn't think of AI as labor replacement so much as laborious replacement.You can learn more about the McLaren F1 Team at mclaren.com/racing/formula-1. And if you haven't already seen it, be sure to watch their world record pit stop at youtube.com/watch?v=tRBOiq-Q6_s. Seriously, it's blink-and-you'll-miss-it fast.~ ~ ~Working Smarter is brought to you by Dropbox Dash—the AI universal search and knowledge management tool from Dropbox. Learn more at workingsmarter.ai/dashYou can listen to more episodes of Working Smarter on Apple Podcasts, Spotify, YouTube Music, Amazon Music, or wherever you get your podcasts. To read more stories and past interviews, visit workingsmarter.aiThis show would not be possible without the talented team at Cosmic Standard: producer Dominic Girard, sound engineer Aja Simpson, technical director Jacob Winik, and executive producer Eliza Smith. Special thanks to our illustrators Justin Tran and Fanny Luor, marketing consultant Meggan Ellingboe, and editorial support from Catie Keck. Our theme song was composed by Doug Stuart. Working Smarter is hosted by Matthew Braga. Thanks for listening!

Gaming Industry analyst and #GamesNightViz co-Lead Louis Yu pops inWe talk about the rise of indie studios and collapse of major studios, dissect pricing models (some predatory, and break down player data telemetryMake sure to check out Louis LinkedIn group for the gaming industry and his show 'Secrets of the Viz'

Dr. Naima Maqsood, Dr. Kelly Arps, and Dr. Jake Roberts discuss the acute management of atrial fibrillation with guest expert Dr. Jonathan Chrispin. Episode audio was edited by CardioNerds Intern Dr. Bhavya Shah. This episode reviews acute management strategies for atrial fibrillation. Atrial fibrillation is the most common chronic arrhythmia worldwide and is associated with increasingly prevalent comorbidities, including advanced age, obesity, and hypertension. Atrial fibrillation is a frequent indication for hospitalization and a complicating factor during hospital stays for other conditions. Here, we discuss considerations for the acute management of atrial fibrillation, including indications for rate versus rhythm control strategies, treatment targets for these approaches, considerations including pharmacologic versus electrical cardioversion, and management in the post-operative setting. CardioNerds Atrial Fibrillation PageCardioNerds Episode PageCardioNerds AcademyCardionerds Healy Honor Roll CardioNerds Journal ClubSubscribe to The Heartbeat Newsletter!Check out CardioNerds SWAG!Become a CardioNerds Patron! Pearls A key component to the management of acute atrial fibrillation involves addressing the underlying cause of the acute presentation. For example, if a patient presents with rapid atrial fibrillation and signs of infection, treatment of the underlying infection will help improve the elevated heart rate. Selecting a rate control versus rhythm control strategy in the acute setting involves considerations of comorbid conditions such as heart failure and competing risk factors such as critical illness that may favor one strategy over another. Recent data strongly supports the use of rhythm control in heart failure patients. Patients should be initiated on anticoagulation prior to pursuing a rhythm control strategy. There are several strategies for rate control medications with therapies including beta-blockers, non-dihydropyridine calcium channel blockers, and digoxin. The selection of which agent to use depends on additional comorbidities and the overall clinical assessment. For example, a patient with severely decompensated low-output heart failure may not tolerate a beta-blocker or calcium channel blocker in the acute phase due to hypotension risks but may benefit from the use of digoxin to provide rate control and some inotropic support. Thromboembolic prevention remains a cornerstone of atrial fibrillation management, and considerations must always be made in terms of the duration of atrial fibrillation, thromboembolic risk, and risks of anticoagulation. While postoperative atrial fibrillation is more common after cardiac surgeries, there is no major difference in management between patients who undergo cardiac versus non-cardiac procedures. Considerations involve whether the patient has a prior history of atrial fibrillation, surgery-specific bleeding risks related to anticoagulation, and monitoring in the post-operative period to assess for recurrence. Notes 1. Our first patient is a 65-year-old man with obesity, hypertension, obstructive sleep apnea, and pre-diabetes presenting for evaluation of worsening shortness of breath and palpitations. The patient has no known history of heart disease. Telemetry shows atrial fibrillation with ventricular rates elevated to 130-140 bpm. What would be the initial approach to addressing the acute management of atrial fibrillation in this patient? What are some of the primary considerations in the initial history and chart review? An important first step involves taking a careful history to understand the timing of symptom onset and potential underlying causes contributing to a patient's acute presentation with rapid atrial fibrillation. Understanding the episode trigger determines management by targeting reversible causes of the acute presentation and elucidating whether the episode is triggered by a cardiac or non-c...

Episode 86: You all told us what you hated about Windows 11, and we fully agreed. So in this episode we go through all our grievances with the current state of Windows.CHAPTERS00:00 - Intro06:21 - Unnecessary Microsoft accounts10:39 - Search is broken15:49 - Splash screens and ads20:52 - The right click context menu26:53 - Pre-installed bloatware33:21 - Windows updates hurting performance38:41 - Telemetry capture and data mining42:28 - Copilot AI integration45:45 - Updates breaking things48:14 - Inability to dismiss pop-ups and updates50:25 - Janky monitor issues58:21 - Removing useful customization options1:01:06 - Driver updates via Windows Update breaking things1:05:17 - Microsoft Store1:09:21 - Is Linux an alternative for gaming PCs?1:14:36 - Summary of the current state of Windows1:17:44 - Updates from our boring livesSUBSCRIBE TO THE PODCASTAudio: https://shows.acast.com/the-hardware-unboxed-podcastVideo: https://www.youtube.com/channel/UCqT8Vb3jweH6_tj2SarErfwSUPPORT US DIRECTLYPatreon: https://www.patreon.com/hardwareunboxedLINKSYouTube: https://www.youtube.com/@Hardwareunboxed/Twitter: https://twitter.com/HardwareUnboxedBluesky: https://bsky.app/profile/hardwareunboxed.bsky.social Hosted on Acast. See acast.com/privacy for more information.

Telemetry is changing the underwriting game, enabling a shift from clunky forms to real-time, verifiable risk data.In this episode, host Anthony Hess sits down with Alex Jomaa, Chief Underwriting Officer at Onda, to explore how real-time data is transforming cyber underwriting, and why it's time the industry stopped relying on outdated processes that frustrate clients and slow brokers down.Alex explains how Onda's Navigator platform integrates directly with a client's infrastructure to deliver objective, verifiable cyber risk insights, thereby eliminating the back-and-forth of long-form questionnaires. In addition, he unpacks the biggest hurdles to cyber adoption, from poor timing and over-complication to misaligned incentives and volatile pricing cycles.You'll learn:1. How telemetry brings scale, accuracy, and speed to cyber underwriting2. What really stops buyers from purchasing cyber policies3. How brokers can sell cyber coverage more effectively4. The key signals Onda uses to assess cyber hygiene and risk quality5. Why market volatility is damaging long-term trust in cyber insurance___________Get in touch with Alex Jomaa on LinkedIn: https://www.linkedin.com/in/alex-jomaa-b84b8520/ ___________About the host Anthony Hess:Anthony is passionate about cyber insurance. He is the CEO of Asceris, which supports clients to respond to cyber incidents quickly and effectively. Originally from the US, Anthony now lives in Europe with his wife and two children.Get in touch with Anthony on LinkedIn: https://www.linkedin.com/in/anthonyhess/ or email: ahess@asceris.com.___________Thanks to our friends at SAWOO for producing this episode with us!

The boys are honored to welcome Living Colour legend #VernonReid who talks about his latest solo album “Hoodoo Telemetry”, released earlier this month on Artone / The Players Club Records.The guitar phenom also shares his thoughts on the legacy of the band's iconic single “Cult Of Personality” and how it still resonates today, using music as a tool to address political issues and more!SHOW CREDITS: Diamond Dave Kinchen & Emerald Shane McEachern (hosts). Intro made in part w/ Drum Pad Machine (DPM). Instagram: @RockNationsDK Twitter: @RockNationsDK. Facebook: @RockofNationsDK.

In part 2 of our discussion with Fisheries Technician Erin Wilson, we turn our attention to the science of muskies and muskie ecology.  Erin delves into the whys and hows of collecting data and provides fascinating insights as to how she uses not only technology to learn about these fish, but also how she draws upon the community of anglers itself to provide critical data on this elusive species.  An insightful and interesting talk on the science of muskies is the result.  Topics include: - Casting and breaking down spots - Equipment setup- Using livescope- Erin's undergraduate - talking to muskie anglers for research- The individualism of muskies- Telemetry and other technological data collection efforts 

Hoodoo Telemetry is Vernon Reid's deepest, most profound work thus far. Vernon joins us to discuss.

Lauren Basile joins us to show how traffic-aware cost intelligence turns spreadsheet guesswork into one-click, per-slice cost estimates across customers, ASNs, and CDNs. Learn about the SNMP plus contracts foundation, the flow-data leap, and how NetOps teams use cost-per-Mbps and path insights to optimize spend, pricing, and margins.

In episode 152 of Cybersecurity Where You Are, Sean Atkinson is joined by Cliff Moten, Manager, Cybersecurity Solutions Engineering at the Center for Internet Security® (CIS®); and Richard Vargas, Security Operations Center Manager at CIS. Together, they discuss how the 24x7x365 CIS Security Operations Center (SOC) and CIS Managed Detection and Response™ (CIS MDR™) work together to accelerate response time while enriching telemetry. Here are some highlights from our episode:01:40. Demystifying SOCs and MDR as cybersecurity concepts02:52. How the CIS SOC works to provide information, context, and next steps for an event05:04. Artificial intelligence and automation as ways to accelerate response time10:20. Real-world instances where a fast response time made a difference13:10. What it means to support underfunded organizations with the resources they need17:22. The role of contextual cyber threat intelligence in accelerating response times19:01. The value of security orchestration, automation, and response (SOAR) in helping defenders move quickly27:33. Lessons that organizations can use to cut down on their incident response timesResourcesThe CIS Security Operations Center (SOC): The Key to Growing Your SLTT's Cyber MaturityEpisode 148: How MDR Helps Shine a Light on Zero-Day AttacksEpisode 144: Carrying on the MS-ISAC's Character and CultureEpisode 137: National Cybersecurity Through SLTT ResilienceCombatting RansomwareEstablishing Essential Cyber HygieneCIS Community Defense Model 2.0If you have some feedback or an idea for an upcoming episode of Cybersecurity Where You Are, let us know by emailing podcast@cisecurity.org.

In this episode of the Identity at the Center podcast, hosts Jeff and Jim engage in an insightful conversation with Darren Rolls, a veteran in the Identity and Access Management (IAM) field. They discuss the complexities of identity fabrics, the evolving landscape of IAM, the impact of AI, and the challenges of integrating new technologies with legacy systems. Darren shares his thoughts on upcoming trends, practical advice for IAM practitioners, and even his personal experience with kite surfing. Tune in to gain expert perspectives on the future of IAM and the significance of continuous learning and adaptation in this dynamic field.Connect with Darran: https://www.linkedin.com/in/darran-rolls/Identity Innovations Blog: https://identityinnovationlabs.com/identity-insights/Chapters00:00 Introduction and Casual Banter00:17 Discussing Identity Fabrics and Leadership Compass03:19 Upcoming Conferences and Events05:32 Interview with Darren Rolls: Identity Management Journey09:09 Evolution and Challenges in Identity Management24:41 Future of Identity Management and AI32:05 The Future of IAM in the Age of AI33:12 The Rise of Agent-Based Applications34:12 Challenges in Identity and Access Management35:31 Exploring Vibe Coding and AI Utilities38:09 Monitoring and Telemetry in IAM40:17 The Evolution of Identity Management42:05 The Role of Laws in IAM Architecture46:16 Balancing Legacy Systems with Future Innovations51:39 Kite Surfing Adventures and Reflections59:01 Closing Thoughts and Future EngagementsConnect with us on LinkedIn:Jim McDonald: https://www.linkedin.com/in/jimmcdonaldpmp/Jeff Steadman: https://www.linkedin.com/in/jeffsteadman/Visit the show on the web at http://idacpodcast.com

This week, Ford unveiled a new electric strategy and manufacturing process to a mixed reaction. But it might be one of the most important moves the company makes. Sam Abuelsamid, host of the Wheel Bearings podcast and VP of Market Research at Telemetry, joins us for an in-depth, realistic conversation. We get into the future of electric vehicles in the United States, the importance of why US companies need a real electric strategy no matter what Washington does, and the reality that the future for US automakers is not guaranteed. Feedback as always - dailydetroit -at- gmail -dot- com or leave a voicemail 313-789-3211. Follow Daily Detroit on Apple Podcasts: https://podcasts.apple.com/us/podcast/daily-detroit/id1220563942  Or sign up for our newsletter: https://www.dailydetroit.com/newsletter/  

In this Telemetry News Now episode, Phil Gervasi and Justin Ryburn tackle Intel's plan to spin off its Network & Edge Group (NEX) and what it means for high‑performance Ethernet NICs, examine Cisco's new partnership with Hugging Face to scan every open‑source AI model for malware, and break down Broadcom's Jericho4 fabric router—bringing 3.2 Tb/s “hyper‑ports” to distributed AI clusters. The hosts also discuss the real‑world state of SD‑WAN adoption, Palo Alto Networks' $25 B CyberArk acquisition, Cisco's quantum‑networking research, and upcoming industry events. Plus: a personal tale of basement‑automation triumph to kick things off.

F1 Racing and the markets. Earnings, economics and the Fed. The casino - zero date options. Thomas Thornton, Hedge Fund Telemetry is this week's guest. NEW! DOWNLOAD THE AI GENERATED SHOW NOTES (Guest Segment)     Stay Updated Thomas Thornton is a former portfolio manager, senior trader, and technical analyst with Level Global Investors and Galileo Capital. Tom has written a daily market note for a select group of hedge fund managers for years and now has offered it for all investors with Hedge Fund Telemetry. His long term focus on sentiment indicators borders on the obsessive. Our growing team at Hedge Fund Telemetry is comprised of current and former buy and sell side individuals. Hedge Fund Telemetry was first conceived with inspiration from Tom's lifelong passion following Formula 1 racing. In the early 90's, Formula 1 teams started to equip cars with sensors on every imaginable component and data was relayed wirelessly through telemetry to the pits to analyze and then instructions from the pits were relayed back to the driver so he could make changes to find the optimal balance for the car. It has always been the same way for Tom, as a senior trader at his hedge fund, he would get in early, collect data from many sources, analyze that data, and then communicate information out to his firm so his team could properly balance the firm's portfolio. It's now our goal to relay that same type of information so that one can also gain that edge. Follow @TommyThornton Check this out and find out more at: http://www.interactivebrokers.com/ Follow @andrewhorowitz Looking for style diversification? More information on the TDI Managed Growth Strategy - HERE Stocks mentioned in this episode: (MSFT), OKLO), (SMR), (WING), (NVDA), (CEG)

Phil Gervasi sits down with Kentik Product Marketing Manager Eric Hian-Cheong to discuss why data enrichment is the "secret sauce" that turns raw flow logs, metrics, and cloud telemetry into true network intelligence. They explore how tagging telemetry with human-readable context—such as customer names, app IDs, Kubernetes labels, and more—shrinks mean-time-to-insight, empowers cross-team troubleshooting, and lays the groundwork for AI-driven operations.

This conversation is a must-listen for engineering leaders, CTOs, and operations professionals who are curious about how to deploy AI in complex, physical systems. It covers everything from telemetry data to orchestration engines, the role of human validation, AI-assisted SDLC, and team culture in AI adoption. If you're building or managing AI-first systems that interact with the real world, this episode offers hands-on insight and strategic direction.

In this episode, Elixir Wizard Charles Suggs sits down with Victor Björklund to map out the landscape of Python integration in Elixir applications. From HTTP APIs and external services to embedded runtimes like ErlPort, PythonX, and the Venomous library, we evaluate each approach's impact on performance, coupling, and developer experience. Victor draws on real-world examples like Scrapy-based web scraping and the Swedish BankID authentication to illustrate best practices for error handling, process pooling, and effective telemetry across the BEAM boundary. We also tackle the practical side of deployment: packaging Python dependencies in Mix releases, mocking Python calls in tests, and deploying multi-language apps with confidence. Wrapping up, Victor shares his wishlist for even tighter interop (think multiple Python interpreter instances per VM) and offers low-risk entry points, like automating monthly reports, for teams ready to explore the power of Python's ecosystem within Elixir. Key topics discussed in this episode: Integration methods: HTTP APIs, ports, ErlPort, PythonX, Venomous Performance vs. coupling trade-offs across interop patterns Managing the Global Interpreter Lock (GIL) with process pools Leveraging mature Python libraries (Scrapy, BankID, etc.) Error handling strategies across BEAM↔Python boundaries Testing mixed-language systems: mocks and integration tests Packaging and deploying Python alongside Elixir releases Monitoring and telemetry for multi-language pipelines Functional programming advantages in Elixir workflows Tool selection guidance by project requirements Future possibilities: multiple Python interpreters in one VM Community resources for Python–Elixir interop help Links mentioned: jawdropping.io https://cplusplus.com/ https://www.python.org/ https://react.dev/ https://nodejs.org/en https://erlport.org/ https://hexdocs.pm/pythonx/Pythonx.html https://pyrlang.github.io/Pyrlang/ Python GIL (Global Interpreter Lock): https://realpython.com/python-gil/ https://github.com/devinus/poolboy https://hexdocs.pm/venomous/Venomous.html Try-catch https://syntaxdb.com/ref/python/try-catch https://www.scrapy.org/ https://www.bankid.com/en/ https://www.phoenixframework.org/ https://www.tzeyiing.com/posts/using-a-hunky-poolboy-to-manage-your-python-erlport-processes-in-elixir/ https://medium.com/stuart-engineering/how-we-use-python-within-elixir-486eb4d266f9 https://x.com/bjorklundvictor https://victorbjorklund.com/ https://www.linkedin.com/in/victorbjorklund/ hello@victorbjorklund.com

In this Telemetry News Now episode, Phil and Justin cover the global Cloudflare DNS outage, a rumored $10B SentinelOne acquisition by Palo Alto Networks, submarine cable security concerns from U.S. lawmakers, a major Alaska Airlines data center failure, why some say data centers are obsolete before they open, and Arista's latest strategic hire. Plus, upcoming events and industry insights.

Luca Palmieri, author of Zero to Production in Rust and Principal Engineering Consultant at MainMatter, speaks with SE Radio host Gavin Henry about Rust in production. They discuss what production Rust means, how to get Rust code into production, specific Rust issues to think about when getting an application into production, what Rust profiles are, expected performance, telemetry options, error handling and what parts of Rust to use and avoid.  Palmieri discusses docker containers, tracing, robust Rust error handling, how performant Rust is in the real world, p50, p99, docker build techniques, project layouts, crates, speeding up Rust build times, unwrap(), panics, budgeting resources, inner development loops, the Facade Pattern, structured logging, and how to always use clippy. Brought to you by IEEE Computer Society and IEEE Software magazine.

Get to know Microsoft's latest Patch Tuesday updates and new features in Windows 11, such as improvements to the Start menu, File Explorer, and Copilot integration. They also cover new AI features coming to the Photos app for Copilot+ PCs and updates to the Microsoft Store. The discussion then shifts to developer conferences like Google I/O and Apple's WWDC, with a focus on their respective AI advancements and product strategies. Plus, the controversy surrounding Microsoft's decision to no longer host its Build conference in Seattle. Don't miss the discussion on the evolving role of the iPad as a potential threat to Surface devices due to recent software enhancements! Windows 11 June Patch Tuesday is here! Big changes for Windows 11 versions 22H2, 23H2, and 24H2 New Start menu finally debuts in Dev and Beta - synchronized again for some reason Copilot+ PCs get Relight feature and natural language search in the Photos app The Microsoft Store gets a major update in the Beta channel And Canary is still a thing, no one knows why Developer conference season draws to a close Build: Protests, problems, and more problems Microsoft pulls out of Seattle permanently Google I/O: Stunning array of AI announcements. But Android 16 is on a weird slow boil after a truncated development cycle Apple WWDC: Apple Intelligence? Look, Liquid Glass! Also, some actual advances across its newly unified platforms Look out Surface: The iPad is a real computer now - And it only took 15 years Microsoft, Google, and Apple all played to their strengths Between Windows 11 2xH2, Android 16, and iOS whatever - do the platform makers even know how to ship software anymore? Xbox Microsoft unveils the first Xbox-branded third-party gaming handheld as part of its Xbox Games Showcase 2025 event - a few interesting things there as well - COD: BO7, Gears remake, Gears v.next delayed to 2026 This heavily modified/optimized version of Windows 11 is coming to more gaming handhelds Looking to the future: What if this is literally the model for future Xbox console hardware? What if the next Xbox was a NUC? More Game Pass titles across platforms for the second half of June You can add 4 TB of storage to your Xbox, but it will cost you dearly Apple loses again in Epic v. Apple, Fortnite can stay in the App Store and developers can stop getting robbed by Apple The Nintendo Switch 2 launched this past week and is apparently the best-selling console of all time at launch PS5 controllers to support multiple Bluetooth connections Tips and Picks Tip of the week: Share Feature, image crunching App pick of the week: Dia Browser RunAs Radio this week: The Case for Telemetry with Liz Fong-Jones Brown liquor pick of the week: Glenlossie 26 Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: uscloud.com 1password.com/windowsweekly

Get to know Microsoft's latest Patch Tuesday updates and new features in Windows 11, such as improvements to the Start menu, File Explorer, and Copilot integration. They also cover new AI features coming to the Photos app for Copilot+ PCs and updates to the Microsoft Store. The discussion then shifts to developer conferences like Google I/O and Apple's WWDC, with a focus on their respective AI advancements and product strategies. Plus, the controversy surrounding Microsoft's decision to no longer host its Build conference in Seattle. Don't miss the discussion on the evolving role of the iPad as a potential threat to Surface devices due to recent software enhancements! Windows 11 June Patch Tuesday is here! Big changes for Windows 11 versions 22H2, 23H2, and 24H2 New Start menu finally debuts in Dev and Beta - synchronized again for some reason Copilot+ PCs get Relight feature and natural language search in the Photos app The Microsoft Store gets a major update in the Beta channel And Canary is still a thing, no one knows why Developer conference season draws to a close Build: Protests, problems, and more problems Microsoft pulls out of Seattle permanently Google I/O: Stunning array of AI announcements. But Android 16 is on a weird slow boil after a truncated development cycle Apple WWDC: Apple Intelligence? Look, Liquid Glass! Also, some actual advances across its newly unified platforms Look out Surface: The iPad is a real computer now - And it only took 15 years Microsoft, Google, and Apple all played to their strengths Between Windows 11 2xH2, Android 16, and iOS whatever - do the platform makers even know how to ship software anymore? Xbox Microsoft unveils the first Xbox-branded third-party gaming handheld as part of its Xbox Games Showcase 2025 event - a few interesting things there as well - COD: BO7, Gears remake, Gears v.next delayed to 2026 This heavily modified/optimized version of Windows 11 is coming to more gaming handhelds Looking to the future: What if this is literally the model for future Xbox console hardware? What if the next Xbox was a NUC? More Game Pass titles across platforms for the second half of June You can add 4 TB of storage to your Xbox, but it will cost you dearly Apple loses again in Epic v. Apple, Fortnite can stay in the App Store and developers can stop getting robbed by Apple The Nintendo Switch 2 launched this past week and is apparently the best-selling console of all time at launch PS5 controllers to support multiple Bluetooth connections Tips and Picks Tip of the week: Share Feature, image crunching App pick of the week: Dia Browser RunAs Radio this week: The Case for Telemetry with Liz Fong-Jones Brown liquor pick of the week: Glenlossie 26 Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: uscloud.com 1password.com/windowsweekly

Get to know Microsoft's latest Patch Tuesday updates and new features in Windows 11, such as improvements to the Start menu, File Explorer, and Copilot integration. They also cover new AI features coming to the Photos app for Copilot+ PCs and updates to the Microsoft Store. The discussion then shifts to developer conferences like Google I/O and Apple's WWDC, with a focus on their respective AI advancements and product strategies. Plus, the controversy surrounding Microsoft's decision to no longer host its Build conference in Seattle. Don't miss the discussion on the evolving role of the iPad as a potential threat to Surface devices due to recent software enhancements! Windows 11 June Patch Tuesday is here! Big changes for Windows 11 versions 22H2, 23H2, and 24H2 New Start menu finally debuts in Dev and Beta - synchronized again for some reason Copilot+ PCs get Relight feature and natural language search in the Photos app The Microsoft Store gets a major update in the Beta channel And Canary is still a thing, no one knows why Developer conference season draws to a close Build: Protests, problems, and more problems Microsoft pulls out of Seattle permanently Google I/O: Stunning array of AI announcements. But Android 16 is on a weird slow boil after a truncated development cycle Apple WWDC: Apple Intelligence? Look, Liquid Glass! Also, some actual advances across its newly unified platforms Look out Surface: The iPad is a real computer now - And it only took 15 years Microsoft, Google, and Apple all played to their strengths Between Windows 11 2xH2, Android 16, and iOS whatever - do the platform makers even know how to ship software anymore? Xbox Microsoft unveils the first Xbox-branded third-party gaming handheld as part of its Xbox Games Showcase 2025 event - a few interesting things there as well - COD: BO7, Gears remake, Gears v.next delayed to 2026 This heavily modified/optimized version of Windows 11 is coming to more gaming handhelds Looking to the future: What if this is literally the model for future Xbox console hardware? What if the next Xbox was a NUC? More Game Pass titles across platforms for the second half of June You can add 4 TB of storage to your Xbox, but it will cost you dearly Apple loses again in Epic v. Apple, Fortnite can stay in the App Store and developers can stop getting robbed by Apple The Nintendo Switch 2 launched this past week and is apparently the best-selling console of all time at launch PS5 controllers to support multiple Bluetooth connections Tips and Picks Tip of the week: Share Feature, image crunching App pick of the week: Dia Browser RunAs Radio this week: The Case for Telemetry with Liz Fong-Jones Brown liquor pick of the week: Glenlossie 26 Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: uscloud.com 1password.com/windowsweekly

Get to know Microsoft's latest Patch Tuesday updates and new features in Windows 11, such as improvements to the Start menu, File Explorer, and Copilot integration. They also cover new AI features coming to the Photos app for Copilot+ PCs and updates to the Microsoft Store. The discussion then shifts to developer conferences like Google I/O and Apple's WWDC, with a focus on their respective AI advancements and product strategies. Plus, the controversy surrounding Microsoft's decision to no longer host its Build conference in Seattle. Don't miss the discussion on the evolving role of the iPad as a potential threat to Surface devices due to recent software enhancements! Windows 11 June Patch Tuesday is here! Big changes for Windows 11 versions 22H2, 23H2, and 24H2 New Start menu finally debuts in Dev and Beta - synchronized again for some reason Copilot+ PCs get Relight feature and natural language search in the Photos app The Microsoft Store gets a major update in the Beta channel And Canary is still a thing, no one knows why Developer conference season draws to a close Build: Protests, problems, and more problems Microsoft pulls out of Seattle permanently Google I/O: Stunning array of AI announcements. But Android 16 is on a weird slow boil after a truncated development cycle Apple WWDC: Apple Intelligence? Look, Liquid Glass! Also, some actual advances across its newly unified platforms Look out Surface: The iPad is a real computer now - And it only took 15 years Microsoft, Google, and Apple all played to their strengths Between Windows 11 2xH2, Android 16, and iOS whatever - do the platform makers even know how to ship software anymore? Xbox Microsoft unveils the first Xbox-branded third-party gaming handheld as part of its Xbox Games Showcase 2025 event - a few interesting things there as well - COD: BO7, Gears remake, Gears v.next delayed to 2026 This heavily modified/optimized version of Windows 11 is coming to more gaming handhelds Looking to the future: What if this is literally the model for future Xbox console hardware? What if the next Xbox was a NUC? More Game Pass titles across platforms for the second half of June You can add 4 TB of storage to your Xbox, but it will cost you dearly Apple loses again in Epic v. Apple, Fortnite can stay in the App Store and developers can stop getting robbed by Apple The Nintendo Switch 2 launched this past week and is apparently the best-selling console of all time at launch PS5 controllers to support multiple Bluetooth connections Tips and Picks Tip of the week: Share Feature, image crunching App pick of the week: Dia Browser RunAs Radio this week: The Case for Telemetry with Liz Fong-Jones Brown liquor pick of the week: Glenlossie 26 Hosts: Leo Laporte, Paul Thurrott, and Richard Campbell Download or subscribe to Windows Weekly at https://twit.tv/shows/windows-weekly Check out Paul's blog at thurrott.com The Windows Weekly theme music is courtesy of Carl Franklin. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: uscloud.com 1password.com/windowsweekly

Episode 247: What if customers achieve real results—but don't know it? Most vendors sell functionality. Mari Cross wants customers to see impact—in their own numbers, in real time. Mari Cross, Chief Customer Officer at Infor, is dismantling a common illusion: that delivering software features equals delivering value. Infor sells enterprise resource planning (ERP) tools, but Mari's focus is on proving business outcomes. She built a system where customers define the results that matter, track them through the product itself, and act on them with confidence. Her team isn't there to rescue implementations. They're there to make value obvious—and to ensure it keeps showing up. Most ERP systems operate like black boxes. Even when customers get results, they can't always prove it. Mari attacks that gap.  Infor's value mapping begins before the deal closes. Once the system is live, telemetry and process mining show what's working and where clients are drifting off course. This isn't a side program—it's baked into the product and reflected back to users in dashboards, metrics, and business KPIs. The shift isn't just operational. It's cultural. Mari rebuilt Infor's customer success team to be proactive, industry-specific, and integrated from day one. That means fewer rescue missions, fewer slide decks, and more conversations grounded in actual product usage and outcome data. And it means the customer success journey starts well before go-live—and runs all the way through renewal. “A good value conversation is if you have some measures in place that are more repeatable than having a value engineer fly in from left field,” Mari says. Learn how Infor's CareFor Success program gives customer success teams the tools, visibility, and data to show what's working and where to go next. And learn how and why value delivered is value clients understand. Guest: Mari Cross, Chief Customer Officer at Infor Host: Rob Markey, Partner, Bain & Company Give Us Feedback: Help us improve the podcast (feedback link) Want to get in touch? Send a note to host Rob Markey. Key Topics Covered: (01:00) The value void: what clients miss—and what it costs (03:30) Why Infor embeds value mapping into the sales process (06:10) Telemetry, process mining, and outcome tracking (11:45) The difference industry specificity makes (14:50) Mari's CareFor Success program explained (17:30) Getting sales, success, and product aligned (22:15) Making value visible across the customer lifecycle (25:00) How to track value realization in real time (36:00) Culture change and customer empathy Notable Quotes: [05:00] “If someone wanted to stick completely to standard, they could flip the switch on Day 1 and use our product. That's very different than the approach, I think, some other vendors take.” [10:00] “In the vision of, ‘We succeed when our customers succeed,' the [chief customer officer] role [at Infor] was really pivoted to make sure to focus on ongoing value realization and optimization after the go-live date. That is probably a very unique orientation for Infor.”  [12:00] “We are very focused on this idea of value engagement. We launched CareFor Success, which is our success program, last year. But it's completing this value-based customer journey all the way through where we are on a regular basis, across all teams, and repeatedly driving value with our customers by helping them look at the data, optimize, and then that visibility into value delivered within the product.” [29:00] “We want to be in sync with our strategy when we talk about success motions, because that alone is an incredible power. We can become proactive.”