php[podcast] episodes from php[architect]

PHP Podcast – October 15, 2026

Hosts: Joe Ferguson & Holly Schilling

Longhorn PHP kicks off, agentic commerce gets scary, bots keep scanning, and a Cold War satellite schematic proves software is harder than hardware.

Swag, Longhorn PHP, and “Am I Even a PHP Developer?”

Joe opened by confessing he found a JavaScript bug in the swag store cart while ordering socks and a hoodie — the curse of being a developer who can only ever see the bugs. Holly joked that Sara got bumped from the show for refusing to wear swag, while Eric apparently bought one of everything in the store, including a Peanuts-style team picture card from PHP Tech.

The conversation turned to Longhorn PHP 2026, which kicked off with a tutorial day and runs through the main talk day on Friday. Holly is presenting remotely after travel plans fell through, giving a talk on her pet peeve: websites that get “packaged up” and shipped as apps instead of being built as real native applications.

That led into a heartfelt riff on imposter syndrome. Holly admitted she’s spent years insisting she’s “not really a PHP developer” despite submitting RFCs, speaking at conferences, and having an elephpant named after her. Joe shared his own years at a Python startup where he felt like a fraud for only writing PHP nights and weekends. The takeaway: showing up in community spaces — Discord, social media, GitHub, conferences — is all it takes to belong.

Agentic Commerce and Single-Use Card Security

Joe highlighted a Community Corner episode with Scott Keck-Warren and Paul Conroy on agentic commerce — the slightly terrifying idea of your Claude agent going out shopping on your behalf. Holly was especially wary of trusting Gemini for shopping advice given Google’s long history of steering how people search and buy.

Much of the underlying tech, they noted, lives in Stripe and resembles Apple Pay-style single-use card numbers: time-limited, amount-limited tokens that protect the real source card. Holly drew on her experience at a buy-now-pay-later company (now branded FlexPay) doing one-time code generation, where even 15-minute-lived card numbers required full PCI compliance, certificate pinning, HMAC, encryption at rest, and constant audits across every layer from mobile SDK to backend.

Bots, Scrapers, and Cloudflare to the Rescue

A Discord listener (ducknizzle) asked what everyone uses to kill bot and scanner traffic on public sites. Joe’s pessimistic answer: block ranges, sometimes entire countries, and ultimately just put it behind Cloudflare and let specialists deal with it — the same way you’d pay someone to host email rather than running it yourself.

Holly praised Cloudflare Pages for static content, calling it free and “it just works” with zero bandwidth worries, though WordPress makes things more complicated. Joe talked about his work-in-progress effort to standardize robots.txt across php.net properties, while acknowledging it only helps the well-behaved crawlers — malicious scrapers and AI training bots will simply ignore it. Holly estimated AI scrapers now outnumber legitimate bots roughly 10 to 1, and both lamented how the internet has lost some of its earlier friendliness.

How the PHP Security Team Handles Your Reports

Joe showcased a PHP Foundation blog post describing how the security team triages reports, sharing insight from his new role as a release manager. Release managers get advance heads-up on security releases, which follow extra processes to handle disclosures responsibly.

He explained that every report is read, triaged, and prioritized — someone in Discord recently got confirmation their advisory was “in the backlog.” The sobering reality is that the greater PHP security team is only one or two humans, reflecting the open-source nature of the project. The team can now issue its own CVEs rather than waiting on GitHub, so fixes and packager updates can ship as fast as possible. Joe noted serious, wild remote-code-execution-level vulnerabilities remain rare, especially this early in the 8.6 cycle, which just branched from master.

New PHP News Site, Design, and php.net’s Redesign

Joe demoed a new PHP ecosystem news site from Eric Barnes (Laravel News) and Matt Stauffer (Titan) in collaboration with the PHP Foundation — a modern aggregator reminiscent of the old Planet PHP days, complete with RFC coverage, a newsletter, topic sections, and a slick automatic dark mode toggle. Holly, admitting she has no eye for design herself, loved how well it was executed.

That sparked a running theme of developer respect for design as a discipline neither host feels competent in. Joe mentioned a php.net redesign in progress — mock-ups are available in the PHPC Discord’s PHP Foundation Ambassador Marketing subgroup, though it’s still a work in progress and not yet mobile friendly. Both admitted feeling like outsiders in design meetings the way non-developers feel in dev meetings. Joe shared Anthropic’s guidance to tell Claude what you *don’t* want for front-end work, to which he replied that as a developer, he often doesn’t even know what he doesn’t want.

