50 épisodes
- 🎙️ PHP Podcast - November 19, 2026
Hosts: Joe Ferguson, Sara Golemon & Holly Schilling
PHP 8.6 ships, Sara git-blames a 20-year-old HTTPS bug live on air, half the internet catches fire with RCEs, and Holly wears a Ninja Turtle hoodie (not a onesie). Just another busy week in PHP.
🐘 PHP 8.6.0 Goes GA
The big headline this week is that PHP 8.6.0 reached general availability. It's production-ready and packed with new features to play with, including partial function application, a new time duration class, and a new polling API. The hosts are genuinely excited about what some of these additions will enable going forward.
Alongside the feature release came a batch of security fixes that were tagged across all supported PHP versions. These weren't the same caliber as the recent "PHP to shell" scare — most of the bugs don't function in default PHP configurations on most platforms — but they were still important enough to warrant updating. Joe noted the PHP Arch clients were patched first thing in the morning as soon as the Docker images were ready.
The team also gave a shout out to the refreshed php.net homepage designs making the rounds, with Sara noting she'd seen them months ago and still liked them. After years of criticizing the look of the site, even the usual skeptics agreed the new design looks snazzy.
🔎 Sara Git-Blames a 20-Year-Old HTTPS Bug Live
For much of the episode, Sara was visibly going through the stages of grief in her terminal window, git-blaming a CVE that she described as "dumb" before softening it to "an unfortunate accidental mistake." The bug: a URL with an "HTTPS" scheme where the "S" is capitalized ends up not being TLS encrypted, because the source code checks whether the fifth byte is a lowercase "s" using a direct single-byte comparison instead of a case-insensitive check.
The same flawed check applies to other schemes like FTPS as well, since it's literally the same piece of code. Sara dug through the history line by line, nearly having a heart attack when it briefly looked like she'd introduced it, before tracing the real origin back to the Ides of March 2002 and the introduction of the streams layer in PHP 4.3.0 — before her time. The last time she touched that line was July 24th, 2004, purely to indent it for an if block.
The lesson the hosts landed on: this is 22-plus-year-old code that hundreds of people have looked at over the decades, and any one of them could have swapped that single-byte compare for a proper case-insensitive comparison. Joe jokingly declared the official takeaway of the episode was "one CVE was Sara's fault," which Sara gamely accepted on behalf of her 20-something-year-old self.
🔥 The Industry-Wide CVE Apocalypse
PHP wasn't alone. The crew ran through a parade of vulnerabilities hitting the broader ecosystem: a pair of NGINX CVEs allowing RCEs on HTTP/2-enabled servers (Joe's un-upgraded servers that never supported HTTP/2 were, ironically, safe), a "Java to shell" RCE, and a Ruby vulnerability that also affected Mastodon — prompting Joe to patch phparch.social that afternoon.
The Java bug had an enormous blast radius, enabling pre-auth RCE in KeyCloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins, and post-auth RCE into Apache Kafka, Solr, and Elasticsearch. Interestingly, it depends on CPU architecture, exploiting the specialized AVX-512 VBMI instructions OpenJDK uses to speed up base64 decoding on x86-64 Intel and AMD chips — meaning Apple Silicon is unaffected.
The hosts mused on why PHP's "to shell" moment got far more attention than any of these, concluding it's down to PHP's ubiquity and massive attack surface. As Sara put it, PHP is like a cockroach that fits in any biome. Holly floated a half-joking theory that AI tools are now surfacing decades-dormant vulnerabilities across every language, and the thing that'll ultimately thwart the robots is our collective lack of shame about shipping buggy software.
🌐 Automattic Lands the .PHP TLD
In lighter PHP news, Automattic (the company behind WordPress) picked up several new top-level domains, including the uncontested .PHP TLD, along with .jazz and .soul. It's essentially a done deal from the string confirmation stage, though it's not clear yet exactly how Automattic plans to steward and issue registrations.
Joe and Holly riffed on who should own the obvious domains — Joe wants index.php, the foundation arguably deserves www.php, and someone in Discord pitched info.php and docs.php as a home for documentation. The consensus was that the PHP Foundation simply doesn't have the roughly six-figure-per-year budget it takes to become a TLD registrar, which is why it landed with Automattic instead.
The conversation drifted into the economics of TLDs — you pay a hefty annual fee to a body like ICANN, with the expectation you'll recoup it by selling second-level domains. Joe's dream buy would be .nerd (php.nerd, wow.nerd, computer.nerd), though as Holly pointed out, you can run your own DNS server declaring .holly as yours all day long; the hard part is getting anyone else's resolvers to listen.
📣 Release Management, Pull Quotes & Terminal to Shell
Joe reflected on his first stint as a PHP release manager, having packaged many of the alphas, betas, and RCs for 8.6 under the mentorship of veteran release manager Daniel (friend of the show, who the hosts ribbed for being young enough that his phone is older than he is). With 8.6 now in its support window, 8.2 is set to drop out of active support on January 1st, 2027.
Eric has started turning snippets from the podcast into quotable image "toots" for Mastodon to tease each episode. Joe admitted he vetoed roughly half of the first batch for being either too spicy or lacking context — a bar that this particular episode, missing the visual of Sara's thousand-yard stare and Holly's Ninja Turtle hoodie, will struggle to clear.
The show closed on the parody site terminal-to-shell.com, a send-up of the CVE panic with a CVSS score of 11 out of 10, a zero-millisecond time to exploit, and a 55-year exposure window. Holly and Sara turned the whole CVE apocalypse into a mock pharmaceutical commercial — if your installation lasts more than four minor versions, please consult a specialist, because you're out of support.
Links from the show:
PHP Tek 2027 — Chicago, April 27–29, early bird tickets available
Join the PHP Arch Discord
PHP Arch Swag Store
PHP 8.6.0 — Now Generally Available
nginx fixes http2 rce vulnerabilities
Ruby2Shell
Automattic gets new TLDs including .php
Terminal2Shell
Host:
Joe Ferguson
Mastodon: @joepferguson@phpc.social
PHPArch.me: @svpernova09
Sara Golemon
Mastodon: @pollita@phpc.social
Holly Schilling
Mastodon: @TheCodeLorax@tech.lgbt
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
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. Learn more.
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 Community Corner Podcast: Why I'm Ditching Docker for Lerd, with George Dumitrescu
18/11/2026 | 20 minIn this episode, Scott talks with George Dumitrescu about Lerd, his open-source PHP development environment: why he wrote it in Go with Claude, why it runs on Podman instead of Docker, and how it gives every git worktree its own .test domain and database.
Links:
Our Discord - https://discord.gg/aMTxunVx
Buy our shirts - https://store.phparch.com/products/community-corner-podcast-t-shirt
Mentioned in this episode:
Lerd - https://lerd.sh/
Lerd on GitHub - https://github.com/lerd-env/lerd
Lerd Discord - https://discord.gg/5JK54s7xCC
Lerd on X - https://x.com/lerdphp
Lerd on Bluesky - https://bsky.app/profile/lerdphp.bsky.social
Laravel Herd - https://herd.laravel.com/
Podman - https://podman.io/
Go - https://go.dev/
Claude - https://www.anthropic.com/claude
git worktree - https://git-scm.com/docs/git-worktree
Laravel Scout - https://laravel.com/docs/scout
Meilisearch - https://www.meilisearch.com/
George's Links:
Website - https://george.dumitres.co
GitHub - https://github.com/geodro
LinkedIn - https://www.linkedin.com/in/geodro
X - https://x.com/geodro
Sponsor George - https://github.com/sponsors/geodro
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
Chapters:
00:00 Meet George Dumitrescu
00:50 What Lerd does
01:52 Laravel Herd for Linux, then framework definitions
03:07 Why Go, and building with Claude
06:20 Podman instead of Docker
08:24 Git worktrees with their own database
10:00 A .test domain for every branch
12:12 Open source, framework stores and plugins
14:30 Request timing, the site doctor and safer git pulls
17:26 PHP communities around the world
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.
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.epid
The post Community Corner Podcast: Zachary Watkins Codes With His Voice, Feet, and Face appeared first on PHP Architect.- 🎙️ PHP Podcast - November 12, 2026
Hosts: Joe Ferguson, Sara Golemon & Holly Schilling
A surprise RC7, assembly-level ABI detective work, Claude landing commits in php-src, a survey on why nobody upgrades, Portuguese wiring codes, and the corporate spy saga that ate your RAM. Just an "off week."
🐘 The Surprise RC7 and the Last-Minute Regression
Joe, serving as a first-time release manager alongside Matteo Beccati, walked through why PHP 8.6.0 RC7 appeared seemingly out of nowhere. RC6 was tagged on the usual Tuesday cadence, but a regression needed to land, leaving the team a choice: ship 8.6.0 GA with a known regression where working 8.5 code would break on upgrade, or throw another RC. As Joe put it, he'd rather apologize for a last-minute RC than apologize for a regression on GA.
The decision was made easier by the fact that packagers like Remy need lead time to rebuild extensions. Because the team committed to an extra RC, they were also able to slip in a few nice-to-haves, including some use-after-free OpenSSL fixes that were all public knowledge and nothing security-embargoed.
Sara fully endorsed the "when in doubt, add an RC" philosophy, pointing out that releases happen on Thursdays precisely so the weekend acts as a buffer. A December GA wouldn't be the end of the world either — uptime-conscious shops wait until January anyway, giving the packages and the public beta crowd time to shake out surprises. Holly reminded everyone: this is a release candidate, not a release. Don't run it in production.
🔬 Reading Assembly to Hunt an ABI Break
The RC saga tied back to an earlier mistake: the ABI version bump that was missed in RC3 because of the CVE scramble on the 21st. That meant RC3 and RC4 could have had nasty extension conflicts, and anyone seeing weird extension behavior on those builds was likely hitting the ABI break that wasn't caught until RC5.
Joe showed off Daniel Scherzer's blog post, which drops down into the actual assembly and diffs the obj-dump output for the exception check. The trio squinted at near-identical instruction listings until the real difference surfaced: a jump target that moved from one address to another — about 32 bytes off from where the code expected to be looking.
Sara reverse-engineered the cause live: roughly four word-sized fields had been added to the end of a structure (it's in Reflection), shifting every subsequent offset. She explained the ABI lesson clearly — a header says "this field is X bytes into the structure," and if you mix an 8.5 header with an 8.6 build, you read garbage memory. For a plain integer that's bad data; for a pointer, the CPU politely tells you to fuck off, mate. The catch: it only bites extensions built as separate shared objects, not statically built ones.
🤖 Claude as a Contributor and the "Humans.txt" Problem
Joe raised a spirited discussion happening in the PHP Foundation's internals Slack: Claude Code now shows up as a contributor in php-src, and some worry that reads like the project endorsing a commercial AI tool. Sara pushed back — commits attributed to @yahoo.com or @facebook.com addresses aren't endorsements, they're just people contributing while earning a living. Holly added that mailing lists and git clients have appended "Sent from my iPhone" style signatures forever and nobody cared.
The real sticking point, Joe argued, is that AI-generated contributions haven't been tested against open-source licensing in any legal system, yet those contributions are now in the project. Sara pointed to php.net/humans.txt, which still reads "built by humans, mostly" — a "mostly" she thinks may have quietly been there all along.
The conversation also detoured into Claude's new 5.2 behavior around security: it'll audit your own code and describe exploits with suggested patches, but it won't generate a proof-of-concept exploit to actually validate the vulnerability. Holly found that limitation a bit pointless, while the gang schemed about pointing it at localhost.
📊 Why Teams Don't Upgrade PHP
Joe dug into a recent opt-in survey about what blocks teams from upgrading. The headline findings: it's almost never a single blocker (47–51% cite more than one), 86% cite at least one business or resource reason, and 51% say there's no visible ROI in upgrading. Sara's immediate rebuttal: if you're on PHP 5, there absolutely is an ROI — you can run half as many servers.
Holly aired a pet peeve that upgrading a language version shouldn't break things, prompting a friendly "citation needed" from Sara. Joe countered that the real pain in legacy apps (pre-8) is usually unvetted, unmaintained dependencies — the one-off package that did one thing well but got abandoned, so even 5.5 to 5.6 broke it. Sara agreed that's an ecosystem problem, not PHP's fault, and challenged the group to name actual PHP-caused breaks: pulling mysql out of core, the ternary precedence swap, and little surprises like opcache becoming standard.
That opcache change was exactly Holly's lived example: an 8.3-to-8.5 Docker build broke because a now-unnecessary build step for opcache failed with no obvious documentation. Sara's gentle suggestion to read the migration guides (plural, since it was a two-version jump) sparked some mock outrage, but the underlying point stood — unnecessary friction is a real cost, and the bigger the version gap, the more insurmountable the step. The survey also noted 56% cite missing tests or staging environments, and even many who run automated tests lack confidence in their coverage.
🏠 Home Automation, Portuguese Wiring, and the Spouse Test
A tangent about testing "wiring" turned literal when Sara revealed she's been rewiring her new place in Portugal — where brown is live and blue is neutral (IEC color codes), which Joe immediately flagged as a nightmare for the colorblind. Sara's home is heavy on automation: motorized metal sun shutters, IKEA smart bulbs in GU10 sockets, Shelly modules behind the light switches, internet-connected heat pumps, and a smart plug that only runs the water heater in the cheap overnight electricity window.
The group compared setups and the all-important "spouse test." Joe keeps it minimal — doorbell camera, backyard security cam, and a Google Nest thermostat that keeps re-adding a schedule he deleted — and admitted his Jellyfin server didn't pass the spouse test at all. Sara and Joe both evangelized Home Assistant: mostly Python but happy to call out to PHP scripts that return JSON, container-friendly via docker-compose, and far from the painful early days of home automation.
They swapped favorite automations — Holly's litter-box nag texts and fridge-door-left-open light color alerts, Joe's jealousy over people graphing solar production in the Rove Discord's home automation channel. Add an MQTT broker and Node-RED and you've got message buses the whole house can listen to. Holly offered to info-dump on anyone who drops by Discord's general channel (dark mode supported, naturally).
🕵️ The NVIDIA Spy Saga and a GA on the Horizon
Somewhere between RAM shortages and bad TV writing, the crew riffed on the ex-NVIDIA CEO news — allegedly running GPUs on Chinese hardware he wasn't married to, plus a third "integration" that shouldn't have been happening, with a spy in the mix and the board already preparing to oust him. Joe shared a Mastodon favorite: a "NVIDIA CEO transitions" headline quote-tooted with "I'm so happy for her," which Holly and Sara declared very brave in this climate.
Back to business: PHP 8.6.0 is scheduled to hit general availability on November 19th, and the team floated doing some live server upgrades as a "release party" during next week's recording. Huge shout-out to Matteo (watching live from a very late timezone) for herding php-src pull requests and pinging contributors for approvals to get RC6 and RC7 ready. And as always — there are socks that need selling, a freshly leaked phparch.com redesign to break, and a PHP Arch cowboy hat the people are now demanding.
🔗 Links from the Show
PHP Tek 2027 — Chicago, April 27–29, early bird tickets available
Join the PHP Architect Discord
production.phparch.com — the new site preview (go break it, nicely)
Home Assistant — open-source home automation
What stops PHP teams from upgrading (Accesto survey)
What happened to PHP 8.6.0 RC6? (Daniel Scherzer)
Hosts
Joe Ferguson
Mastodon: @joepferguson@phpc.social
PHPArch.me: @svpernova09
Sara Golemon
Mastodon: @pollita@phpc.social
Holly Schilling
Mastodon: @TheCodeLorax@tech.lgbt
📺 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.
🤝 Partners
This podcast is made a little better thanks to our partners.
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. Learn more about PHP Architect Consulting.
Music provided by Epidemic Sound.
🎯 Join Us Live Next Week
Watch on our YouTube Channel
Got feedback? Join us on Discord at discord.phparch.com - In this episode, Scott talks with Zach Watkins about coding through osteoarthritis with Talon Voice, a split keyboard mounted to his chair, and foot pedals with macOS head tracking.
Chapters:
00:00 Meet Zach Watkins
01:26 Numb hands and an osteoarthritis diagnosis
03:21 One week searching for answers
06:30 Patching Talon Voice for PHP
10:03 Writing your own voice commands
12:09 Split keyboards on camera mounts
14:01 Layers on a 42-key keyboard
17:17 Foot pedals
19:35 macOS head and face tracking
Links:
Our Discord – https://discord.gg/aMTxunVx
Buy our shirts – https://store.phparch.com/products/community-corner-podcast-t-shirt
Mentioned in this episode:
Save Your Hands for Another Day (Longhorn PHP 2026 talk) – https://zacharywatkins.com/presentations/save-your-hands-for-another-day/
Coding without typing – https://zacharywatkins.com/articles/coding-without-typing/
Coding without typing (part 2) – https://zacharywatkins.com/articles/coding-without-typing-part-2/
Talon Voice – https://talonvoice.com/
Talon community commands – https://github.com/talonhub/community
Zach’s Talon configuration – https://github.com/ZachWatkins/user-talon
r/ErgoMechKeyboards – https://www.reddit.com/r/ErgoMechKeyboards/
Crosses keyboard – https://github.com/Good-Great-Grand-Wonderful/crosses
Kinesis Savant Elite2 foot pedals – https://kinesis-ergo.com/shop/savant-elite2-triple-pedal/
Move the pointer using head pointer on Mac – https://support.apple.com/guide/mac-help/mchlb2d4782b/mac
Shortcuts for Mac – https://support.apple.com/guide/shortcuts-mac/welcome/mac
Longhorn PHP – https://www.longhornphp.com/
Zach’s Links:
Website – https://zacharywatkins.com/
GitHub – https://github.com/zachwatkins
X – https://x.com/zachwatkinsv1
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.
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.epid
The post Community Corner Podcast: Zachary Watkins Codes With His Voice, Feet, and Face appeared first on PHP Architect. - PHP Podcast – November 5, 2026
Hosts: Eric Van Johnson & Joe Ferguson (John Congdon)
Two months, a dozen new stream buttons, and a 6 AM crypto-mining emergency. Eric falls in love with a developer-only social network, the PHP2Shell CVE tests the team, and PHP Tek season kicks off. Welcome to the Boss Level.
Back After Two Months — and Everything Is On Fire (Audio-Wise)
After nearly two months off the air, Eric and John opened the Boss Level episode the only way they know how: with a full-blown audio meltdown. Eric was on the wrong mic, and as usual, his connection kept cutting in and out while the crew wrestled with a fresh stack of stream widgets, pop-up reactions, and survey overlays nobody fully understood.
Once they got the sound working, they reintroduced the show. This is the monthly “Boss Level” episode where the two people behind PHP Architect pull back the curtain on the magazine, the conference, and the consulting business — with a little more candor than usual, since, as Eric put it, John can’t fire him and he can’t fire John.
Leaked AWS Keys and a 6 AM Bitcoin-Mining Nightmare
John’s week started at 6:10 AM with pager alerts about a Lambda function failing to post to Slack. What looked like a trivial memory leak turned out to be something far worse: a leaked AWS key with permission to spin up instances. An attacker had launched 32x and 64x large machines in every single region to mine Bitcoin.
The team rallied — four or five people each terminating instances region by region — and disabled the compromised key before new instances could spawn. Using AI tools to dig through the logs, they discovered the key had first been quietly tested back in September, likely by whoever was selling it to prove it was valid before putting it on the market. Identifying and rectifying took about 20 minutes, but it was not a fun morning.
/Dev/Null: A Social Network Built for Developers in a Day
Eric gushed about /dev/null, a brand-new developer-centric social network built on Laravel in roughly a day or two by Nuno, Brent, Matthew, and Pauline Voss. Everything about it is geared to developers: the main feed is “the log,” posting is “making a commit,” your VIM bindings work inside it, and sign-up ties directly to your GitHub account to pull in your profile. He’s begging the creators to keep the walled garden intact and not make it easier for the “normies.”
He also highlighted a TUI built by Wendell (a Laravel employee and PHP Architect columnist) that mirrors the web app so closely it’s become Eric’s home for DevNull right inside his Tmux setup. That led into a tour of his terminal-centric workflow — one Tmux session per project (a trick from Jess Archer), panes for Claude, nvim, and dev servers, lazygit for commits — and why he quietly retired PHPStorm earlier this year in favor of nvim and the terminal. Pauline, a fantastic conference speaker known for Git talks, has even started livestreaming on Twitch following the build.
PHP Tech 2027: Call for Speakers Closed, Evaluation Begins
The call for speakers has closed, and talk evaluation is underway. John is changing the process this year so reviewers judge fewer talks at a time — one smaller track took him about three minutes. Anyone in the community, ideally planning to attend, can reach out to John on Discord to get added and help pick what gets presented. You rank three anonymized talks side by side, with the title doing most of the heavy lifting since that’s what attendees see on the website.
Eric reminded listeners that submitting multiple talks improves their odds of being selected when narrowing the final list. Speakers with more than one accepted talk get priority since they’re the biggest bang for the buck. This year’s third track rotates: a JavaScript day, a Laravel day, and a DevOps day. John noted it was exactly that deployment knowledge gap that first drew him to PHP Tech back in 2010, when he had no idea how to actually deploy an application. All the details live at phptek.io.
The PHP-to-Shell CVE and Why a DevOps Person Matters
PHP had a rough couple of weeks due to a major “PHP2shell” CVE. Joe, a release manager for the upcoming PHP 8.6, had sensed something was brewing and started preparing rollout plans before the details dropped. When it hit, the team patched nearly everything across their clients within 24 hours, with only a couple of third-party-dependent servers trailing. Eric and John reflected that after 14 years of running their consulting arm (the DiegoDev Group, now PHP Architect Consulting), finally having a dedicated DevOps person has made the difference between night and day.
The fallout rippled outward: NativePHP published a candid write-up about having to issue its first-ever security advisory, since a PHP vulnerability affects anything that compiles PHP into a mobile app. The hosts wondered how projects like NativePHP can get into the “consortium” that receives early patch access alongside the big distros. They also pushed back on the “PHP is dead” crowd — this was a memory bug that has lived in the code for 20 years and affects roughly 70% of the web, but memory bugs happen in every language, from Node to npm. The silver lining: a visible spike in PHP Foundation financial contributions, with Eric clarifying that the Foundation funds internal developers but doesn’t dictate PHP’s direction.
Git Workflows, SVN War Stories, and the Specialization of Developers
The conversation wandered into deployment history — FTP and rsync in the SVN/CVS days — and Eric’s war stories from a Java/WebSphere enterprise shop where developers had no idea where their apps were even hosted. His takeaway: developers today are extremely specialized, and you shouldn’t be surprised when a brilliant Java dev can’t navigate a command line.
Eric defended his fork-based Git workflow: a single clean “upstream” repo that only deploys to servers, with everyone forking into their own private GitHub account and sending back only clean, deployment-ready code, essentially the open-source model. The chat gave him grief, including jabs about failing at Git worktrees, which Eric conceded he understands in principle but finds painful in a PHP workflow with its multiple Composer and npm installs and environment files.
Links from the show:
PHP Tech 2027 — Call for speakers closed; register now
PHP Architect Consulting
store.phparch.com — PHP Architect merch & elephants
PHP Foundation Office Hours (streamed on our channel)
Dev-Null.sh
PHP 8.6.0 RC5 available for testing
Linux Kernel TCP Flaw
PHP 8.6’s soft feature freeze
PHP Foundation Community Hour Podcast
NativePHP first security advisories
Host:
Eric Van Johnson
/dev/null: @ericvanjohsnon
X: @shocm
Mastodon: @eric@phparch.social
Bluesky: @ericvanjohnson.bsky.social
PHPArch.me: @eric
John Congdon
/dev/null: @johncongdon
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
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.11.05 appeared first on PHP Architect.
Plus de podcasts Technologies
Podcasts tendance de Technologies
À propos de PHP Architect Podcasts
All podcasts from PHP Architect — PHP tutorials, interviews, and community discussions.
Site web du podcastÉcoutez PHP Architect Podcasts, A la French ou d'autres podcasts du monde entier - avec l'app de radio.fr

Obtenez l’app radio.fr gratuite
- Ajout de radios et podcasts en favoris
- Diffusion via Wi-Fi ou Bluetooth
- Carplay & Android Auto compatibles
- Et encore plus de fonctionnalités
PHP Architect Podcasts: Podcasts du groupe







































