Podcasts about deploy

SUMMARY: As tools like Mythos create new AI-cybersecurity concerns, CIOs and CISOs need to be prepared for two challenges: Security Remediation and Patch to Production. SHOW: 1037SHOW TRANSCRIPT: The Enterprise AI Show #1037 TranscriptSHOW VIDEO: https://youtu.be/H5KxoiEIfUoSHOW SPONSORS:Nasuni - Activate your data for AI and request a demoOutShift by Cisco - “Scaling Out Superintelligence”  The Internet of Cognition architectureShareGate - ShareGate Protect. Microsoft 365 Governance, we got this!SHOW NOTES:Project Lightwell (Red Hat and IBM)Athena (Chainguard)Anthropic Project GlasswingOpenAI GPT 5.5-CyberTHESIS: Major initiatives are forming to help enterprise organizations combat security vulnerability threats found or created using new AI-cyber tools such as Anthropic Mythos. What are the key considerations, and what additional steps do organizations need to take to be advantaged by these capabilities? Part 1The Breaking Point and the Mythos MomentThe scope of open source security and supportPatches, disclosures and upstream open sourceClearinghouses, EOs, Laws and CommunitiesRemediation - Build vs. BuyPart 2How fast can you get from Patch to Production?Mitigation before patchingFast path and stable patch pipelines?Automation in patching vs. automation in deploymentFEEDBACK?Email: show @ the enterprise ai show dot comeBluesky: @TheEntAIShow.bsky.socialTwitter/X: @TheEntAIShowInstagram: @TheEntAIShow

Cloe Axelson, a senior editor at WBUR, was feeling like the essays she produced that were written by listeners weren't sounding conversational enough -- until she deployed this one simple trick. It's a trick any producer could use to help narrators sound more like themselves.

The requirements to be a coach these days in the business world is such a joke. And it's only going to get worse.   In this episode, we break down 3 Mistakes Coaches are making in their business and brand that is going to ruin their reputation long term.   We also give a solution for each mistake that you can implement immediately.   The question you should be thinking about is: What are you willing to tolerate and not tolerate in your coaching business   Make sure you have your note pads or apps out and listen to the full episode.   Keep taking action, pursuing personal excellence, and impacting lives!   In This Episode, we discuss: 3 Mistakes to Avoid and Solutions Why Giving Generic Advice Sucks You Are Either in The Game or Not   Listen Now On: Apple Podcasts: https://podcasts.apple.com/us/podcast/live-a-dynamic-lifestyle-podcast/id1118271108 Spotify: https://open.spotify.com/show/19EcFKHAc82c2Cqc6PGrWW   Follow Us: Instagram: https://www.instagram.com/chrisandericmartinez/ YouTube: https://www.youtube.com/user/Dynamicduotraining Website: https://www.liveadynamiclifestyle.com/     Attention Nutrition & Fitness Coaches: "Join our Free Dynamic Fit Pros Community Skool Group Where we help you Discover, Develop, & Deploy your skills, gifts, and greatness to help others."  See HERE   Attention Nutrition & Fitness Coaches: "Enrollment is Open for our Accelerator Mentorship to build a 6-Figure Online Fitness Coaching Business"  See HERE     See the full Show Notes to this episode here: https://www.liveadynamiclifestyle.com/podcast/the-bar-for-coaching-is-embarrassingly-low/  

PHP Podcast – June 11, 2026 Guest Hosts: Sara Golemon, Elizabeth Barron & Holly Schilling Eric and John are out this week — Sara, Elizabeth, and Holly take over. Here’s what they covered: PHPVerse Recap PHPVerse just wrapped up, and Elizabeth was there in Amsterdam. The format is unusual — all speakers are flown to one location, but the audience is entirely virtual. It was a class act: professional TV crew, studio lighting, and a makeup and hair team on site. Around 2,500–3,000 people watched the live stream. Everything was broadcast as one long block; individual talk segments and possibly the documentary trailer will be cut and released separately. The full stream is available now — the PHP documentary trailer (produced by Jet Breeze, covering 30+ years of PHP history) appears around the 2:24:30 mark. PHP Foundation 2026 Strategy Document Elizabeth and the PHP Foundation released their 2026 strategy document the same day as this recording. The foundation gathered community input across numerous conversations and conferences, synthesized it into findings, and has now published a plan for the rest of the year. Key themes: repositioning PHP’s public perception (which Elizabeth calls a solvable problem), creating six special interest groups, and launching an Onboarding Initiative to build a real on-ramp for new PHP developers. Elizabeth’s view is that the two things giving her the most hope for PHP’s future are the passion and expertise of the community, and how good the language itself has gotten. Visit thephp.foundation to read the full document. The Onboarding Initiative One of the six special interest groups the foundation is launching is specifically focused on bringing new developers into PHP. Goals include creating a true learning path (not just a reference manual that assumes existing knowledge), improving educational resources, and potentially working with the php.net website to improve the first-time experience. Holly made the point that PHP’s barrier to entry is genuinely lower than almost any other language — the Hello World program is 11 characters — but that story isn’t being told outside the PHP bubble. New developers are turning to JavaScript as a first language and running into minified spaghetti instead of something approachable. AI Writing PHP — And PHP as a Second Language Holly built the entire PHP Tek conference app backend in Laravel without writing a single line of code herself — AI-generated throughout, which she reviewed and approved. The code held up to peer review at the conference with only minor style nits. She ran it on PHP 8.3 and used modern standards throughout (one piece of feedback: stop using empty()). The consensus: AI models write good modern PHP because of the vast amount of open source PHP they were trained on. The caveat Sara raised is worth thinking about — how much of that training data is PHP 4-era code and WordPress 3 repositories? Either way, Holly’s case for PHP as a second language is strong: low ceremony, low boilerplate, readable syntax, and it’s a language where you can do something useful in minutes. PHP’s Reputation Problem (and Why It’s Fixable) The group dug into PHP’s perception gap — the mismatch between how good the language actually is and how it’s perceived outside the community. Holly’s experience as a mobile developer who recommends PHP to others: the pushback is immediate (“isn’t that slow?”, “isn’t that dead?”). The benchmarks don’t support that reputation — PHP outperforms Python on most comparable workloads — but data alone doesn’t shift perception. Elizabeth’s point is that this is primarily a storytelling and coordination problem, not a language problem, and that the foundation’s repositioning work is exactly aimed at closing that gap. The community has the passion. It just needs to tell the story outside its own bubble. PHP Polling API RFC Sara walked through the RFC for a new Polling API in PHP (wiki.php.net/rfc/poll_API). The short version: PHP currently has five or six different ways to do I/O multiplexing (watching multiple streams and acting on whichever one is ready first), and which one works depends on the OS, available extensions, and PHP version. The Polling API proposal creates a single, unified interface that abstracts all of that. The immediate beneficiaries are async frameworks like Amp PHP, ReactPHP, and Revolt, which currently have to maintain multiple backend implementations to cover different environments. The bigger picture: this is a building block on the path toward true async PHP, likely contributing to something more complete in PHP 9.0. Most app developers won’t use it directly — but the libraries they depend on will. RFCs are all listed at wiki.php.net/rfc. PHP.net: Do As We Say, Not As We Do Sara, who has contributed to php.net, copped to the state of the codebase: some of it dates to the PHP 3 era, there are functions.inc files, and it is very much “do as we say, not as we do.” The historical reason is that php.net used to rely on community-administered mirrors (r-synced servers running everything from PHP 5.1 to 5.6 simultaneously), so modernizing the code was impossible without controlling the runtime. That’s changed with CDN-based load balancing — they can now control what PHP version runs on php.net — and the code has been getting better. But it’s a slow process. PHP Podcasts Past, Present, and Future Holly asked about the PHP Town Hall podcast (Ben Edmonds and Phil Sturgeon), and the group did a quick tour of PHP podcast history. The PHP Roundtable — originally started by Sammy, taken over by Eric — has produced about three episodes. Sara and producer Joe are planning to take it off Eric’s hands and actually do it properly. And Elizabeth announced that the PHP Foundation is launching a new podcast: tentatively called PHP at Scale, hosted by Ben Marx, focused on telling the stories of organizations pushing PHP to its limits. No launch date yet, but there’s already a queue of interested guests. Next Week’s Show — Moved to Wednesday Sara will be on a boat off the coast of Galicia on Thursday, so next week’s episode is moving to Wednesday. Guests will include Paul Reinheimer and (hopefully) Sean Coase — two veterans from PHP’s podcasting past. Elizabeth is going to try to make it work around the Canadian Grand Prix. Mac Mini M4 for Local LLMs Holly picked up a refurbished Mac Mini M4 (16GB RAM, 512GB storage) specifically to run LLM models locally via Ollama. Apple Silicon is a solid choice for this because the unified memory architecture gives the neural cores access to far more RAM than a discrete GPU setup. Sara is waiting for the M5, which is reportedly not coming until fall — and is already resigned to spending too much on it when it lands. Links from the show: PHP Foundation — 2026 Strategy Document PHP RFC: Polling API PHP RFC Wiki — All RFCs Under Discussion Amp PHP — Async framework ReactPHP — Event-driven async PHP Revolt — Event loop for PHP php.net website source code (github.com/php/web-php) PHP Architect Discord Guest Hosts: Sara Golemon Based in Lisbon, Portugal PHP core contributor; code contributor via the Curl project (which means she technically has code on Mars) Elizabeth Barron Executive Director, PHP Foundation Based in Germany Holly Schilling Primary mobile developer; built the PHP Tek 2026 conference app Based near Chicago, IL Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ PHPScore Put Your Technical Debt on Autopay with PHPScore Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Note: Next week’s show is on Wednesday (not Thursday) with guests Paul Reinheimer and Sean Coase. Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.06.11 appeared first on PHP Architect.

The Smart 7 is an award winning daily podcast, in association with METRO, that gives you everything you need to know in 7 minutes, at 7am, 7 days a week…With over 20 million downloads and consistently charting, including as No. 1 News Podcast on Spotify, we're a trusted source for people every day and we've won Gold at the Signal International Podcast awardsIf you're enjoying it, please follow, share, or even post a review, it all helps... Today's episode includes the following:https://x.com/ITVNewsPolitics/status/2064678270143005176/video/1 https://x.com/PoliticsJOE_UK/status/2064725165976551793/video/1 https://x.com/Acyn/status/2064743024551477740/video/1 https://x.com/clashreport/status/2064715693623288242/video/1 https://x.com/nexta_tv/status/2064643358346084419/video/1 https://x.com/AJENews/status/2064735145031078046/video/1https://x.com/SkySportsNews/status/2064433138592354799/video/1 https://x.com/i/status/2064701784338407469https://x.com/DiscussingFilm/status/2064696096819925023/video/1 Contact us over @TheSmart7pod or visit www.thesmart7.com or find out more at www.metro.co.uk Voiced by Jamie East, using AI, written by Liam Thompson, researched by Lucie Lewis and produced by Daft Doris. Hosted on Acast. See acast.com/privacy for more information.

Peter Huessy discusses US plans to deploy nuclear-capable F-35s in Europe to counter Russian threats. He explains Russia's "escalate to win" doctrine involving low-yield battlefield nukes for "surgical" strikes. Huessy warns that Russiapossesses thousands of non-strategic weapons, far exceeding current NATO theater capabilities and its lack of transparent weaponry numbers. (15)1953 ATOMIC CANNON