A Satellite Schematic vs. a Million Lines of Code

Holly launched into a favorite tangent, inspired by Apple releasing its home hub device years after the hardware was ready and pundits asking why the software took so long. Working on her own project with 16 encryption keys across five servers, she had to draw diagrams just to keep the key exchanges straight.

She then described a treasured artifact: a 3-by-9-foot schematic of an entire FSC-78 Bravo-mod satellite terminal from her Army SATCOM days at Fort Detrich — the whole Cold War-grade, anti-jamming system fitting on roughly 65 letter-sized pages. Contrast that with Margaret Hamilton’s famous photo beside the Apollo code printouts: around a million lines, a scale that’s routine in modern projects. Her point: software complexity dwarfs even elaborate hardware, and developers rarely give themselves credit for it — leaky abstractions, uncaught exceptions, and endless edge cases don’t plague hardware the way they plague code.

The discussion wrapped with fault tolerance stories: Joe discovered a three-node Elasticsearch staging cluster where failover had never been enabled (and only one node was taking all the traffic), and Holly recalled a satellite timing setup with redundant cesium sources where the only part that kept failing monthly was the single non-redundant box joining them together. Fault tolerance, they agreed, is important.

Links from the show:

PHP Tech 2027 — Chicago, April 27–29, tickets & CFP open

Join us in Discord

PHP Arch Swag Store

PHP Foundation — How the Security Team Handles Your Reports

Community Corner Podcast: Agentic Commerce with Paul Conroy

2027 State of Open Source Survey (Perforce / OpenLogic / Zend)

PHP Architect Consulting

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

The post The PHP Podcast 2026.10.15 appeared first on PHP Architect.

In this episode, Scott talks with Paul Conroy about agentic commerce: how AI agents buy things on our behalf, how Stripe’s shared payment tokens keep them on a budget, and how the Machine Payments Protocol finally puts HTTP 402 Payment Required to work in your API middleware.

Links:

Our Discord – https://discord.gg/aMTxunVx

Buy our shirts – https://store.phparch.com/products/community-corner-podcast-t-shirt

Mentioned in this episode:

Charging AI Agents Per Request: A Practical Guide to the Machine Payments Protocol – https://conroyp.com/articles/practical-guide-machine-payments-protocol

Agentic Commerce Beyond The Checkout: Building with Machine Payments (Paul’s talk) – https://conroyp.com/speaking/agentic-commerce-beyond-the-checkout-building-with-machine-payments

PayForGoals.com, the MPP demo – https://payforgoals.com

PayForGoals.com source code – https://github.com/square1-io/www.payforgoals.com

laravel-mpp package – https://github.com/square1-io/laravel-mpp

Stripe Machine Payments Protocol quickstart – https://docs.stripe.com/payments/machine/mpp/quickstart

Paul’s Links:

Website – https://conroyp.com

Company: Square1 – https://square1.io

X / Twitter – https://x.com/conroyp

Bluesky – https://bsky.app/profile/conroyp.bsky.social

LinkedIn – https://www.linkedin.com/in/paulconroy2/

GitHub – https://github.com/conroyp

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.epidemicsound.com/

The post Community Corner Podcast: Agentic Commerce with Paul Conroy appeared first on PHP Architect.

PHP Foundation Community Hour – October 8, 2026

Hosts: Elizabeth Barron & James Titcumb

James tells the story of how he fell into open source, breaks down what Pie actually does, celebrates the 1.5 release, and shares real advice for anyone nervous about making their first contribution.

How James Got Into Open Source

James traced his open source journey back many years to a set of Zend Framework 1 helper classes he found useful enough to publish, back when he wasn’t even sure GitHub existed yet. From there he built a little tool to deploy code from Git over SSH at a previous employer, replacing a hand-upload process that he knew had to be modernized.

Things really took off when he joined Roave, where contributing was actively encouraged and he was surrounded by prolific maintainers like Marco working on Doctrine, alongside in-house libraries such as Security Advisories and Better Reflection. Having a supportive employer early on made all the difference, letting him do the work during the day instead of squeezing it into nights and weekends.

