Larasense logo
Aug 30, 2026
·
9m 34s

I hate everything after two weeks

Aug 29, 2026
·
13m 1s

Write better requirements or pay for it later

Have you ever handed off a feature request with barely any detail and expected the developer to just figure it out?In the latest episode of the No Compromises podcast, we discuss why writing clear requirements is one of the most valuable things a business can do before development starts.We make the case that even imperfect requirements beat none at all because they determine where the discovery happens, closer to the finish line rather than somewhere in the middle of the country.We also cover why letting AI write your requirements for you is a trap, and how AI can help you review and cross-check requirements instead. And why the more detail you put in upfront, the less money you spend on surprises later.(02:53) - Good requirements let you build start to finish (05:10) - Imperfect requirements still beat having none (07:36) - Why AI should not write your requirements (09:09) - Using AI to cross-check requirements instead (10:46) - Silly bit Have a messy real-world project you're working through? Join the No Compromises community and talk it through with other developers.Subscribe to the Mastering Laravel newsletter for practical insights that help you communicate better with your development team.

Aug 28, 2026
·
22m 18s

I FINALLY CRACKED UNDERSTANDING CODE THAT AI WRITES

Aug 27, 2026

The PHP Podcast 2026.08.27

PHP Podcast – August 27, 2026 Hosts: Joe Ferguson, Sara Golemon & Holly Schilling Zero-downtime swaps that nobody noticed, 3D printers that refuse to calibrate, a nostalgia tour through the entire PHPArch back catalog, Go generics, TypePHP, and a very good reason to book a flight to Belgium. This one lived in the gutter and loved it. Zero-Downtime Environment Swaps in AWS Joe kicked off the show talking about migrating a client’s production, staging, and test environments to completely new Elastic Beanstalk setups in AWS — during one of the client’s biggest selling seasons — and nobody noticed except him. That’s the dream: a zero-downtime upgrade that customers never feel. He explained that this was actually the second full rebuild of these servers in two months. The first migration got them off an aging Amazon Linux platform, and once everything was captured in CloudFormation templates and supporting scripts, swapping to an entirely new environment for an SSL certificate adjustment was suddenly no big deal. Being able to swap whole fleets of application servers behind a CNAME or DNS record and have clients never know is, in Joe’s words, one of the coolest things about cloud computing that will never get old. It also spawned a new accidental buzzword: “infrastructure as cloud.” 3D Printing Trials, Tribulations, and Guitar-String Belts Sara got her 3D printer working and has been printing everything from QR codes to a donate-link plaque for the PHP Foundation booth (inspired by feedback Sebastian got at a conference), all using the tried-and-true multicolor technique of hitting pause at the right layer and swapping filament. This is Sara’s fourth printer that should have been her third — she detailed the multi-day kit assemblies, belts that had to be tightened like guitar strings before calibration would work, and a tiny plastic pulley holder that snapped apart. Apparently nobody in Lisbon has a working 3D printer to help print a replacement part, so she resorted to sanding wood into a makeshift holder before finally getting it running and printing spares of everything. Holly admitted 3D printing is another expensive hobby she’d never follow through on, and Joe confessed he’d want the “Apple of 3D printers” that never jams — the same reason flying drones didn’t stick for him, since what he was actually doing was crashing and repairing drones. Sara later shared her first real project: little blue printed brackets that consolidate her monitor’s power and Thunderbolt into a single clean cord. Old Tech Nostalgia: Radio Shack Kits, Punch Cards, and Hard Drive Platters The crew took a deep dive into computing nostalgia. Sara reminisced about Radio Shack electronics kits with big springs you’d push aside to hold wires in place, lamenting that modern kits just have you jumper a GPS to a single-board computer — something big is missing from that experience. Holly recalled hacking on a third-hand 8088 laptop from a garage sale because her parents wouldn’t let her touch the family 486, and spending a full year in 1997 trying to get DHCP working across three Windows 95 machines before giving up and hard-coding IP addresses. Sara topped it with serial null-modem cables running between rooms in her first apartment, back when your serial port was your network. Holly then held up hard-drive platters she keeps as wall decoration, prompting a genuinely fun tangent about whether you could manually write bits to a low-density platter with a needle and magnet — a “solvable problem” per Joe, complete with G-code and a printed robot housing. The group also swapped memories of building PCs when a video card was mandatory and Sound Blaster was king, plus punch cards still stacked in a university basement at the turn of the century. Go Generic Methods, the PHPArch Archive Vault, and PHP 8.6 Go’s newest release finally added support for generic methods (it already had generic structs and functions), which Holly noted is PHP-relevant since it ties back to her own generics proposal debates. Sara puzzled over why methods and functions weren’t just supported together, since the only declarative difference is that receiver parameter — leading to an impromptu live look at the syntax and the conclusion that “all of Go is weird, just in the opposite direction PHP is weird.” Eric dropped breaking news mid-show: anyone with a phparch.com account — even an old one from a lapsed subscription — now has access to the magazine archive going all the way back. Joe pulled up Volume One, Issue One, and dug up a November 2002 piece about PHP 4.3 RC2 — right around when Sara submitted her first PHP patch and gave the world unified streams. They also covered Eric Van Johnson’s blog post on the PHP 8.6 soft feature freeze. Beta 2 shipped with a lot more deprecations landing that weren’t in beta 1, and the hosts encouraged listeners feeling froggy to grab it and test drive. Holly griped that one of her merged 8.6 changes didn’t even get a mention — thanks a lot, Eric. TypePHP and Competing Runtimes The team dug into TypePHP, which compiles PHP down to a native binary. Sara was openly dubious of the speed claims — a 50% gain wouldn’t surprise her, but an 8x gain needs much better data — while Joe noted the only demos so far are CLI apps, not traditional web workloads, and worried the authors are writing a very different style of PHP than most people do. Holly framed it through history: the whole reason PHP, Perl, and CGI exist is to avoid the per-request cost of loading and launching a native binary, so she’s curious what tradeoffs a compiled approach makes — especially since people sensitive to raw performance often reach for Go in the first place. She also pointed out most PHP code is just reading a file, not running the billion-row challenge. Sara pushed back on the “competing runtime” framing, recalling HHVM as more synergistic than antagonistic — it launched with PHP’s own code inside it, and PHP 7 hitting the speed of PHP 5 was directly informed by HHVM’s research. The real test will be whether TypePHP can run real Laravel apps and WordPress sites reliably enough for ecosystem adoption, the same way HHVM eventually powered Wikipedia’s front end with just a single WordPress patch. PHP Foundation Speaker Accreditation & PHP BeNeLux Returns Joe covered today’s PHP Foundation Ambassador SIG meeting, focused on the speaker subgroup and a proposal James Seconde has been working on. The goal is a foundation accreditation program that builds a list of speakers who can carry a consistent PHP message, tapped by geographic region so events get local speakers, more diverse voices get on stage, and nobody gets burned out flying halfway across the world when four nearby speakers could do the same talk. The big excitement, though, was the announcement of PHP BeNeLux in Antwerp, Belgium in January 2027 — the first since January 2020 before COVID. Sara audibly lost it, partly because it lines up with FOSDEM and partly out of love for longtime organizer Michelangelo van Dam, whom Joe credited as a huge, welcoming reason he got involved in the PHP community in the first place. Both hosts are already thinking about submitting talks. Links from the show: PHP Tek 2027 CFP — extended through end of October PHP Tek 2027 — April 27–29, Chicago (tickets available) PHPArch Swag Store 3D Code Generator Export QR codes as STL for 3D printing PHPArch.com Magazine Archive — now available to all account holders PHP 8.6 Beta 2 — now available for testing TypePHP — PHP compiled to a native binary PHPBenelux — Antwerp, Belgium, January 2027 Host: Joe Ferguson Mastodon: @[email protected] PHPArch.me: @svpernova09 Sara Golemon Mastodon: @[email protected] Holly Schilling Mastodon: @[email protected] Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email [email protected] – 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/     OurCVEs Your security posture, on autopilot with OurCVEs   CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.   PHP Architect Consulting   Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on. https://www.phparch.com/consulting/   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.08.27 appeared first on PHP Architect.