Debt is not automatically dangerous. Used correctly, it can become leverage. In this episode of The Level Up Podcast, Paul Alex breaks down the difference between bad debt that traps you and strategic debt that helps you scale faster. Let's be real… Borrowing money to buy liabilities is dangerous. But borrowing money to acquire assets… Fund growth… Deploy infrastructure… Or generate recurring revenue… That can become a powerful business weapon. In this episode, you'll learn: Why consumer debt and business leverage are not the same thing How strategic capital can accelerate growth Why waiting to scale only with cash can slow your expansion How to use borrowed money responsibly to create returns The truth is simple: Debt is not the enemy. Bad math is. If you borrow money with no plan… No return… No system… And no discipline… You are building a trap. But if you understand the numbers… Deploy capital into assets… And generate returns that outperform the cost of borrowing… You are using leverage like a real operator. Most people fear debt because they do not understand it. High-level entrepreneurs learn how to command capital. They use it to buy speed. They use it to expand faster. They use it to build assets that pay them back. Stop being afraid of money. Learn the math. Use leverage wisely. And keep leveling up. Your Network is your NETWORTH! Make sure to add me on all SOCIAL MEDIA PLATFORMS: Instagram: https://jo.my/paulalex2024Facebook: https://jo.my/fbpaulalex2024YouTube: https://www.youtube.com/channel/UCGhDAD1JyGGzSQUPD9lc9HQLinkedIn: https://jo.my/inpaulalex2024 Looking for a secondary source of income or want to become an entrepreneur? Check out one of my companies below to see if we can help you: www.CashSwipe.com FREE Copy of my book “Blue to Digital Gold - The New American Dream”www.officialPaulAlex.com Learn more about your ad choices. Visit megaphone.fm/adchoices

In this Community Roundtable, Chris Lopez sits down with PassivePockets members Pascal Wagner, Adam Cranmer, and Christy Burakovsky for a candid investor-to-investor conversation on how they're allocating capital right now and what would make them change course. Pascal frames the dilemma many LPs are feeling: with risk-free rates near 5% and major macro signals flashing red (record debt loads, expensive public markets, and uncertainty around where rates settle), does it still make sense to allocate to interest-rate-sensitive commercial real estate? He shares how he's thinking about portfolio construction with fresh liquidity and why he's prioritizing stable income and downside protection before chasing upside. Adam and Christy offer counterweights: where fear can create opportunity, why liquidity matters, and how they're approaching “safer” yield today (short-duration debt funds, notes, treasuries) while keeping dry powder for dislocated assets. The conversation also explores where each of them sees asymmetric opportunity: distressed commercial, non-performing loan strategies, medical office, assisted living tailwinds, and long-term fixed-rate debt structures that avoid the five-to-seven-year refinance trap. Key Takeaways Why some LPs are pausing syndication allocations and leaning into cash/T-bills and what would change their mind The “income-first” portfolio approach: build stable cash flow, then take higher-upside bets Where investors are hunting opportunity: distress, NPLs, office dislocation, medical office, and long-term fixed-rate debt plays Why HUD-style long-term amortizing debt can change the risk profile of a deal dramatically Mezz vs. leveraged first-lien funds: the real differentiator is control of the underlying collateral The underrated skill in 2026: staying liquid enough to act when the “no-brainer” window opens Disclaimer The content of this podcast is for informational purposes only. All host and participant opinions are their own. Investment in any asset, real estate included, involves risk, so use your best judgment and consult with qualified advisors before investing. You should only risk capital you can afford to lose. Past performance is not indicative of future results. This podcast may contain paid advertisements or other promotional materials for real estate investment advisers, investment funds, and investment opportunities, which should not be interpreted as a recommendation, endorsement, or testimonial by PassivePockets, LLC or any of its affiliates. Viewers must conduct their own due diligence and consider their own financial situations before engaging with any advertised offerings, products, or services. PassivePockets, LLC disclaims all liability for direct, indirect, consequential, or other damages arising out of reliance on information and advertisements presented in this podcast.

People are either Contaminating or Contributing to your life and vision.   In this episode, we break down how to cut the dead weight of people, negativity, and gossip and get locked in.   Make sure you have your note pads or apps out and listen to the full episode.   Keep taking action, pursuing personal excellence, and impacting lives!   In This Episode, we discuss: Signs of people's behavior that are toxic and need to be removed Why you get what you tolerate in life and business In order to grow and reach new level you will have to cut ties with people   Listen Now On: Apple Podcasts: https://podcasts.apple.com/us/podcast/live-a-dynamic-lifestyle-podcast/id1118271108 Spotify: https://open.spotify.com/show/19EcFKHAc82c2Cqc6PGrWW   Follow Us: Instagram: https://www.instagram.com/chrisandericmartinez/ YouTube: https://www.youtube.com/user/Dynamicduotraining Website: https://www.liveadynamiclifestyle.com/     Attention Nutrition & Fitness Coaches: "Join our Free Dynamic Fit Pros Community Skool Group Where we help you Discover, Develop, & Deploy your skills, gifts, and greatness to help others."  See HERE   Attention Nutrition & Fitness Coaches: "Enrollment is Open for our Accelerator Mentorship to build a 6-Figure Online Fitness Coaching Business"  See HERE     See the full Show Notes to this episode here: https://www.liveadynamiclifestyle.com/podcast/how-to-cut-the-dead-weight-and-get-locked-in/

Free is not always free. Sometimes it costs you the most valuable asset you have. In this episode of The Level Up Podcast, Paul Alex breaks down why trying to do everything yourself just to save money can actually keep you broke. Let's be real… If you spend five hours trying to fix a problem just to save fifty dollars… You are valuing your time at ten dollars an hour. And if you are the CEO… That math does not work. In this episode, you'll learn: Why doing everything yourself can become a massive liability How low-level tasks steal time from high-value revenue work Why hiring experts is often cheaper than wasting your own hours How to buy back your time and focus on the vision The truth is simple: Your job is not to save every penny. Your job is to build wealth. That means knowing when to delegate. Knowing when to hire. Knowing when to pay for speed. And knowing when your time is too valuable for the task in front of you. Too many founders stay stuck trying to save money… While losing the hours they need to actually scale. Free can be expensive. Cheap can be slow. And doing it yourself can become the biggest bottleneck in your business. Protect your time. Deploy your capital. Hire the experts. And keep leveling up. Your Network is your NETWORTH! Make sure to add me on all SOCIAL MEDIA PLATFORMS: Instagram: https://jo.my/paulalex2024 Facebook: https://jo.my/fbpaulalex2024 YouTube: https://www.youtube.com/channel/UCGhDAD1JyGGzSQUPD9lc9HQ LinkedIn: https://jo.my/inpaulalex2024 Looking for a secondary source of income or want to become an entrepreneur? Check out one of my companies below to see if we can help you: www.CashSwipe.com FREE Copy of my book “Blue to Digital Gold - The New American Dream”www.officialPaulAlex.com Learn more about your ad choices. Visit megaphone.fm/adchoices

PHP Podcast – June 4, 2026 Hosts: Eric Van Johnson & John Congdon Another fun episode of the PHP Podcast! Here’s what we covered: PHP Tek 2027 — New Dates, Bold New Format Mark your calendars: PHP Tek 2027 is happening April 27–29 in Chicago, and Eric and John are shaking things up. Rather than a straight three-day PHP conference, next year gets three tracks — two of which are familiar PHP-focused content, and a third specialty track that rotates each day: one day of JavaScript, one day of DevOps, and one day of Laravel. The Laravel track is specifically focused on how developers actually use the framework day-to-day, not a product pitch. Single-day passes will be available, so if you’re only coming for the DevOps or JS day, you’re covered. One important heads-up: there’s a big convention happening at a venue nearby in Rosemont, so the hotel block could sell out faster than usual. When they open reservations, don’t wait. Holly the Elephant Is Going Fast The PHP Architect conference elephant, named Holly, is now available at store.phparch.com, and demand has been remarkable. Eric woke up one morning to a flood of orders and genuinely couldn’t figure out what happened. The warning from last year applies here: people said they’d grab Tony later, and now Tony is gone forever. Holly ships June 17th for most orders, but if you’ve already ordered, it’s likely on its way. Get yours while you can. PHP Tek TV Is Doing Something Different This Year In past years, conference talk videos would get edited and uploaded weeks (or months) after the event. This year, John is doing things differently: the raw, unedited recordings are going up now, with timestamps in the description so you can jump straight to specific talks — some rooms recorded a seven-hour continuous feed and just left it running. The clean edited versions are still coming (a video editor friend in the UK is on it), but if you want to see a talk right now, the raw version is there. Audio quality varies by room, but it’s watchable. Immich — A Self-Hosted Google Photos That Actually Works John has been running Immich, a self-hosted photo management platform, in a Docker container for about a month and loves it. It does facial recognition, GPS tagging, and auto-uploads from his phone — essentially everything he cares about in Google Photos, without handing his photos to Google or Apple. He’s now planning to use it as the PHP Architect conference photo library, centralizing all the Tech photos in one browsable, shareable place. It’s fully open source, with no licensing cost, and an optional donation tier. If you’re sick of paying ever-increasing storage bills to big tech companies, this is worth a look. Ben Ramsey’s PHP Tek Homecoming Article Is Free to Read The May issue of PHP Architect magazine is now available to digital subscribers, and this month’s free article is Ben Ramsey’s piece on the PHP Tek homecoming experience. Eric reached out to Ben last minute and he delivered. If you’ve never subscribed, this is a low-barrier way to see what the magazine is like. Head to phparch.com, grab the free article, and if you like what you see, subscriptions are not expensive. John Is Resurrecting a Legacy Laravel App — With Claude’s Help John has been grinding away on a Laravel 6 app that was a passion project years ago and has now been revived as an actual client project. Using Claude to methodically baby-step through each version upgrade — starting with writing tests to establish a baseline — he’s worked up through the major Laravel versions. The turning point came when he hit the version where the old event sourcing package (Prooph) was clearly on its way out, and the decision was made to migrate to Verbs, Nuno Maduro’s Laravel-native event sourcing package. John’s now looking forward to it. He’s also accidentally been burning tokens on the company Anthropic account (not his personal account), which Eric caught live on air. They are going to talk about it after the show. Eric’s Mystery Side Project Is Almost Ready — If DNS Would Cooperate Eric teased a new side project last week and intended to reveal it this week, but he’s stuck waiting on DNS propagation. The domain was registered with DigitalOcean DNS already in use by a previous owner, so Eric moved it to Cloudflare — only to discover there may be a conflict because the previous owner was also on Cloudflare. The result: the name servers are stuck on old values. John’s live suggestion was to move it to Route 53, and Eric was immediately sold. The project is almost ready to show the world, DNS gods willing. Meta’s AI Support Bot Got Socially Engineered Eric shared a video demonstrating how someone prompt-injected Meta’s AI customer support bot into sending a verification code to an attacker-controlled email address — and then using that code to add the email to an account, enabling a full password reset and account takeover. The irony: Meta is the company behind Llama and has some of the deepest AI expertise on the planet, and they still shipped a support bot with permissions it shouldn’t have. Eric’s point was pointed: you can fire a human employee who gets social engineered, which creates accountability throughout the team. An AI has no such incentive structure. Crowbarring AI into account-modification workflows without appropriate guardrails is just asking for this. The PHP Foundation Now Publishes Board Meeting Minutes Eric discovered that the PHP Foundation has started publishing their board meeting minutes in a public GitHub repository. Nothing earth-shattering yet, but seeing who attended, what was discussed, and what decisions are being made gives the community a real window into how the foundation operates at scale. It also helps explain something Eric and John have always found interesting: why PHP stalled so hard between versions 5 and 7. There was no foundation, no financial backing, just volunteer hours. Now there’s a paid staff and governance structure — and the minutes show exactly how complex running something at PHP’s scale actually is. The PHP Foundation Has a Dedicated Security Team Now Speaking of the Foundation, it now has a dedicated security team — a sign of how seriously the supply chain attack problem has gotten. AI tools are being deployed by black hat actors to find vulnerabilities in open source projects at a scale that wasn’t possible before. PHP is not just another open source project; it underpins a massive slice of the web, and companies depend on it staying secure. Having a team specifically focused on this is the right call, even if it’s a sobering reminder of where the threat landscape is heading. Moat — Nuno’s GitHub Security Auditing Tool Nuno Maduro (of Laravel fame) quietly shipped a tool called Moat that audits your GitHub presence for security gaps. Install it globally via Brew or Composer, point it at your GitHub org, a specific repo, or even a specific branch, and it gives you a report on where your security posture could be improved. It’s read-only — it won’t change anything — and it’s explicit that it is not a security certification. Eric wants to use it to audit the PHP Architect organization’s repos, many of which haven’t been touched in years. Think of it as a fast, opinionated triage tool, not a replacement for a real security audit. Links from the show: PHP Tek 2027 — Chicago, April 27–29 PHP Architect Store — Holly the Elephant Immich — Self-Hosted Photo Management PHP Architect Magazine Verbs — Laravel Event Sourcing by Thunk Moat — GitHub Security Auditing by Nuno Maduro PHP Foundation on GitHub PHP Architect Discord Host: Eric Van Johnson X: @shocm Mastodon: @eric@phparch.social Bluesky: @ericvanjohnson.bsky.social PHPArch.me: @eric John Congdon X: @johncongdon Mastodon: @john@phparch.social Bluesky: @johncongdon.bsky.social PHPArch.me: @john Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ PHPScore Put Your Technical Debt on Autopay with PHPScore CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.06.04 appeared first on PHP Architect.