Elizabeth reflected that this is a common on-ramp into open source: scratch your own itch, put it out there, and hope it helps someone with the same problem. She emphasized how much employer support, team mentorship, and a genuine culture of open source help newcomers find their footing.

What Pie Is and Why It Exists

James explained that Pie came about because the infrastructure around PECL and PEAR is simply aging, with very few people who know the code base well enough to maintain it. The PHP Foundation approached him to overhaul that tooling, applying the hard-won lessons of Composer — which he agrees is arguably the best package manager for any language.

Under the hood, Pie is really a very fancy wrapper around four commands — phpize, configure, make, and make install — plus a lot of dependency management and making sure you get the right package for your specific PHP install, something PECL never really did. Thanks to the Packagist team setting up an extensions area, Pie plugs into Composer’s source code to get that dependency resolution for free.

A key distinction is that you aren’t installing extensions for a project the way you do with Composer packages — you’re installing them for a particular PHP install. Pie manages this in a dedicated Pie home directory, keeping each of your many PHP versions and their extensions sorted out. James’s bigger goal has evolved from simply replacing PECL to making installing an extension as frictionless as installing a PHP package.

Democratizing Extensions and the Windows Challenge

Moving off PECL’s centralized repository and onto Packagist means literally anyone can now submit an extension, the same way they publish PHP packages. James noted that when problems come up there are usually three kinds of fixes: improving something in Pi, writing better documentation, or working with an extension author who hasn’t configured their composer.json correctly.

Because extensions have unique needs, the Composer team added new Pi-specific options to specify configure flags, supported platforms, and architectures — concepts Composer never had since it only ever dealt with pure PHP code. A Windows-only library extension is useless on macOS or Linux, and a systemd-dependent one is useless on Windows, so that categorization matters.

The most common friction point James sees is Windows extensions. Unlike PECL, which auto-compiled DLLs from uploaded source, the Pie ecosystem requires authors to build the DLL themselves — handled through a GitHub Action called PHP Windows Builder, which Shivam worked on. For security reasons Pie deliberately can’t just download and run arbitrary binaries on people’s systems.

The 1.5 Release

Elizabeth congratulated James on shipping 1.5, a significant release that pulled together several large, closely-related requests. A lot of it grew from working with the author of the mlocati Docker PHP extension installer, mapping out everything Pie does on a whiteboard to see where changes could unlock multiple features at once.

The big internal change was fixing how Pie handles locking, bringing it much closer to how Composer manages its own lock file. That one improvement enabled installing multiple extensions at once, making a reinstall of an already-installed extension a no-op, installing reproducibly from a lock file, and the long-requested Pie upgrade command that bumps all your Pie extensions in one go.

The other massive chunk of work was the attestation library. It started as a bare-bones OpenSSL-based verification of GitHub attestation certificates — written with help from Tim Düsterhus so people could verify Pi’s authenticity without needing the gh CLI. For 1.5, James ran it against the Sigstore conformance test suite and filled in a huge number of gaps, bringing it close to full conformance on the verification side. That opens the door to the Composer team’s stated interest in authenticating PHP packages down the line.

Advice for New Contributors

Asked what he’d tell his past self, James kept it simple: just get involved, and always assume good intent. If a maintainer doesn’t respond within a day they’re probably just busy — not ignoring you — and lengthy back-and-forth on a pull request usually reflects a maintainer trying to keep the project maintainable, not nitpicking.

He encouraged everyone to open a discussion before sending a PR so effort doesn’t get duplicated — a lesson learned after early contributions collided with work he already had in progress. To help with that, he adds a “maintainer investigating” label to issues he’s actively working on, and leans on issue and PR templates to steer people in the right direction.

Elizabeth added that newer coders can find it intimidating to put their work out publicly on GitHub forever, and that both sides benefit from a little grace and a shared social contract. James closed by stressing that the single most helpful contribution is feedback — report even the small things you worked around, because eliminating that friction saves the next developer the same headache, as happened with a recent PCRE2 compile fix on macOS.

Links from the show:

Pie(php/pie) — GitHub repository, issues & discussions

PHP Windows Builder GitHub Action

Packagist Extensions

Composer

attestation library

Introduction to PIE

Host:

Elizabeth Barron

Mastodon: @elizabeth@fosstodon.org

LinkedIn: elizabethn

James Titcumb