Aug 27, 2026
·
13m 30s

I tried Amp and Claude desktop today to see what I'm missing

Aug 27, 2026
·
21m 38s

Meteors and space peanuts and identifying wrong-turns

Aug 27, 2026
·
54m 7s

Paused queues, test doubles, and migrating files

Jake and Michael discuss all the latest Laravel releases, tutorials, and happenings in the community.Show linksPause All Queues and a New artisan dev UI in Laravel 13.25Read-Through Disks and Debounced Listeners in Laravel 13.26Laravel Read-Through Filesystem: Lazy Storage MigrationDebounced Queued Event Listeners in LaravelQueue::forward(): Reroute Laravel Queues in One PlaceAgent Run Observability in Laravel AI SDK 0.11Laravel AI: Trace Agent Runs With Lifecycle EventsLaravel AI: Get Raw HTTP Responses and Rate LimitsMock PHP Classes in Tests With the Double LibraryNativePHP v4: Build Native iOS and Android UI in BladeLet's Encrypt HTTPS on an IP Address With FrankenPHPStatamic Mailables Viewer Previews Laravel Emails in the Control PanelLaravel Discount: Coupon Codes, Usage Limits, and StackingLaravel Chores: Resumable Data Operations and CleanupsLaravel Tackle: Run an AI Coding Agent in Your Laravel AppTutorialsLaravel Terminal UI for the artisan dev CommandPause All Laravel Queues During a Deploy