We Like Shooting - Ep 665 This episode of We Like Shooting is brought to you by: Foxtrot Mike (Code: WLSISLIFE) C&G Holsters (Code: WLSISLIFE) Midwest Industries (Code: WLSISLIFE) Blue Alpha Bowers Group (Code: WLS) Otis Technology (Code: WELIKESHOOTING15) Second Call Defense Text Dear WLS or Reviews +1 743 500 2171 Public   Show Titles   GOA GOALS Aug 1-2 in Iowa. https://goals.goa.org/ GunCon.net Tickets on sale now. Use code AGENCY171 GEAR CHAT (Nick) Nick's Dumb 6.5 Creedmoor Nick's Dumb 6.5 Creedmoor DERYA RELEASES THE RAN AND RAN Derya RAN and RAN-X Series Lever-Action Rifles Derya announced the official launch of its RAN and RAN-X lever-action series, featuring modernized designs with factory-integrated aftermarket upgrades including threaded barrels, M-LOK forends, and adjustable stocks. Available in .357 Magnum, .44 Magnum, and .45 Long Colt, the series will be showcased at GunCon 2026. Derya has launched the RAN full-size and RAN-X compact pistol lever-action series in .357 Magnum, .44 Magnum, and .45 Long Colt. The rifles feature a mono-block steel receiver, threaded suppressor-ready barrel, M-LOK compatible forend with Picatinny rail, fixed front and adjustable rear sights with optics rail, and rebounding hammer. The RAN offers wood or patented adjustable aluminum Ironwolf stock options while the RAN-X uses a 12″ barrel with Steelfang PSB Ironwolf grip system at 22.95″ overall length. BULLET POINTS SOLDIERSYSTEMS Roni Nano Roni Pistol-to-Carbine Conversion Kit Houston, TX – Roni Corporaton, the leading designer and manufacturer of the renown Micro-Roni, PDW-style pistol-to-carbine conversion kits and other fi … The Nano Roni is Roni's most compact pistol-to-carbine conversion kit that installs a handgun into a chassis in seconds without tools, transforming it into a pistol-braced PDW. It includes a complete system with chassis plus accessories such as magazine holders, light mounts, Picatinny rails, charging handles, optics mounts, slings, and a belt holster. Initial compatibility covers multiple Glock models with additional Glock, SIG Sauer, Taurus, and Canik models planned; available in black, OD Green, and Flat Dark Earth. THE TRUTH ABOUT GUNS Can You Shoot 5.56 Through a .22 Suppressor? – The Truth About Guns Can you shoot 5.56 through a .22 suppressor? Usually no. Here's why pressure, heat, and gas volume matter so much. The article addresses whether .556/.223 ammunition can be safely fired through a standard .22LR (rimfire) suppressor. In the general case, it is not safe or recommended. Most dedicated rimfire suppressors are engineered only for the much lower pressures, smaller gas volumes, and reduced heat produced by .22LR, .22WMR, or similar rimfire cartridges. NSSF NSSF Releases Most Recent Firearm Production Figures (ATF AFMER 2023) Over 32 million Modern Sporting Rifles in Circulation WASHINGTON, D.C. — NSSF®, The Firearm Industry Trade Association, released the Firearm Production in the United States including the Firearm Import and Export Data 2025 Edition (reporting 2023 data) to its members. The report compiles the most up-to-date information based on data sourced from the Bureau of Alcohol, […] According to the NSSF article dated January 15, 2026, ATF AFMER data shows 2023 U.S. domestic firearm production at 8,466,729 units, a 15.4% decrease from 2022. Total firearms made available for the U.S. market in 2023 were 13,574,653 (handguns 8,176,535; rifles 3,899,907; shotguns 1,498,211). Cumulative civilian firearms in possession 1990–2023 reached 506.1 million, with modern sporting rifles (MSRs) in circulation estimated at over 32 million. GUN FIGHTS Play the best Price Is Right-style GunBroker game on the internet. BANGRANK A live cast ranking segment for anything and everything in the gun world, powered by questionable certainty, strong opinions, and audience voting. THE AGENCY BRIEF Agency Update 1. AGENCY BRIEF: RUBY RIDGEWhat Ruby Ridge really was: a federal pressure campaign over a minor, technical gun charge that turned into a botched siege, unconstitutional rules of engagement, and the killing of a mother and her child. The setup started in 1989. The ATF wanted an informant inside Aryan Nations circles in northern Idaho. They targeted Randy Weaver, an Army veteran living off-grid with his family. Weaver had racist beliefs and associations, but constitutional limits matter most when the person in the government's sights is unpopular. The ATF used an informant to cultivate Weaver and buy two shotguns. The agency claimed the barrels were cut a fraction of an inch below the 18-inch legal minimum. Whether Weaver cut them at the informant's request or sold them as-is is heavily disputed. What is confirmed is what happened next: the ATF did not arrest him to protect the public. They used the federal firearms charge as leverage to pressure Weaver into becoming a paid snitch. Weaver refused. Because he refused, the ATF pushed the case to prosecutors, and Weaver was indicted in late 1990. Then came the bureaucratic failure. Weaver's court-appointed attorney was sent a notice with the wrong appearance date, and Weaver missed his hearing. Instead of resolving a government paperwork error cleanly, the system escalated. The U.S. Marshals launched an 18-month surveillance operation on his remote cabin. In August 1992, an armed reconnaissance team of Marshals encountered Weaver's 14-year-old son Sammy and family friend Kevin Harris in the woods. A firefight erupted. Exactly who fired first remains disputed, but the results are not: the family dog was killed, Sammy Weaver was shot and killed while running back toward the cabin, and Deputy U.S. Marshal William Degan was killed. The FBI's Hostage Rescue Team was called in to take over. Instead of containment, the FBI adopted modified, unconstitutional rules of engagement. In plain English, agents were told they “could and should” shoot any armed adult male seen outside the cabin. FBI sniper Lon Horiuchi fired two shots. The first wounded Randy Weaver. The second shot, fired as Weaver and Harris retreated, passed through the cabin door and hit Vicki Weaver in the head while she stood in the doorway holding her 10-month-old infant. She died instantly. The legal aftermath demolished the government's narrative: A federal jury acquitted Kevin Harris of murder on self-defense grounds. Randy Weaver was acquitted of all original firearms and murder charges, convicted only of failure to appear and a bail condition violation. A 1995 Department of Justice review found the FBI's modified rules of engagement unconstitutional. The federal government paid over $3 million in civil settlements to the surviving family. Despite Senate hearings and state-level indictments, no federal agent ever served a day in prison for the killings. 2. WHY IT MATTERS Ruby Ridge is the ultimate case study in how federal agencies use technical firearms violations to manufacture leverage, and what happens when their targets refuse to bend. This operation was never about public safety. It was about coercion. When Weaver wouldn't play ball, the agency's objective shifted from investigation to punishment, kicking off a predictable escalation ladder: Use a regulatory charge as a trap. Demand intelligence cooperation, and turn refusal into a target on the citizen's back. Treat a procedural court-date mistake as a fugitive manhunt. Deploy paramilitary recon teams for a paperwork warrant. Rewrite deadly force rules on the fly to authorize a shoot-on-sight posture. Once federal agencies invest that much time, manpower, and ego, the institutional pressure to justify the operation takes over. They stop seeing citizens with rights, and start treating them as enemy combatants on American soil. 3. THE 2A ANGLE For gun owners, Ruby Ridge is the blood-soaked warning label on every “it's just a paperwork violation” argument. The underlying charge was a National Firearms Act measurement. That is the exact kind of regulatory trap Washington loves to describe as narrow, reasonable, and harmless. But in practice, technical gun laws give agencies the legal cover to ruin lives. That is the modern lesson for FFLs navigating zero-tolerance revocations, home builders facing shifting administrative definitions, and ordinary owners one bad pistol-brace ruling away from becoming a federal case file. Apply the Supreme Court's Bruen standard to the government's actions. There is zero text, history, or tradition from the founding era of a permanent federal bureaucracy measuring the barrels of defensive weapons to coerce citizens into acting as informants, and then militarizing a warrant service when the citizen refuses. The Founders would not recognize a system that turns a man into a felon over a quarter-inch of steel. Heller proved that the Second Amendment protects an individual right. But rights on paper mean nothing if the enforcement state can use a minor regulatory allegation to justify surveillance, coercion, and deadly force. The strongest takeaway from Ruby Ridge is that when the federal government wields broad, discretionary power over firearms, abuse is not a glitch. It is the natural result. When agencies can turn a fractional barrel measurement into a capital siege, the process itself becomes the punishment. Being technically compliant doesn't protect you; it just makes you useful until you aren't anymore. GOING BALLISTIC AMMOLAND SHOOTING SPORTS NEWS(Savage) NRA, FPC, SAF v. Maryland (SB 334 Glock-Style Handgun Ban) NRA, FPC, and SAF filed a federal lawsuit challenging Maryland's SB 334, arguing the state's Glock-style handgun ban violates the Second Amendment. The National Rifle Association, Firearms Policy Coalition,...

The Midwest: 140 million acres of corn and soybeans, rural economies slowly dying, a system with no real long-term future in terms of soil or human health. It's also where roughly 25% of farmland could flip the entire region toward regeneration—but only if you coordinate capital the right way.Ivana Gazibara, Director of Systemic Investment Programmes at the TransCap Initiative, spent two years mapping the intervention points needed to drive systemic change across the agricultural heartland. She uncovered something unexpected: money isn't the problem. Coordination is. Venture capital, public funders, and philanthropists all allocate capital into regenerative agriculture—but almost never in the same room together, much less actively collaborating. The result? Capital that's supposed to be systemic lands as scattered bets.The solution: the Regenerative Agriculture Capital Orchestrator (RACO), a blueprint for deploying $1.4 billion in catalytic capital to attract $7.5 billion more, organized around four pillars—system intelligence platform, capital matchmaking, catalytic finance, and field building. This is systems change made concrete: what it costs per acre, how to move money at scale, what happens when you stop treating regeneration as a one-off problem and start treating it as a reshaping of incentives across lending, insurance, and investment. Because you can't finance a transition you haven't mapped, and you can't scale a transition money isn't deliberately coordinated to reach.More about this episode.Thoughts? Ideas? Questions? Send us a message!Find out more about our Generation-Re investment syndicate:https://gen-re.land/ Thank you to our Field Builders Circle for supporting us. Learn more hereSupport the show=======In Investing in Regenerative Agriculture and Food podcast show we talk to the pioneers in the regenerative food and agriculture space to learn more on how to put our money to work to regenerate soil, people, local communities and ecosystems while making an appropriate and fair return. Hosted by Koen van Seijen.