Mastodon: @asgrim@phpc.social

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.



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 PHP Foundation Community Hour Podcast 2026.10.08 appeared first on PHP Architect.

In this episode, Scott talks Len Woodward about This Week in PHP Internals and the state of the PHP Internals world.

Links:

Our Discord – https://discord.gg/aMTxunVx

Buy our shirts – https://store.phparch.com/products/community-corner-podcast-t-shirt

Len’s Links:

X / Twitter: @ProjektGopher — https://x.com/ProjektGopher

Bluesky: @projektgopher.com — https://bsky.app/profile/projektgopher.com

Mastodon: @ProjektGopher@phpc.social — https://phpc.social/@ProjektGopher

Threads: @projektgopher — https://www.threads.com/@projektgopher

Instagram: @projektgopher — https://www.instagram.com/projektgopher/

LinkedIn: https://www.linkedin.com/in/projektgopher/

Pinkary: @ProjektGopher — https://pinkary.com/@ProjektGopher

Reddit: @ProjektGopher — https://www.reddit.com/user/ProjektGopher/

Dev.to: @projektgopher — https://dev.to/projektgopher

YouTube: @ArtisanBuild — https://www.youtube.com/@ArtisanBuild

Show: This Week in PHP Internals — https://www.youtube.com/@ArtisanBuild

Company: Artisan Build — https://artisan.build

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.epidemicsound.com/

#phpc #php #communityCornerPodcast #podcast #phptek

The post Community Corner Podcast: This Week in PHP Internals with Len Woodward appeared first on PHP Architect.

PHP Podcast – October 1, 2026

Hosts: Joe Ferguson, Sara Golemon & Holly Schilling

It’s John’s birthday, so naturally he skipped. The PHP Foundation is hiring, 8.6 picks up a surprise RC, and the crew goes deep on ABI promises, deprecation pile-ups, generics, and a childhood firefighter who’s still “a hit.”

John’s Birthday and the PHP Foundation’s Hiring Call

The episode kicks off with Joe, Sara, and Holly holding down the fort while Eric and John are out — John, as it happens, because it’s his birthday. The crew gleefully encourages everyone in Discord to ping John and wish him a happy birthday (and harass him appropriately), noting that John and Eric were the ones who scheduled the show for the first of the month in the first place.

From the celebratory ribbing, Joe pivots to real news: the PHP Foundation has opened its 2027 contractor applications. He walks through what they’re actually looking for — contributors who can read and write C, not just PHP, with experience writing extensions, participating on the internals mailing list, and contributing to open source. The work centers on filling gaps around security, reviewing pull requests, and keeping the language healthy.

Holly jokes she’d be the first person fired from the Foundation, and Sara dryly notes that someone has to be first. It’s a warm, self-deprecating opening that sets the tone for a technically dense but very loose episode.

PHP 8.6: The Mistag, the Extra RC, and the Release Schedule

Joe explains that it has been an unusually slow PHP news week, with most contributors heads-down on 8.6. He admits the team completely forgot to toot the recent release versions on Mastodon — which was notable because one of them was a security release, so listeners should update their PHP versions if they haven’t already.

The bigger story is a tagging bug. When branching 8.6 off master into its own branch at the RC1 milestone, the automation (a Docker-based release toolchain descended from scripts Sara once maintained and Mateo later upgraded) mistagged something. The fix was simply bumping to RC2, which means 8.6 now gets five RCs instead of the planned four, since RC1 and RC2 landed in the same week. Barring any game-breaking bugs, RC5 lands November 5th and general release is targeted for November 19th — conveniently dodging US Thanksgiving week.

Joe shares how much he’s learned stepping into the release manager role alongside Mateo, especially around ABI compatibility and backwards-incompatibility decisions. Sara confirms that PHP’s long-standing promise lives in the minor version number: as long as that middle number stays fixed, APIs can be added but never removed or changed from, say, a macro to a function pointer.

Feature Freezes, Late Deprecations, and the Branch Means Branch Debate

The conversation turns to process frustration. Sara makes her position clear: once a version branches, it’s a feature freeze — and feature freeze means feature freeze. She recounts how she drifted away from release management partly because every cycle brought the same surprise, with people acting shocked that time had passed linearly and that a feature freeze was arriving on schedule.