Aug 25, 2026
·
1h 32m 42s

146: Do Things & Tell People

Ian and Aaron discuss Aaron's trip to Copenhagen for Laravel Live DK, meeting DHH, having "the hell trip home", using AI to beat Air Canada's bureaucracy, and so much more.Sponsored by Bento, DropInBlog, Valorin Security, and Svix.Interested in sponsoring Mostly Technical?  Head to https://mostlytechnical.com/sponsor to learn more.(00:00) - Back In the Land of the Free (01:52) - Happy Anniversary! (04:22) - Aaron's First Intl Biz Class Flight (12:04) - Laravel Live DK (22:05) - Aaron's Talk & Meeting DHH (32:58) - DHH & Taylor's Fireside Chat (42:27) - The Spoon Is An Airplane (56:22) - The Hell Trip Home (01:17:41) - Scheming With Codex (01:27:34) - A Quick Controversy Links:Abigail Otwell's airport photo (Aaron in line behind Taylor & Abigail)Laravel Live DKDHH on Twitter/XOmacom Foundation launches with $8 million (Omarchy blog)GeocodioTom Crary on Twitter/XTaylor's video of Aaron trying caviarFlighty (iOS app)Ian's tweet of the chairs Aaron slept on

Aug 24, 2026
·
16m 27s

I MADE A SALE!

Aug 20, 2026

The PHP Podcast 2026.08.20