The 10 Trust Killers Silently Tanking Your Business Right Now...   Trust is the foundation of every successful business relationship but most entrepreneurs are unknowingly destroying it every single day.   In this episode, we break down the 10 most common mistakes that quietly erode customer trust, and what you can do right now to fix them before they cost you even more.   Make sure you have your note pads or apps out and listen to the full episode.   Keep taking action, pursuing personal excellence, and impacting lives!   In This Episode, we discuss: The hidden communication gaps killing your brand/company Why your experience and story are the keys to trust How to recover trust once it's broken    10 Ways to Build More Trust: Sell people on the truth. Be honest. Be more transparent and bold. Be real about what it actually takes to see results instead of making gimmicky claims that attract little more than lazy, entitled clients. Meet people where they are at. What would you recommend? Step by step Obsess over your clients, not the competition. Focus on what you can do to improve your clients' results. Talk about your values, morals and beliefs Your Why & Mission Show more empathy & compassion     10. More testimonials, results from clients      Bonus: Talk more about your level of experience and how many people you have worked with. If not much experience, use conviction   Listen Now On: Apple Podcasts: https://podcasts.apple.com/us/podcast/live-a-dynamic-lifestyle-podcast/id1118271108 Spotify: https://open.spotify.com/show/19EcFKHAc82c2Cqc6PGrWW   Follow Us: Instagram: https://www.instagram.com/chrisandericmartinez/ YouTube: https://www.youtube.com/user/Dynamicduotraining Website: https://www.liveadynamiclifestyle.com/     Attention Nutrition & Fitness Coaches: "Join our Free Dynamic Fit Pros Community Skool Group Where we help you Discover, Develop, & Deploy your skills, gifts, and greatness to help others."  See HERE   Attention Nutrition & Fitness Coaches: "Enrollment is Open for our Accelerator Mentorship to build a 6-Figure Online Fitness Coaching Business"  See HERE     See the full Show Notes to this episode here: https://www.liveadynamiclifestyle.com/podcast/10-reasons-your-customers-dont-trust-you-and-you-dont-even-know-it/  

https://www.amazon.com/Point-Revised-Updated-30th-Anniversary/dp/052565352X/ref=sr_1_1?crid=2ZW78488HF72K&dib=eyJ2IjoiMSJ9.C2MFHtSXa9OCZOXc7hgH6aGhfNnv43xhSm1Fy-x9qa8KvEdH-aSJxu-aTlG5KT134vxYjoaW_wZnHr5fL3InD5YqVTXboVHERNtkhewwJb4rpHS2EoARko1BgSDopePbdwBYbV885f7C0A3-4gMSonW0gCLAoEtblCb2AyqFHNjR8LSU8mOb4w1XPnBIcHCpuW1GoneatZbe0kk_bn6HpWfDKvxkDNJ-8Uqzr0HCoJY.8o6kJvhHNx6CgMubgkfiTqMRu4RkeNVuvL5oygEF-yY&dib_tag=se&keywords=point+man&qid=1779037686&sprefix=point+man%2Caps%2C172&sr=8-1White Flag of Victory by Ty Braxton: https://www.amazon.com/White-Flag-Victory-Ty-Braxton/dp/B0CK3ZWYR3/ref=sr_1_2?crid=1PBK9YE1EXS7W&keywords=white+flag+of+victory&qid=1696613968&sprefix=white+flag+of+%2Caps%2C114&sr=8-2 Shop: gocharliemike.com To Donate:      Venmo: @CharlieMikeIntlDonatePaypal: charliemike.me@gmail.com For more videos: https://www.youtube.com/channel/UCO7u5mHOBX7TCaReVTwZC6w Facebook: https://www.facebook.com/charliemikeinternational Instagram: https://www.instagram.com/charliemikeintl/ Podcast Platforms we are on: Apple: https://podcasts.apple.com/us/podcast/the-breach/id1542623117?fbclid=IwAR3berLPvTkXXjoxW3dk1fPfzIyDK3TJYm5epuEPfWHcrkewr_TpV0mwJEs Spotify: https://open.spotify.com/show/3L6rL1x8J9loM7maBZXNWk?fbclid=IwAR0JEmwiV10nLMjhPQ0LJeYrYK68XggzDSN1Uo7Qzf2TzCqmXa6rMaiONxg Breaker: https://www.breaker.audio/the-breach-1?fbclid=IwAR13iwxEoDWKWyzzAhvFB4hvBDoH981E3IW3NHKL1td6HO74iY9rBmRib58 PocketCasts: https://pca.st/7ght6e4u?fbclid=IwAR2e_UvTdgCpbsOJW4ZsJloVM1ftP3OE20GRMLgW8iN4ksGUht1B0_nabh8 Anchor: https://anchor.fm/charliemikeintl?fbclid=IwAR1kAU-Oo5pZrdoK9CiaDUzN3G7HPNgiznNlUDk3WuokIhY3GWhemMQ-y1k  

PHP Podcast – May 28, 2026 Hosts: Eric Van Johnson & John Congdon Links from the show: PHP barely avoided disaster – YouTube CVE-2026-45793: Anatomy of a 14-Hour PHP Supply-Chain Near-Miss · graycoreio/github-actions-magento2 · Discussion #261 · GitHub An Update on Composer & Packagist Supply Chain Security PHP Tek: A Homecoming by Ben Ramsey Tek Roundup – Roave Speaking at PHP Tek 2026! #tech – YouTube PHP Tek is behind us, the ballroom is cleaned up, and we’re back to talk about all of it. Here’s what we covered: RIP Archie Bot After a long fight to keep him alive, Eric has officially retired Archie — the Discord bot built on OpenClaw that handled team standups, monitored PHP Architect’s Twitter/X group for join requests, and did a surprising amount of background work for the consulting team. When Anthropic shut down the OpenClaw API, Eric tried every model and service he could find to bring Archie back to form, but nothing got him all the way there. After a month of “almost working,” the call was made. He’s dead. Eric hasn’t ruled out revisiting it eventually — maybe with Claude Cowork — but for now, the bot is gone and the starting-soon link in Discord is broken because of it. Reviving a Six-Year-Old Codebase A client PHP Architect Consulting worked with from 2018 to 2021 has come back. The project — a reimagining of their app — was killed off when COVID hit and the CEO couldn’t align with the team’s vision. The last commit was six years ago. Now the client wants to bring it back, and Eric is spending the next few days analyzing what it’ll take to get it running again. Outdated packages, an old PHP version, and the general entropy of time are all on the checklist. Eric has genuine affection for this codebase — it was one of the first projects where he felt like the team was truly operating as a team, not just as an extension of him. Now it’s time to dust it off. Partner Spotlight: PHP Score → Our CVEs The PHP Score sponsor read may be getting a refresh — the folks at Artisan Build, who built PHP Score, have a new product they’re excited about: ourCVEs.com. It monitors your codebase’s Composer and NPM packages — and optionally your servers via a lightweight agent — for exposure to open CVEs, and alerts you when something needs attention. Pricing is generous: free forever for open source projects, $17/month for solo devs, $83/month for teams (or $1,000/year), with server monitoring scaling at $1 per server above 50. Ed from Artisan Build was at PHP Tek and made a strong impression. Go check it out at ourcves.com. How PHP Barely Avoided a Supply Chain Disaster Brent Roose released a 22-minute video covering a near-miss in the PHP ecosystem involving GitHub and Composer. The short version: GitHub changed their token format and briefly released it before Composer was ready to handle it. Composer was logging the token when the format check failed — meaning GitHub tokens were ending up in CI logs. In GitHub Actions, depending on how your action is configured, that container (and its token) might stick around for a while, giving an attacker a window to act. An alert developer caught the issue, used Claude to help research it, then did responsible disclosure — contacting the Composer maintainers and reaching out to Taylor Otwell, Vincent Pontier, and others in the ecosystem to disable their actions until the fix was in place. Update your Composer. GitHub rolled back the new token format but won’t keep it rolled back forever. Packagist MFA and Account Security Following up on the supply chain theme: Nils and Igor (Composer/Packagist maintainers) released a blog post on what they’re doing to improve supply chain security. The immediate ask for anyone publishing packages is to enable MFA on your Packagist account — it’s not required yet, but it will be. Eric went to check his own account, found MFA was already on, but noticed his username was still “diegodev” and he was using an old email. While updating it, he noted that Packagist didn’t require him to re-authenticate or confirm the change via the old email — a gap worth flagging if you have popular packages and someone ever gets into your session. PHP Tek 2026 Recap — The Good PHP Tek 2026 in Chicago is done, and despite everything (see below), the team is proud of how it went. Some highlights: Holly (CodeLorax) built a conference mobile app from scratch, released on both Google Play and the Apple App Store within 24 hours of the conference opening. The app let attendees build their own schedule, detected conflicting talk selections, sent push notifications when talks moved rooms, and even included a vendor lead-scanning feature where vendors could scan attendee QR codes to capture contacts. It was a genuine game-changer for the event. Eric and John named the conference elephant after Holly in appreciation — she also changed a trailer tire during setup, which sealed the deal. Clayton Kendall sponsored and produced the conference shirts and bags on an extremely tight timeline — shirts two weeks out, bags just one week before the event. Both were a hit. Attendees at the conference were getting questions about the rainbow PHP Architect shirt in particular. A job fair ran for the first time, with four companies represented. One hiring manager showed up even though they already had 1,400 applicants — because they knew that conference attendees are exactly the kind of motivated, self-improving developers they want. Attendees got to ask questions directly, including the real-world stuff like remote vs. office. Eric would love feedback on how to make it better next year. JS Tech debuted as a fourth track alongside the three PHP tracks, bringing in fresh faces from the JavaScript community. Eric came away energized by the cross-pollination — different people, different approaches to similar problems. Ben Ramsey and James Tickham (Rove) both wrote great blog posts about the conference. Ben’s will be featured in the magazine. Diana Pham also put together a video recap. Links in the show notes. PHP Tek 2026 Recap — The Incident On Monday during final setup, a hotel employee had a medical incident while walking through the main ballroom — leaving a trail that required hazmat-suited cleanup crews and forced the team to quarantine the ballroom, the hallway leading to it, and the adjacent bathroom. The person is okay and was back at the hotel by Friday, which was a relief. But in the moment, nobody knew what was happening or how long the room would be unavailable. The team had to rebuild the entire conference footprint overnight. The keynote moved, the JS Tech track went into the quiet room, vendors moved to the atrium, and the hotel staff — to their enormous credit — cleared their own furniture and accommodated every ask without complaint. Attendees were equally patient; once they understood the situation, there was no drama, just “tell us where to go.” The incident also took out the streaming setup for day one, compounding an already-difficult start. The solution that eventually worked — plugging the Ethernet into a hub before the streaming equipment — wasn’t tried until day three. Eric is mad at himself for thinking of it and not doing it sooner. PHP Tek 2027 — Save the Date (TBD) Planning for next year is already underway. The current target is April 2027 — away from the May timing that caused Eric to miss two of his kid’s band performances this year. Nothing is locked yet, but they’re working through venue and date options and hope to have an announcement soon. Links from the show: ourCVEs.com — Daily security audit on autopilot PHPScore — Technical debt monitoring for PHP Brent Roose — “How PHP Barely Avoided Disaster” (YouTube) Packagist — Enable MFA on your account PHP Architect Discord PHP Architect Merch Store PHP Architect YouTube Host: Eric Van Johnson X: @shocm Mastodon: @eric@phparch.social Bluesky: @ericvanjohnson.bsky.social PHPArch.me: @eric John Congdon X: @johncongdon Mastodon: @john@phparch.social Bluesky: @johncongdon.bsky.social PHPArch.me: @john Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ PHPScore Put Your Technical Debt on Autopay with PHPScore CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.05.28 appeared first on PHP Architect.