Joe observes that most of 8.6’s deprecations landed in the beta stage, which felt late to him. With the alphas largely empty of the substance that defines the release, he questions what incentive anyone has to test an alpha that lacks the deprecations and features that matter. He wishes he’d pushed harder to land those changes earlier.

Holly asks the obvious question: why are deprecations so late when the conversation about the next version’s deprecations should already be happening now? Sara offers a theory tied to habits of past release managers doing deprecations in May and June, plus the recurring tendency to dump fifty deprecation votes all at once. Joe confirms this round was among the largest deprecation batches since PHP 7, which Sara attributes partly to people wanting to start the two-phase removal clock as a new major version looms.

Generics, Arrays, and What Makes a Major Version

The hosts debate what would justify PHP 9. Sara argues PHP doesn’t use SemVer, so majors have historically been reserved for big conceptual shifts — annotations/attributes in 8, the engine rewrite in 7, object reference changes in 5, the Zend Engine in 4 — not just features. The current pipeline, in her view, lacks something substantial enough to warrant a nine.

Generics come up as the candidate. Joe thinks generics could eventually bump the version, though not until well after 8.7 ships. Sara wants generics for two reasons: they’re genuinely useful, and they’d finally get people to stop asking for them. Holly draws a firm line: generics should never be retrofitted onto the base array type, which is too strongly optimized to touch.

That spirals into a rich aside on arrays. Holly recounts seeing inexplicable ten-percent performance swings just from recompiling identical code. Sara reveals the awkward truth that “array” isn’t really one type but several hiding behind a shared facade, and that for associative data a plain-old-data class with named properties will be faster than array keys. The group also floats value types, structs, and copy-on-write semantics as worthwhile future directions.

Voice to Vectors: Eric Mann’s Searchable Audio Archive

Joe highlights a short, practical blog post from frequent contributor Eric Mann titled “From Voice to Vectors: Building a Searchable Audio Archive.” The value proposition resonates with anyone at a large company drowning in recorded meetings stashed in S3 — finding the one meeting you missed while on vacation is painful.

The post demonstrates using a handful of PHP extensions to transcribe recordings into text, run them through an LLM for inference, and load the results into a search engine so meetings, company history, and the decisions made in them become genuinely searchable. Joe calls it an awesome use case for the workflow.

Sara immediately riffs on applying it to her own hundreds of gigabytes of raw GoPro footage, using FFmpeg to strip the audio first — mostly so she can read transcripts and figure out which clips are safe to delete without watching hours of video (while carefully preserving the gold, like old footage of her niece and nephew).

Vanilla PHP vs. Framework Identity, and a Trip Down Assembly Lane

A Reddit thread asking whether to learn PHP from scratch or jump straight to a framework prompts a thoughtful segment. Joe favors learning vanilla PHP first — it’s how he learned — but recognizes not everyone learns that way, drawing parallels to the Rails era where developers identified as Rails devs more than Ruby devs, and to WordPress developers who wrote PHP without realizing it.

Sara pushes back gently on the idea that framework identity is new, citing years of Zend Framework devs and others, while agreeing it’s intensifying as ecosystems grow stronger. Both conclude it’s perfectly fine to specialize down to a framework if that fits your business — Joe notes PHP Architect standardizes on Laravel while still maintaining plenty of non-Laravel client code, some predating Laravel entirely. He reminisces about CakePHP being his first framework before Laravel 4 won out on an eleven-year-old hackerspace RFID member-management app that cheerfully ignores SemVer.

The show closes on a nostalgic low-level tangent sparked by a comment about learning pure languages first. Sara recounts learning x86 assembly in high school from a book that included the bytecode, writing her own video driver in Turbo Pascal to enable a 320×200 256-color mode via inline assembly. She and Holly trade register trivia — AX, BX, CX, DX, the accumulator, the X/E/R prefixes for 16/32/64-bit, and the AH/AL byte split — before wrapping with Jurassic Park quotes and calling it an episode.

Links from the show:

PHP Tek 2027 CFP — Submissions close at the end of the month

PHP Tek 2027 — Early bird tickets (April 27–29, Chicago)

PHP Architect Store — Socks, shirts, and swag

PHP Foundation 2027 Contractor Applications

Eric Mann: From Voice to Vectors — Building a Searchable Audio Archive

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. 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.10.01 appeared first on PHP Architect.