PHP Podcast – August 20, 2026 Hosts: Joe Ferguson, Sara Golemon & Holly Schilling Shirley MacLaine is the answer — but what’s the question? RAM prices went up 500%, GitHub fell over for eight hours, and the crew figured out how you can actually contribute to PHP. Glasses optional. Shirley MacLaine, Green Room Shade, and the Show’s New Normal The episode opens with Joe flustered — not because it’s a “flustered day,” but because there’s shade being thrown in the green room backstage chat. Rather than spoil the drama, the crew turns a mysterious green-room answer into a running bit: “Shirley MacLaine” is the answer, and listeners are invited to submit what the question was. It’s declared the first round of PHP Architect’s Jeopardy, complete with its own Easter egg sound cue. Joe also lays out where the show is heading. Eric and John took over the podcast the previous week to relive their glory days, and the plan is for the old guys to step back to roughly one episode a month. Joe and Sara are working on something to fill one slot, another mystery show is in the works pending signed contracts, and Alive and Kicking is confirmed still alive and kicking after a great recent episode with Derek. Joe also plugs the PHP 8.6 Beta 1 tag and Scott Keck-Warren’s PHP Community Podcast interview with release managers Daniel Scherzer and Matteo Bacotti. The RAM Apocalypse: 500% in Twelve Months The big topic of the week is the ongoing memory and chip crisis. Memory prices have climbed 500% in twelve months, and the crew commiserates about the parts they wish they’d bought bigger. Sara explains the brutal math: you can’t build a semiconductor fab fast enough — two or three years minimum — and by the time one comes online nobody knows if we’ll have overproduction or a burst bubble. Worse, Sara notes that essentially every RAM stick through the end of 2027 is already accounted for and sold to vendors. The ripple effects are everywhere. Console prices are going up instead of down late in their cycle, with next-gen consoles projected to start at $1,000 or more. The hobbyist single-board computer market is getting crushed — Pine64 announced they’re stepping back from making hardware, and a Raspberry Pi 5 that debuted cheap now runs over 100 pounds. Holly’s new PC, bought at the start of 2025, ended up shipped 3,000 kilometers the wrong way to California and is stuck awaiting import paperwork, leaving her leaning on a laptop and some now-precious Raspberry Pi zeros. The nostalgia gets thick as the crew reminisces about DIP chips, EDO RAM, Pentiums, Epson 486s, Tandy 1000s, and the TRS-80. Special venom is reserved for Packard Bell (“utter freaking trash”) and Gateway 2000’s cow-pattern branding — which Sara confirms sold better in Wisconsin than anywhere, though hay bales in a Berkeley storefront still boggle the mind. A chat comment about technicians de-soldering and reballing BGA RAM chips becoming economically viable gets a hearty “absolutely.” Memory-Aware Development and Why PHP 7 Doubled Down Bringing the RAM crisis back to PHP, Joe wishes more developers were aware of how their applications consume and release memory — a lesson he credits to learning enough C back in the day, where you have to manage memory yourself. He connects sloppy memory awareness to the N+1 query problems web developers keep tripping over. Sara drops a great deep dive: a significant reason PHP 7 was roughly twice as fast as PHP 5 was changes in the memory layout. Every variable became referenced by one fewer pointer, and while eight bytes sounds trivial, every level of indirection adds time across every single instruction and access. Sara adds the CPU-level detail — one layer of indirection can be a single instruction on most architectures, but adding a second layer can push a lookup from one instruction to three. That leads into a warm tangent about learning C to become game developers. Sara’s evergreen joke: “I’m going to be a game developer” is the programmer’s version of “I’m going to buy a bar.” Great people, brutal hours, endless competition, and the reality of hitting spacebar 400 times to figure out why you can phase through a wall. The cat-reading-the-paper “I should buy a boat” meme makes an appearance to seal it. The GitHub Outage and the Monoculture Problem Monday’s eight-hour GitHub outage hit the crew directly. Holly couldn’t use a site that only offered “log in with GitHub,” and Joe got kicked out of his CLI auth session mid-PR with no way to re-authenticate. To GitHub’s credit, they published an incident update and a follow-up blog post: a service auto-scaled so aggressively to handle network traffic that the sidecar and supporting services couldn’t keep up, bringing the whole thing down. The conversation turns to whether this is self-inflicted. Joe recalls GitHub’s pre-Microsoft, gold-standard reliability and wonders aloud how much the decline lines up with Copilot’s arrival and internal AI adoption, with uptime reportedly slipping below a single nine at points. Sara defends them somewhat — the number of actions, CPU cores, and pull requests has genuinely hockey-sticked, partly because AI has emboldened people who previously wouldn’t have opened a PR. But as Joe puts it, the call is coming from inside the house, since GitHub itself has been pushing AI. On alternatives, Joe says the least-jarring migration for PHP Architect’s clients would be self-hosting GitLab, since GitHub Actions and GitLab runners are nearly identical in syntax — Atlassian’s Bitbucket, by contrast, is a bridge too far, mostly because the entire ecosystem assumes you’re on GitHub. Sara names this the core problem: monoculture. The crew discusses package mirrors, local caches, 12-factor thinking, and Composer’s support for custom mirrors, all while remembering the PHP repo intrusion years ago that came from an unmaintained self-hosted Git server. The takeaway: owning your pipeline end-to-end is the only way an outage can’t stop you — and Joe teases spinning up a self-hosted GitLab now that “the boss” (Sara) has signed off. How to Contribute to PHP (and Handling Security Reports) The crew highlights two PHP Foundation blog posts. First, Matt Stauffer’s “How to Contribute to PHP,” adapted from a talk he gave at Atlanta PHP. It goes well beyond “learn C,” clearly separating the PHP project, the PHP ecosystem, and the Foundation, and lays out approachable on-ramps: testing pre-releases (PHP 8.6 Beta 1 is out, Beta 2 lands next week), improving documentation, and writing tests — which, spoiler, are written in PHP, not C, using PHP’s own test format that’s simple enough to learn from any single example. Other contribution paths include triaging and reviewing issues across PHP repositories — invaluable work that frees core developers from wading through AI-generated slop bug reports — and participating in internals via the well-documented mailing list process, up to and including running for release manager (8.7 managers will be needed before you know it). Sara points folks to discord.phpc.chat for the PHP Discord, with dedicated Internals and Foundation channels for anyone the mailing list intimidates. Second, Sebastian Bergmann’s “So you received a security report. Now what?” is a jump-around reference for application developers rather than a front-to-back read, walking through roughly ten steps to triage, validate, and resolve reported issues the right way. Sara shares a real-world example from mobile: a flagged package that was only exploitable on a rooted device with an actively hostile package installed alongside it — a very different risk profile than a SQL injection on an API endpoint. Cue reminiscing about writing SQL against Access databases over ODBC from PHP (and Perl) back in the 90s, and Joe’s advice for handling any security report: don’t panic, and always know where your towel is. Links from the show: PHP Tek 2027 — April 27–29, 2027 in Chicago; early bird tickets & hotel available now PHP Tek 2027 CFP Audio versions of the podcast at phparch.com Join us live on Discord at discord.phparch.com PHP Discord — discord.phpc.chat Community Corner Podcast: PHP 8.5 + 8.6 Release Manager Daniel Scherzer Memory prices climb 500% in 12 months So You Received a Security Report. Now What? How to Contribute to PHP Shirley MacLaine Host: Joe Ferguson Mastodon: @[email protected] PHPArch.me: @svpernova09 Sara Golemon Mastodon: @[email protected] Holly Schilling Mastodon: @[email protected] Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email [email protected] – 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/     OurCVEs Your security posture, on autopilot with OurCVEs   CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.   PHP Architect Consulting Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on https://www.phparch.com/consulting/   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.08.20 appeared first on PHP Architect.

Aug 20, 2026

Community Corner Podcast: PHP 8.5 + 8.6 Release Manager Daniel Scherzer

 In this episode, Scott talks with Daniel Scherzer, release manager for PHP 8.5 and PHP 8.6, about the bug-fix release cycle, partial function application coming in 8.6, and his upcoming talks at Longhorn PHP on what’s new in 8.6 and building PHP extensions in Rust. Links Our Discord – https://discord.gg/aMTxunVx Buy our shirts – https://store.phparch.com/products/community-corner-podcast-t-shirt Daniel’s Link https://scherzer.dev/ LinkedIn – https://www.linkedin.com/in/daniel-scherzer-520539263/ 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 #jscpd The post Community Corner Podcast: PHP 8.5 + 8.6 Release Manager Daniel Scherzer appeared first on PHP Architect.

Aug 20, 2026
·
12m 16s

Zoom in and zoom out