Feeling stuck, uncertain, overwhelmed, or disconnected from your purpose? In this episode of She Will Flourish, Rachel Earp introduces the Flourish Path—a faith-rooted framework for women who want to grow in confidence, discover their calling, deepen their faith, overcome self-doubt, and step into the life God created them for.What if flourishing wasn't about becoming more impressive, but becoming more aligned?In this deeply personal episode of She Will Flourish, Rachel Earp shares the heart behind what she calls the Flourish Path—a transformational journey designed to help women move from confusion, striving, fear, and hiding into confidence, clarity, emotional resilience, faith, and purpose.This episode is for the woman who feels stuck between who she is and who she feels called to become, struggles with confidence, self-doubt, comparison, or overwhelm, wants to deepen her faith while building a meaningful life, desires clarity around her calling and purpose, feels emotionally exhausted from hustle culture and striving, and is ready to stop hiding and begin flourishing.Rachel walks through the five stages of the Flourish Path: Discover, Develop, Declare, Deepen, and Deploy. Through heartfelt storytelling, practical wisdom, Biblical encouragement, and honest reflection, she shares what it means to become rooted in peace, alignment, and purpose instead of performance and pressure.This conversation feels like sitting across the table with a trusted friend reminding you that you are not behind… you are becoming.What You'll Learn in This Episode:You'll learn how to discover your gifts, voice, values, and calling, why emotional resilience and confidence matter in personal growth, the difference between striving and aligned living, how to stop hiding your gifts and begin sharing your voice, why spiritual depth and peace are foundational to flourishing, how to use your gifts in business, ministry, family, and leadership, the five stages of the Flourish Path, and why flourishing begins with rootedness instead of performance.Ready to Go Deeper?If this episode resonated with you, Flourish was created for women just like you. Flourish is a transformational space for women who want to grow in confidence, deepen their faith, clarify their calling, heal emotionally, build aligned lives, and flourish from the inside out. Join the movement at www.wewillflourish.orgFollow Rachel on Instagram @iamrachelearpFollow Flourish on Instagram @youbelonginflourishThis episode is powered by EARPware

Recorded live from a co-working space in New Jersey — couch surfing, sublet starting June 1st, figuring it out day by day — Norense opens this episode with a question that most people are too afraid to ask out loud:What do you do when God doesn't come through the way you thought He would?It started with an Instagram Live. A viewer kept asking the same question over and over: "How do I have more faith that God will get me and my girl back together?" And instead of answering on the surface, Norense went deeper — to the root of why we ask the questions we ask, and what we're really crying out for when we try to box God into the shape of our broken heart.This episode is for anyone in a season of loss — a relationship, a role, an identity — who is still trying to control how God shows up instead of trusting who He already is.In this episode:Why the question you keep asking God reveals what you've placed your identity in — and how to find it againWhat it means to box God into the shape of your broken heart — and why it leaves Him no room to be who He isHow loss — of a relationship, a role, a season — is often God's protection disguised as painWhy God has already answered your prayer — and the real question is whether you're answering His callThe power of serving in your season of need — and how giving unlocks what asking never couldWhy you don't know God like this until life forces you into a situation you've never seen beforeA personal word on surrender: losing a sister to leukemia, losing cousins, navigating a new city alone — and still trusting the processFeatured: Chandler Moore's "What I Needed" — and why the lyric "it's foolish of me to box you in the shape of my broken heart" captures everything this episode is about.Key Truth: "Deploy yourself. Don't just look for employment — deploy yourself. Because everything is working together for your good."Key Verse: John 1:1 — In the beginning was the Word, and the Word was with God, and the Word was God.MIND BULLY PODCAST:SpotifyApple PodcastsSOCIALS:@kingno_@mindbullypodcast If this episode impacted you, rate and review the podcast to help this message reach more homes and hearts.

Are you building with conviction and clarity or are you running on pride, impatience, and ego?   In this episode, we break down one of the most important distinctions in business and leadership: the difference between a Reformer and a Rebel. The side you're operating from will determine whether you build something lasting or blow it up.   3 Key Takeaways Meekness is not weakness. Reformers are submitted, coachable, and spirit-led. Rebels resist correction the moment it challenges their ego. Your fuel source is revealed under pressure, not in the highlight reel. Check what's actually driving your conviction and calling, or pride and proving people wrong. If you can't be examined, you can't be trusted with what you're trying to build. Reformers invite scrutiny. Rebels deflect it. Make sure your notepad is ready. This one hits differently. Keep taking action, pursuing personal excellence, and impacting lives!   In This Episode, We Discuss: The Reformer vs. The Rebel Two types of leaders. Two very different outcomes. Nehemiah was called to rebuild the wall of Jerusalem; he faced opposition, ridicule, and threats, and never reacted in anger. He kept building. King Saul was given a kingdom and lost it through pride, impatience, and self-will. Same pressure. Completely different response. Which one are you? The Reformer: Meek, spirit-led, purposeful, and submitted. The Rebel: Arrogant, self-willed, flesh-driven, prideful, stubborn, and impatient. Reformation is not about tearing down it's about restoration, repentance, renewal, and alignment. In business, it means aligning your work with your calling, your values, and a vision bigger than yourself.   5 Keys To Becoming a Reformer In Business Key #1  Know Your Sphere (Don't Fight Outside Your Lane) Nehemiah didn't try to reform everything he was called to one wall, one city. Rebels scatter their energy fighting battles they were never assigned to. When you work on your actual assignment, you become unstoppable.   Key #2  Meekness Is Not Weakness (Submit Before You Lead) Meekness is strength under control. Reformers are submitted to God, to mentors, to a process. Rebels are coachable until the coach challenges their ego. In business, are you building under authority or building around it?   Key #3  Check Your Fuel Source (What's Driving You?) Both reformers and rebels work hard. The difference is why. Rebel fuel is anger at the system, pride in proving people wrong, and impatience with the pace. Reformer fuel is conviction, calling, and the people they're serving.   Key #4  Patience Is a Strategy (The Long Game Wins) King Saul couldn't wait; he moved before he was supposed to and it cost him everything. Nehemiah faced 52 days of opposition and ridicule. He didn't quit. He didn't retaliate. He built. Rebels mistake urgency for anointing. Just because you feel it strongly doesn't mean it's time.   Key #5  Reformers Invite Scrutiny, Rebels Deflect It Nehemiah was transparent to the king, to the people, to God. Rebels hide from accountability, feedback, and the full picture. Do you have real financial accountability? A coach, a mastermind, a mentor who sees your actual numbers and decisions?   Follow Us: Instagram: https://www.instagram.com/chrisandericmartinez/ YouTube: https://www.youtube.com/user/Dynamicduotraining Website: https://www.liveadynamiclifestyle.com/     Attention Nutrition & Fitness Coaches: "Join our Free Dynamic Fit Pros Community Skool Group Where we help you Discover, Develop, & Deploy your skills, gifts, and greatness to help others."  See HERE   Attention Nutrition & Fitness Coaches: "Enrollment is Open for our Accelerator Mentorship to build a 6-Figure Online Fitness Coaching Business"  See HERE     See the full Show Notes to this episode here: https://www.liveadynamiclifestyle.com/podcast/the-reformer-vs-the-rebel-the-nehemiah-standard-for-business/  

What happens when a brilliant engineer or software developer builds a successful business, but realizes they don't actually know how to be a CEO? In this episode of the Leaders in Tech podcast, host David Mansilla interviews growth adviser Pete Steege to tackle the unique challenges faced by "Accidental CEOs."Pete spent decades in tech marketing before launching his own firm, B2B Clarity, right during the pandemic. Today, he shares his proprietary CMP (Clarity, Meaning, Purpose) Growth framework designed to help technical founders simplify their messaging, align their company culture, and scale intentionally.If you are tired of losing deals because your product feels "too complicated" to explain, this episode is your masterclass in marketing with meaning.

Send us Fan MailThere is a fake version of masculinity being sold to men right now.It is loud. Flashy. Ripped. Rich. Angry. Seductive. It calls itself alpha, but a lot of it is just insecurity wearing a costume.In this episode, Rory goes after counterfeit masculinity and exposes the scammers selling warrior costumes to boys who do not want to pay the price of becoming real men.Real masculinity is not body count, bank accounts, online bravado, dominance games, or peacocking for attention.Real masculinity is strength submitted to God.A real man fears God, carries responsibility, controls his appetites, protects women instead of preying on them, loves sacrificially, builds brotherhood, repents fast, and serves before he leads.In this episode, we break down:The difference between real masculinity and counterfeit masculinityWhy the manosphere attracts insecure men looking for shortcutsThe “Threat Index” of fake masculine personasWhy strength without surrender becomes dangerousHow biblical masculinity carries both strength and loveWhat it means to stop looking like a man and start becoming oneScripture of the Day1 Corinthians 16:13–14 ESV“Be watchful, stand firm in the faith, act like men, be strong. Let all that you do be done in love.”Dangerous FocusAsk yourself:What fake version of masculinity am I most tempted to follow?Name it. Expose it. Kill it.Then take one real masculine action this week: serve, repent, confess, train, lead, apologize, call a brother, or carry what you have been avoiding.Destroy your weakness. Build the man. Deploy the dangerous self.Support the showTDMP SITE: https://dangerousmanpodcast.com/NEW HERE: https://open.spotify.com/playlist/6edYYGXup6pimDwU1kGnsSGrab some DANGEROUS GEAR in our shop https://dangerousmanpodcast.com/shop/Support the show for as little as $3 a month https://www.buzzsprout.com/2080275/supporters/newFollow us on X for more shenanigans https://twitter.com/TDMPodcast603Follow us on Instagram for extra shenanigans https://www.instagram.com/thedangerousmanpodcast/Connect with Matt Fortin & Rory LawrenceEmail us at: thedangerousmanpodcast@gmail.comRemember men... Stop trying & start training!

O Antes do Deploy chegou! Depois de mais de 190 episódios do Kubicast, o primeiro e maior podcast do Kubernetes do Brasil, a Getup estreia um novo formato: conversas técnicas sobre software supply chain security com quem vive esse assunto na prática.No primeiro episódio, Camila Bedretchuk e Heitor Gouvêa conversaram sobre o que faz um pesquisador de segurança e o que esse trabalho revela sobre como as empresas ainda tratam segurança hoje.O episódio cobre:O que faz um pesquisador de segurança na prática e como esse perfil se formaA relação entre pesquisa de segurança e produtoComo times de produto podem começar a incluir segurança nas discussões do dia a diaA maturidade do mercado brasileiro em software supply chain security e o que está mudando com novas regulaçõesNosso podcast é construído com a comunidade. Se você tem um tema que quer ver discutido, conhece alguém que tem muito a contribuir ou quer aparecer por aqui para trocar uma ideia sobre software supply chain security, preencha o formulário.#Getup #Quor #AntesdoDeploy #SoftwareSupplyChainSecurity #DevOps #Kubernetes #SRE #CloudNative #CNCF #DevSecOps #Cibersegurança #Podcast O Antes do Deploy é uma produção da Getup, empresa especialista em Kubernetes e projetos open source para Kubernetes. Também somos criadores do Quor, catálogo de imagens de container com CVE próximo de zero. Os episódios estão nas principais plataformas de áudio digital e no YouTube.com/@getupcloud. 

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

Cash sitting still is not safety. It is wasted leverage. In this episode of The Level Up Podcast, Paul Alex breaks down how to use capital the right way—and why hoarding money can actually slow down your growth. Let's be real… Money is not a trophy. It is a tool. And if you are afraid to deploy it… You are leaving speed, freedom, and opportunity on the table. In this episode, you'll learn: Why cash should be treated like ammunition, not decoration How hoarding money can keep you trapped in a survival mindset Why investing in people, systems, coaching, and assets buys back your time How strategic capital deployment creates faster growth and long-term wealth The truth is simple: You cannot build an empire while being terrified to spend. At some point, you have to stop protecting the bank balance… And start using it to build the machine. Hire the expert. Buy the speed. Deploy the assets. Invest in the systems. Because the right money spent in the right places does not disappear. It multiplies. When you use capital correctly… Your business moves faster. Your time opens up. And your wealth starts working for you. Your Network is your NETWORTH! Make sure to add me on all SOCIAL MEDIA PLATFORMS: Instagram: https://jo.my/paulalex2024 Facebook: https://jo.my/fbpaulalex2024 YouTube: https://www.youtube.com/channel/UCGhDAD1JyGGzSQUPD9lc9HQ LinkedIn: https://jo.my/inpaulalex2024 Looking for a secondary source of income or want to become an entrepreneur? Check out one of my companies below to see if we can help you: www.CashSwipe.com FREE Copy of my book “Blue to Digital Gold - The New American Dream”www.officialPaulAlex.com Learn more about your ad choices. Visit megaphone.fm/adchoices

In this high-energy kickoff episode, Tyler Kamerman stands before the Clive Emerging Leaders to lay down a foundational blueprint for what it truly means to be an "Intentional Pursuer." Drawing from his own hilarious fifth-grade confessions of "diarrhea of the mouth" to a mid-life career crisis at age 43, Tyler shatters the corporate obsession with the badge of "busyness." He challenges listeners to stop hiding behind overscheduled calendars and instead look backward to their childhood playgrounds to excavate the authentic raw sparks that God uniquely hardwired into their DNA. The episode delivers a massive reality check on what pursuing your calling actually looks like, debunking the myth of the flawless career path through concepts like the 20% "Suck Factor" and the Iceberg of Success. By blending tactical strategies like the 24-Hour Pause with deep theological insights on identity, Tyler reframes passion not as a luxury item for a side hustle, but as the essential, sustainable fuel required for kingdom significance. This is a fierce, witty, and grace-filled charge to stop playing a character, build a trusted community, and confidently step into your own "Send Me" moment. Key Takeaways - Embrace the 20% Suck Factor: Even in your absolute dream job, a portion of the work will simply drain you (like Tyler's spreadsheets!). True passion doesn't eliminate the grind; it gives you the extra willpower and resilience to push through it. - Practice Playground Archaeology: To discover what makes you come alive today, use the 7/10 Rule. Look back at what you naturally loved doing between the ages of 7 and 10 before the world told you your dreams were unrealistic. - Deploy the 24-Hour Pause: Banish the "automatic yes" from your vocabulary to protect your time. Use a script to give yourself a day to evaluate whether an opportunity is a "Heck Yeah" or a "No, Thank You." - Become a "Relevant Surprise": Avoid becoming a replaceable corporate commodity by pairing your professional relevance (your career skills) with a beautiful surprise (your unique, God-given passions).   To connect with Tyler: https://www.tylerkamerman.com/

The mission's climax involved the sample capsule's return to Earth in the Utah desert. Dante Lauretta describes the harrowing moments when the drogue parachute failed to deploy as scheduled, threatening a catastrophic crash landing. The successful deployment of the main parachute at 60,000 feet ultimately secured a "mission success" and the recovery of a spectacular sample. Lauretta has since transitioned the spacecraft's ongoing mission, now called OSIRIS-APEX, to his former student Daniella DellaGiustina. He concludes by celebrating the mission's impact on training over 200 students, ensuring a legacy for future planetary exploration. (4/4)AUGUST 1961

Interview with Dimitri Sirota from BigID Most organizations think AI risk lives in the model – or the identity. It doesn't. It lives in the data. In this episode, BigID's CEO reframes the conversation: why legacy access controls are breaking down, why visibility into sensitive data is the missing foundation, and what it takes to govern humans and machines under a single, accountable framework. Segment Resources: BigID's Agent Access Management Guide BigID's podcast, CTRL + ALT + AI This Week's Topic: Cascading Breaches We're seeing more and more 3rd and 4th party attacks that chain through multiple layers of compromised tools and services. In this topic segment, we discuss the two main aspects of this trend: How we can stop the chain of breaches from a third party library, vendor, or service provider How this might get handled at the legal, contractual, and organizational levels We discuss two big recent examples: Sonicwall's 2025 breach of their cloud firewall configuration backup service The compromise of Aqua Security's widely used Trivy open source tool The Weekly Enterprise News Finally, in the enterprise security news, Funding and M&A courtesy of the Security, Funded newsletter We have evidence that attackers are leveraging AI now (this sounds like old news, but there was little to no evidence before, when people were claiming this) The Angry admin problem emerges again Vulnerability information is getting crazy to keep up with Breach information is getting crazy to keep up with You can give your Agents an allowance now - don't spend it all in one place Are vulnerabilities sparse or dense? Mythos, as a model, isn't all that special Deploy your own deception sensors! Japan made something weird. Again. All that and more, on this episode of Enterprise Security Weekly. Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://securityweekly.com/esw-459

In this powerful episode of the Live a Dynamic Lifestyle Podcast, we sit down with Dr. Alex Spinoso to unpack the real story behind building a purpose-driven life and business.    From working as an MD for the California Department of Corrections to renting out every room in his home with his wife to save money and take a leap into entrepreneurship Dr. Alex shares the sacrifices, risks, failures, and lessons that shaped his journey.   We dive into the realities of scaling too fast, grassroots marketing, leadership, urgency, discipline, and what it truly means to serve people with a "one person mindset." This conversation also goes deeper into family, faith, fulfillment, legacy, and the emotional price success can demand behind the scenes.   If you're an entrepreneur, leader, coach, or someone chasing a bigger vision for your life, this episode will challenge you to raise your standards, stay patient through the process, and focus on what truly matters before time runs out.   3 Key Takeaways: Success requires sacrifice, humility, and the willingness to endure uncomfortable seasons before breakthrough happens. Scaling fast without the right foundation can create costly lessons in leadership, systems, and sustainability. The most impactful businesses are built by obsessing over serving people at the highest level one person at a time.   Make sure your notepad is ready. This one hits differently.   Keep taking action, pursuing personal excellence, and impacting lives!   In This Episode, We Discuss: Why Dr. Alex walked away from a stable medical career to pursue entrepreneurship and fulfillment The mindset, routines, and principles that helped him build Genesis into a multi-location business Lessons on faith, family, legacy, aggressive patience, and living with urgency before time runs out   Dr Alex Spinoso Bio: Dr. Alex Spinoso is a medical doctor and high-growth entrepreneur best known for scaling numerous medical and wellness businesses to 7-, 8-, and even 9-figure revenues, including co-founding Genesis Lifestyle Medicine. He also hosts The Spinoso Podcast, mentors other medical entrepreneurs, and blends his business expertise with passion projects like comic books and cars.   Follow Dr Alex Spinoso:   •      Instagram: https://www.instagram.com/dralexspinoso/ •      Website:https://dralexspinoso.com/   Follow Us: Instagram: https://www.instagram.com/chrisandericmartinez/ YouTube: https://www.youtube.com/user/Dynamicduotraining Website: https://www.liveadynamiclifestyle.com/     Attention Nutrition & Fitness Coaches: "Join our Free Dynamic Fit Pros Community Skool Group Where we help you Discover, Develop, & Deploy your skills, gifts, and greatness to help others."  See HERE   Attention Nutrition & Fitness Coaches: "Enrollment is Open for our Accelerator Mentorship to build a 6-Figure Online Fitness Coaching Business"  See HERE     See the full Show Notes to this episode here: https://www.liveadynamiclifestyle.com/podcast/the-5-success-standards-that-separate-the-elite-with-dr-alex-spinoso/

White Flag of Victory by Ty Braxton: https://www.amazon.com/White-Flag-Victory-Ty-Braxton/dp/B0CK3ZWYR3/ref=sr_1_2?crid=1PBK9YE1EXS7W&keywords=white+flag+of+victory&qid=1696613968&sprefix=white+flag+of+%2Caps%2C114&sr=8-2 Shop: gocharliemike.com To Donate:      Venmo: @CharlieMikeIntlDonatePaypal: charliemike.me@gmail.com For more videos: https://www.youtube.com/channel/UCO7u5mHOBX7TCaReVTwZC6w Facebook: https://www.facebook.com/charliemikeinternational Instagram: https://www.instagram.com/charliemikeintl/ Podcast Platforms we are on: Apple: https://podcasts.apple.com/us/podcast/the-breach/id1542623117?fbclid=IwAR3berLPvTkXXjoxW3dk1fPfzIyDK3TJYm5epuEPfWHcrkewr_TpV0mwJEs Spotify: https://open.spotify.com/show/3L6rL1x8J9loM7maBZXNWk?fbclid=IwAR0JEmwiV10nLMjhPQ0LJeYrYK68XggzDSN1Uo7Qzf2TzCqmXa6rMaiONxg Breaker: https://www.breaker.audio/the-breach-1?fbclid=IwAR13iwxEoDWKWyzzAhvFB4hvBDoH981E3IW3NHKL1td6HO74iY9rBmRib58 PocketCasts: https://pca.st/7ght6e4u?fbclid=IwAR2e_UvTdgCpbsOJW4ZsJloVM1ftP3OE20GRMLgW8iN4ksGUht1B0_nabh8 Anchor: https://anchor.fm/charliemikeintl?fbclid=IwAR1kAU-Oo5pZrdoK9CiaDUzN3G7HPNgiznNlUDk3WuokIhY3GWhemMQ-y1k 

Interview with Dimitri Sirota from BigID Most organizations think AI risk lives in the model – or the identity. It doesn't. It lives in the data. In this episode, BigID's CEO reframes the conversation: why legacy access controls are breaking down, why visibility into sensitive data is the missing foundation, and what it takes to govern humans and machines under a single, accountable framework. Segment Resources: BigID's Agent Access Management Guide BigID's podcast, CTRL + ALT + AI This Week's Topic: Cascading Breaches We're seeing more and more 3rd and 4th party attacks that chain through multiple layers of compromised tools and services. In this topic segment, we discuss the two main aspects of this trend: How we can stop the chain of breaches from a third party library, vendor, or service provider How this might get handled at the legal, contractual, and organizational levels We discuss two big recent examples: Sonicwall's 2025 breach of their cloud firewall configuration backup service The compromise of Aqua Security's widely used Trivy open source tool The Weekly Enterprise News Finally, in the enterprise security news, Funding and M&A courtesy of the Security, Funded newsletter We have evidence that attackers are leveraging AI now (this sounds like old news, but there was little to no evidence before, when people were claiming this) The Angry admin problem emerges again Vulnerability information is getting crazy to keep up with Breach information is getting crazy to keep up with You can give your Agents an allowance now - don't spend it all in one place Are vulnerabilities sparse or dense? Mythos, as a model, isn't all that special Deploy your own deception sensors! Japan made something weird. Again. All that and more, on this episode of Enterprise Security Weekly. Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://securityweekly.com/esw-459

Interview with Dimitri Sirota from BigID Most organizations think AI risk lives in the model – or the identity. It doesn't. It lives in the data. In this episode, BigID's CEO reframes the conversation: why legacy access controls are breaking down, why visibility into sensitive data is the missing foundation, and what it takes to govern humans and machines under a single, accountable framework. Segment Resources: BigID's Agent Access Management Guide BigID's podcast, CTRL + ALT + AI This Week's Topic: Cascading Breaches We're seeing more and more 3rd and 4th party attacks that chain through multiple layers of compromised tools and services. In this topic segment, we discuss the two main aspects of this trend: How we can stop the chain of breaches from a third party library, vendor, or service provider How this might get handled at the legal, contractual, and organizational levels We discuss two big recent examples: Sonicwall's 2025 breach of their cloud firewall configuration backup service The compromise of Aqua Security's widely used Trivy open source tool The Weekly Enterprise News Finally, in the enterprise security news, Funding and M&A courtesy of the Security, Funded newsletter We have evidence that attackers are leveraging AI now (this sounds like old news, but there was little to no evidence before, when people were claiming this) The Angry admin problem emerges again Vulnerability information is getting crazy to keep up with Breach information is getting crazy to keep up with You can give your Agents an allowance now - don't spend it all in one place Are vulnerabilities sparse or dense? Mythos, as a model, isn't all that special Deploy your own deception sensors! Japan made something weird. Again. All that and more, on this episode of Enterprise Security Weekly. This segment is sponsored by BigID. Visit https://securityweekly.com/bigid to learn more about them! Show Notes: https://securityweekly.com/esw-459

Interview with Dimitri Sirota from BigID Most organizations think AI risk lives in the model – or the identity. It doesn't. It lives in the data. In this episode, BigID's CEO reframes the conversation: why legacy access controls are breaking down, why visibility into sensitive data is the missing foundation, and what it takes to govern humans and machines under a single, accountable framework. Segment Resources: BigID's Agent Access Management Guide BigID's podcast, CTRL + ALT + AI This Week's Topic: Cascading Breaches We're seeing more and more 3rd and 4th party attacks that chain through multiple layers of compromised tools and services. In this topic segment, we discuss the two main aspects of this trend: How we can stop the chain of breaches from a third party library, vendor, or service provider How this might get handled at the legal, contractual, and organizational levels We discuss two big recent examples: Sonicwall's 2025 breach of their cloud firewall configuration backup service The compromise of Aqua Security's widely used Trivy open source tool The Weekly Enterprise News Finally, in the enterprise security news, Funding and M&A courtesy of the Security, Funded newsletter We have evidence that attackers are leveraging AI now (this sounds like old news, but there was little to no evidence before, when people were claiming this) The Angry admin problem emerges again Vulnerability information is getting crazy to keep up with Breach information is getting crazy to keep up with You can give your Agents an allowance now - don't spend it all in one place Are vulnerabilities sparse or dense? Mythos, as a model, isn't all that special Deploy your own deception sensors! Japan made something weird. Again. All that and more, on this episode of Enterprise Security Weekly. Show Notes: https://securityweekly.com/esw-459

Now is the time to overcome fear, step into your purpose, and deploy your gifts to make an eternal impact for the Kingdom of God.

PHP Podcast – May 14, 2026 Hosts: Eric Van Johnson & John Congdon Another fun episode of the PHP Podcast! Here’s what we covered: PHP Tek Is Four Days Away The countdown clock is basically ticking in real time — PHP Tek 2026 in Chicago is just four days and ten hours out as this episode begins. Eric flies Friday, John flies Saturday, and the team descends on the venue Sunday to get the trailer unloaded, the booth assembled, and everything tested before the conference kicks off. The conference magazines — ordered three weeks ago and still showing “printing” on Tuesday — pulled through at the last minute and are set to arrive at the venue tomorrow. That’s cutting it close, but it counts. Win a Free PHP Tek Ticket — Live on Air John put a full conference ticket up for grabs: DM him on any social platform, and he’d draw a winner on the live stream. The caveat? You had to be watching live — audio listeners are out of luck on this one. The lucky winner drawn on air was Jeffrey Davidson, who will now be at PHP Tek. Eric offered to even bring him to the team’s Saturday minor league baseball game if he flies in early enough. Jeffrey gets a hand-printed sticker name badge, but he’ll have a badge. New PHP Architect Conference Merch Fresh shirts are coming to the PHP Tek booth courtesy of Clayton Kendall, who is producing the apparel. The new design goes with a smaller logo placement — a more subtle, wearable-anywhere look compared to the big bold prints. If you’re headed to Chicago, swing by the PHP Architect table and see what’s there. Holly’s Conference App Gets a Vendor Mode The PHP Tek attendee app built by Holly (developed by CodeLorax) has been upgraded ahead of the conference. What started as a schedule browser with conflict detection and push notifications has now merged with a vendor lead scanning tool. Attendees can log in by scanning the QR code on their badge, and vendors can scan attendee badges to capture leads — all in a privacy-preserving way that doesn’t expose raw contact data. Eric’s wife Bek figured out the app entirely on her own without being told anything, which remains one of the best usability endorsements you can give. Something Big Is Happening in the PHP Community Eric teased something he can’t officially talk about yet — a community acquisition that’s still working through the legal and DNS transfer process. A new droplet has been created. Joe has already figured out what it is. Eric is too excited not to bring it up but too responsible to spill the details before it’s official. The plan is to announce after PHP Tek. If you want to know early, apparently getting Joe drunk at the conference is your best strategy. Grok AI Exploited via Morse Code in Bank Transactions A video from the Dave’s Garage YouTube channel surfaced a genuinely unsettling AI exploit: someone used a Grok-powered AI banking agent and embedded hidden instructions inside transaction memo fields — written in Morse code. The agent decoded the dots and dashes, interpreted them as instructions, and followed them, ultimately losing somewhere between $154,000 and $200,000 in crypto transfers. This is prompt injection in its most creative and alarming form yet. The attack surface for AI agents hooked into real financial systems is not theoretical — it’s happening. TanStack Hit by NPM Supply Chain Attack The TanStack ecosystem — the popular query, router, and table libraries — was hit by a supply chain attack via GitHub Actions cache poisoning. The attack vector was a forked pull request: a malicious fork can trigger GitHub Actions workflows and potentially inject poisoned artifacts into the build cache, which then get picked up by the legitimate package. Simon Hamp from NativePHP caught it and raised the alarm in the PHP Architect Discord. It’s a good reminder that the supply chain attack surface extends well beyond just what’s in your `composer.json` or `package.json` — your CI pipeline’s caching behavior matters too. PHP Tek Job Fair — Wednesday Afternoon There will be a job fair at PHP Tek this year, scheduled for Wednesday afternoon. At least one confirmed hiring manager will be there. If you’re looking for PHP work, or if you’re a company looking for PHP talent, this is worth planning around. Eric and John both see it as a natural fit for the conference — the PHP community is tight-knit enough that a job fair actually means something. Eric’s Birthday Spa Day in Palm Springs Eric’s wife Bek surprised him with a birthday spa day in Palm Springs. It was his first massage ever, and he paired it with a mineral soak in the natural springs. He came away thoroughly convinced — the combination of the mineral water and a proper massage left him feeling better than he expected, and he’s already thinking about going back. Beck planned the whole thing, and Eric was appropriately grateful. John’s First Couples Massage John has now also had his first couples massage, and it did not go quietly. He opted for deep tissue — which means the therapist was working hard — and his wife, in the room next door, was apparently convinced something was wrong based on the sounds coming through the wall. John described it as the kind of massage where you’re not entirely sure if you’re being helped or attacked, and the answer turns out to be both. He’d do it again. PHP Architect Becomes Padres Season Ticket Holders Eric and John are now official San Diego Padres season ticket holders — their first year in the program. As first-timers, they’re at the very bottom of the seniority ladder, which means they were among the last to pick seats. John blames Eric for not signing up years ago. There’s an upcoming Wednesday day game against the Dodgers with available tickets if anyone in San Diego wants them — reach out to John. Links from the show: PHP Tek 2026 — Chicago TanStack — Open Source Data Tools for the Web NativePHP — Simon Hamp’s Native App Framework for PHP PHP Architect Store PHP Architect Discord Host: Eric Van Johnson X: @shocm Mastodon: @eric@phparch.social Bluesky: @ericvanjohnson.bsky.social PHPArch.me: @eric John Congdon X: @johncongdon Mastodon: @john@phparch.social Bluesky: @johncongdon.bsky.social PHPArch.me: @john Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ PHPScore Put Your Technical Debt on Autopay with PHPScore CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.05.14 appeared first on PHP Architect.

 In this episode, Scott talks Global Accessibility Awareness Day with Joe Devon the creator of the day. Links: Our Discord – https://discord.gg/aMTxunVx Buy our shirts – https://store.phparch.com/products/community-corner-podcast-t-shirt Joe’s Links: LinkedIn – https://www.linkedin.com/in/joedevon/ Global Accessibility Awareness Day – https://accessibility.day/ Accessibility and Gen AI Podcast – https://podcasts.apple.com/us/podcast/accessibility-and-gen-ai-podcast/id1759047581 Scott’s Links: Website – https://scott.keck-warren.com/ Bluesky – https://bsky.app/profile/scottkeckwarren.bsky.social LinkedIn – https://www.linkedin.com/in/scott-keck-warren-91689810/ Mastodon – https://phpc.social/@scottkeckwarren PHP Architect Social Media: X: https://x.com/phparch Mastodon: https://phparch.social/@phparch Bluesky: https://bsky.app/profile/phparch.com Discord: https://discord.phparch.com Subscribe to our magazine: https://www.phparch.com/subscribe/ Partners This podcast is made a little better thanks to our partners. Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ PHPScore Put Your Technical Debt on Autopay with PHPScore https://phpscore.com/ CodeRabit CodeRabbit – Cut code review time & bugs in half instantly with CodeRabbit. https://www.coderabbit.ai/ Music Provided by Epidemic Sound https://www.epidemicsound.com/ #phpc #php #communityCornerPodcast #podcast #phptek The post Community Corner: Global Accessibility Awareness Day with Joe Devon appeared first on PHP Architect.

Ever wonder what actually happens when you step away from social media?   In this episode, I share what I discovered after a 7-day fast from my phone and social platforms.   Make sure you have your note pads or apps out and listen to the full episode.   Keep taking action, pursuing personal excellence, and impacting lives!   In This Episode, we discuss: Why disconnecting can dramatically reduce anxiety and mental noise The freeing truth about what happens when you stop posting How silence and stillness can deepen your faith and spark your creativity   Follow Us: Instagram: https://www.instagram.com/chrisandericmartinez/ YouTube: https://www.youtube.com/user/Dynamicduotraining     Attention Nutrition & Fitness Coaches: "Join our Free Dynamic Fit Pros Community Skool Group Where we help you Discover, Develop, & Deploy your skills, gifts, and greatness to help others."  See HERE   Attention Nutrition & Fitness Coaches: "Enrollment is Open for our Accelerator Mentorship to build a 6-Figure Online Fitness Coaching Business"  See HERE     See the full Show Notes to this episode here: https://www.liveadynamiclifestyle.com/podcast/i-quit-social-media-for-7-days-heres-what-i-found/

From AI agents as economic actors to quantum threats and prediction market regulation, Ali Yahya of a16z lays out the investment thesis behind a16z crypto's fifth fund. ======================================================== Thank you to our sponsor! Coinbase One 20% off first year of annual plan + $50 Bitcoin bonus. Offer valid until May 31. coinbase.com/unchained ======================================================== a16z crypto just closed its fifth crypto fund at $2.2 billion — smaller than its previous fund, but the firm says that's deliberate.  General Partner Ali Yahya argues we are entering a different phase of crypto's development: one where infrastructure is ready, regulatory clarity is arriving, and the competition for real users has begun in earnest.  Two themes sit at the center of a16z's thesis — the collision of crypto and FinTech, and the emergence of AI agents as economic actors. But Yahya's most striking claim may be about blockchains themselves: that performance is no longer a moat, privacy is. And that the chains which get privacy right will accrue stronger network effects than anything the industry has built before.  What does a world of privacy-dominant blockchains do to DeFi composability, to security, to the ability to track hackers? And where does the quantum threat actually stand? Host: ⁠⁠⁠⁠⁠⁠⁠⁠Laura Shin⁠⁠⁠⁠⁠⁠⁠⁠, Host / Unchained Guests: ⁠⁠⁠⁠⁠⁠⁠⁠Ali Yahya, General Partner, a16z crypto Learn more about your ad choices. Visit megaphone.fm/adchoices

This week, Dan and Donnie welcome back Raymond Kidwell, director of business development for Voice for Pest, for an update on the current capabilities of AI voice agents. Raymond explains how pest and lawn companies are using this ever-changing technology now, where it's going in the future, and how companies that have not yet incorporated it can get started.    Guest: Raymond Kidwell, Director of Business Development, Voice for Pest Hosts: Dan Gordon, PCO Bookkeepers & M&A Specialists: https://pcobookkeepers.com/ Donnie Shelton, Triangle Home Services: https://trianglehomeservices.com/ Sponsors: Coalmarch: https://www.coalmarch.com/podcast PestSure: https://www.pestsure.com/ Voice for Pest: https://www.voiceforpest.com/podcast Forshaw: https://www.forshaw.com/ Peer Groups: https://www.pmpindustryinsider.com/peergroups

As we approach the hot summer and accompanying rainy season, the specter of Florida's water quality issues will no doubt rear its ugly head so it seemed like the perfect time to spread some educational science ahead of all the seasonally induced emotional rhetoric and grifting. Unfortunately, and against all scientific data, agriculture in Florida has become the easy target, the primary scapegoat if you will, for Florida's water quality woes. It's past time to admit that everyone in our state owns these problems and that we've all got to come together to effectuate real and lasting solutions.

The Third Amendment to the Constitution forbids the quartering of troops in Americans' houses. It's a reminder of how uneasy the people of the country have been about the domestic deployment of our soldiers. There are robust rules about how the military can be used on American soil, but how did those rules come about? It's a question that National Guard officer Jonathan Bratten hoped to help answer in Forging the Framework: Evolving Law, Policy, and Doctrine for the US Military's Domestic Response, which he edited and contributed to as one of the authors. "It was really cool to see the way that the roots of our processes are built into the colonial era, just as the roots of a lot of our frictions are built into the colonial era," Bratten tells Modern Law Library host Lee Rawles. Forging the Framework, which is available for free from the Army University Press, looks at how different periods of American history shaped how the military operates on American soil today. As a country that has not faced many invasions, the bulk of domestic military operations have been to respond either to civil unrest or to natural disasters. "When you look at how this affects those who serve, I just think about the number of people who got called off of the COVID-19 mission, where [you were] helping your community members to go deploy, to protect, go into support of law enforcement during the George Floyd protests," says Bratten. "There's just that weird duality that exists in the Guard and these experiences sort of ripple through." In this episode of the Modern Law Library, Bratten and Rawles dive deep into the Pullman Strike, Posse Comitatus, slave revolts, the rewards of disaster response and the difficulty of convincing militiamen to confront their rioting relatives. Download Jonathan's book here. 

Most people spend their lives chasing the wrong things: money, status, validation, and the approval of others. But what if there was a better way?   In this episode, we pull back the curtain on our exciting rebrand and introduce The Higher Standard Series, a podcast dedicated to helping you be more purpose driven and invite God into every area of your life, make Him your true business partner, and build a life of real meaning and purpose.   3 Key Takeaways: This is not about becoming more religious, it's about becoming more aligned. Aligned with your purpose, your values, and who God created you to be. Real success is deeply meaningful, not just financially impressive. Learn how to build serious income and impact without selling your soul to do it. Life is dynamic. You can pivot, grow, heal, and raise your standards but it starts with refusing to settle for less than what you were made for.   Make sure your notepad is ready. This one hits differently.   Keep taking action, pursuing personal excellence, and impacting lives!   In This Episode, We Discuss: The Vision Behind The Higher Standard Series The Higher Standard is about inviting God into every area of life and business and learning how to make Him your true business partner. This series will cover how to build income and impact without compromise, include God in your decisions and leadership, walk away from the flesh-driven side of entrepreneurship pride, greed, comparison, and selfish ambition and discover, develop, and deploy your God-given gifts and potential.   What Does It Mean To Live A Higher Standard & Dynamic Lifestyle? It means refusing to settle. Choosing not to live complacent, comfortable, or mediocre. It means being a giver, choosing growth over comfort, taking full ownership of your life, and building a life and business aligned with your values. Because life is not static you can pivot, adapt, grow, reinvent yourself, and dream bigger.   The 5 Pillars of Living a Higher Standard & Dynamic Lifestyle: Faith: Your relationship with God, your values, and the foundation that guides every area of your life. Love: Your marriage, family, friendships, and the people who matter most. Health (Temple): Your physical, mental, emotional, and spiritual well-being. Wealth (Treasure): Financial freedom, stewardship, and the ability to provide and make an impact. Happiness (Fruit of the Spirit & Talents): Living with joy, gratitude, peace, passion, and doing work and life you genuinely love.   Follow Us: Instagram: https://www.instagram.com/chrisandericmartinez/ YouTube: https://www.youtube.com/user/Dynamicduotraining Website: https://www.liveadynamiclifestyle.com/     Attention Nutrition & Fitness Coaches: "Join our Free Dynamic Fit Pros Community Skool Group Where we help you Discover, Develop, & Deploy your skills, gifts, and greatness to help others."  See HERE   Attention Nutrition & Fitness Coaches: "Enrollment is Open for our Accelerator Mentorship to build a 6-Figure Online Fitness Coaching Business"  See HERE   "We are here to help you Live A Higher Standard & A Dynamic Lifestyle!"     See the full Show Notes to this episode here: https://www.liveadynamiclifestyle.com/podcast/the-higher-standard-5-shifts-to-stop-settling-start-living-with-real-purpose/

White Flag of Victory by Ty Braxton: https://www.amazon.com/White-Flag-Victory-Ty-Braxton/dp/B0CK3ZWYR3/ref=sr_1_2?crid=1PBK9YE1EXS7W&keywords=white+flag+of+victory&qid=1696613968&sprefix=white+flag+of+%2Caps%2C114&sr=8-2 Shop: gocharliemike.com To Donate:      Venmo: @CharlieMikeIntlDonatePaypal: charliemike.me@gmail.com For more videos: https://www.youtube.com/channel/UCO7u5mHOBX7TCaReVTwZC6w Facebook: https://www.facebook.com/charliemikeinternational Instagram: https://www.instagram.com/charliemikeintl/ Podcast Platforms we are on: Apple: https://podcasts.apple.com/us/podcast/the-breach/id1542623117?fbclid=IwAR3berLPvTkXXjoxW3dk1fPfzIyDK3TJYm5epuEPfWHcrkewr_TpV0mwJEs Spotify: https://open.spotify.com/show/3L6rL1x8J9loM7maBZXNWk?fbclid=IwAR0JEmwiV10nLMjhPQ0LJeYrYK68XggzDSN1Uo7Qzf2TzCqmXa6rMaiONxg Breaker: https://www.breaker.audio/the-breach-1?fbclid=IwAR13iwxEoDWKWyzzAhvFB4hvBDoH981E3IW3NHKL1td6HO74iY9rBmRib58 PocketCasts: https://pca.st/7ght6e4u?fbclid=IwAR2e_UvTdgCpbsOJW4ZsJloVM1ftP3OE20GRMLgW8iN4ksGUht1B0_nabh8 Anchor: https://anchor.fm/charliemikeintl?fbclid=IwAR1kAU-Oo5pZrdoK9CiaDUzN3G7HPNgiznNlUDk3WuokIhY3GWhemMQ-y1k

Five Eyes agencies issue agentic AI guidance. A federal database leaks Social Security numbers. A stealthy worm poisons open source packages. OT firms are sidelined from frontier cyber models. The FBI warns of a surge in cyber-enabled cargo theft. Officials flag likely election interference as security programs face cuts. Researchers uncover a covert Python backdoor. Ubuntu's site takes Iranian-linked DDoS fire. Cyber pros are sentenced in a ransomware case. Our guest is Andrew Carr, Global Head of Threat Management at Booz Allen, discussing how AI is accelerating cyberattacks. OpenAI joins the invitation-only club. Remember to leave us a 5-star rating and review in your favorite podcast app. Miss an episode? Sign-up for our daily intelligence roundup, Daily Briefing, and you'll never miss a beat. And be sure to follow CyberWire Daily on LinkedIn. CyberWire Guest On today's Industry Voices we are joined by ⁠Andrew Carr⁠, Global Head of Threat Management at ⁠Booz Allen Hamilton⁠, discussing how AI is accelerating cyberattacks and reshaping cybersecurity defenses. If you enjoyed this conversation be sure to check out the full interview here. Selected Reading Careful Adoption of Agentic AI Services (CISA)  Careful adoption of agentic AI services (Cyber.gov.au) Medicare portal exposed health providers' Social Security numbers (The Washington Post) Open-source registries hit by 'Mini Shai-Hulud' supply chain attacks (Developer) OT Cybersecurity Frozen Out by Frontier Labs (OTToday) FBI Warns of Surge in Hacker-Enabled Cargo Theft (SecurityWeek) Breach Roundup: US Cyber Command Flags Election Threats (Gov Infosecurity) Sophisticated Deep#Door Backdoor Enables Espionage, Disruption (SecurityWeek) Pro-Iran group turns Ubuntu DDoS into shakedown (The Register) Two Americans Who Attacked Multiple U.S. Victims Using ALPHV BlackCat Ransomware Sentenced to Prison (United States Department of Justice) OpenAI locks GPT-5.5-Cyber behind velvet rope (The Register) Share your feedback. What do you think about CyberWire Daily? Please take a few minutes to share your thoughts with us by completing our brief listener survey. Thank you for helping us continue to improve our show. Want to hear your company in the show? N2K CyberWire helps you reach the industry's most influential leaders and operators, while building visibility, authority, and connectivity across the cybersecurity community. Learn more at sponsor.thecyberwire.com. The CyberWire is a production of N2K Networks, your source for strategic workforce intelligence. © N2K Networks, Inc. Learn more about your ad choices. Visit megaphone.fm/adchoices

All links and images can be found on CISO Series This week's episode is hosted by David Spark, producer of CISO Series and Michelle Wilson, CISO, Movement Mortgage. Joining is sponsored guest Rob Allen, chief product officer, ThreatLocker. This show was recorded in front of a live audience at ThreatLocker's conference, Zero Trust World 2026. In this episode: Risk as a daily habit AI agents talking to AI agents The code on the lock Words that shape decisions A huge thanks to our sponsor, ThreatLocker ThreatLocker makes Zero Trust practical. With Default Deny, Ringfencing, and Elevation Control, CISOs get real control that's easy to manage and built to scale. Stop threats before they execute and reduce operational noise without adding complexity. See how simple prevention can be at ThreatLocker.com/CISO.

8. GUEST: Una Schneck and Charlie Detelich. Una Schneck and Charlie Detelich outline future Titan exploration plans. With an unlimited budget, they would deploy weather stations, buoys, and submarines to study the moon's methane lakes and complex hydrological cycle. 82019

The same bold playbook that built the middle class can restore it, and voters are ready…See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

PREVIEW FOR TOMORROW: Peter Huessy discusses the lack of nuclear education among young national security officials,. He warns that Russia and China now deploy battlefield nuclear weapons to win conflicts, moving far beyond Cold War deterrence strategies today. (1)1953