PHP Architect Podcasts

<br />

Hosts: Elizabeth Barron & James Titcumb

How James Got Into Open Source

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

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

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

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

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.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

https://www.epidemicsound.com/

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.

<span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span>

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

Links:

Len’s Links:

Scott’s Links:

PHP Architect Social Media:

Subscribe to our magazine: https://www.phparch.com/subscribe/

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

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.

<br />

Hosts: Joe Ferguson, Sara Golemon & Holly Schilling

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

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

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

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

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

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

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.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

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/

https://www.epidemicsound.com/

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.

<span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span>

In this episode, Scott talks to Nick Sagona about Pop PHP, a PHP framework that removes the “magic” so your code is easier to understand and maintain.

Links:

Nick’s Links:

Scott’s Links:

PHP Architect Social Media:

Subscribe to our magazine: https://www.phparch.com/subscribe/

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

Music provided by Epidemic Sound https://www.epidemicsound.com/

#phpc #php #communityCornerPodcast #podcast #phptek

The post Community Corner Podcast: Pop PHP with Nick Sagona appeared first on PHP Architect.

<br />

Hosts: Joe Ferguson, Sara Golemon & Holly Schilling

Longhorn PHP, Three Weeks Out and Doing Things Differently

Friday is the main conference day, opening with a keynote from Elizabeth Barron of the PHP Foundation and closing with Eric Mann. In between there are three tracks and fifteen non-keynote talks, plus open spaces later in the day for the topics that didn’t quite make the cut but still deserve a room full of experts to hash them out.

The biggest change: instead of the previous Thursday/Friday/Saturday layout, Longhorn is running as a weekday event. The main conference day is still available as a virtual ticket for anyone who can’t make it to Austin, streamed both live and after the fact — though the tutorial day stays in-person because three-hour hybrid workshops are notoriously hard to get right.

Streaming, Latency, and PHPC.tv

Ian explained how Longhorn and PHP Tech run their streams through MUX rather than YouTube or Twitch, because MUX lets them toggle low-latency streaming. With the venue fully hardwired at gigabit, they can drop latency from thirty seconds down to five or ten, getting remote attendees closer to real time. Joe reminisced about broadcast TV and AM radio football feeds being perfectly in sync back in the day — something modern streaming has, ironically, made worse.

Sara recalled Sean Coates hauling a satellite dish onto a hotel roof back in 2008 just to get a workable stream out of a venue with dial-up-grade internet. The good news is that serving a gigabit of packets no longer requires heroics, and venue connectivity has steadily improved year over year.

A Shifting Industry and the Job Market

Joe noted that straight-up “PHP developer” roles have largely vanished, replaced by “back-end,” “full stack,” “cloud,” and “forward deployed engineer” titles. Ian pointed out that on smaller teams, full stack is effectively mandatory now, and the real value a developer brings is increasingly about communication — pushing back on vague requirements that even a stack of servers couldn’t guess at.

This naturally spilled into a shared loathing of GraphQL, an aside about SOAP and XPath, and a genuinely grim note on RAM prices. With Samsung doubling a portion of production and rumors of Intel getting back into memory (and maybe even reviving Optane), there was cautious, sarcastic hope that prices might eventually come back down to earth.

The Business of Running a Conference

The hard numbers were sobering. Attendance dropped roughly 30% going into 2025, landing around 110 in-person attendees in a room built for 150 to 250 — enough to feel empty. The reliable last-minute booking surge that used to push the event from red to black largely failed to materialize, leaving the buffer demolished. Ian is happy to subsidize sponsorship gaps from his own pocket when the room is full, but a downturn in actual attendees is a different signal entirely.

That’s why this year scales back to two days: running a two-day event pencils out to about two-thirds the cost of three, Saturday flights are cheaper for a continental US crowd, and the better-attended days make for fuller rooms — which are simply more fun to speak to. Ticket and sponsorship prices even came down slightly rather than climbing with inflation.

Why the Human Component Still Matters

Sara made the emotional case plainly: her greatest fear is that in three years we lose the human component of problem solving and sharing our love of it. The hallway track, she insisted, is where it’s always at — you can’t replicate that over Zoom or a YouTube “like and subscribe,” and you certainly can’t get the photo of you stabbing your friend in a Viking helmet five years later.

To lean into that, the schedule intentionally keeps AI to a single tutorial and single talk — everything else is chosen for shelf life, including a PHP 8.6 talk from a release manager (the release lands about a month after the conference) and Elizabeth’s PHP Foundation session. The rest, Ian figures, will show up organically in the hallway track anyway.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

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

Youtube Channel

Got feedback? Join us on Discord at discord.phparch.com

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

<br />

Hosts: Joe Ferguson, Sara Golemon & John Congdon

The September Issue Ships Early (and the Blue Elephant Situation)

Attention quickly turned to the cover, which featured a distinctly blue elephant that the crew agreed had strong “Eric” energy. It came out that this was Jackie’s first attempt at managing the AI-generated cover art, which sparked plenty of teasing about who exactly the human-in-the-loop was. The team also teased upcoming pet shirts and cat socks for the swag store.

PHP Foundation Community Hour Launches

The first episode featured Elizabeth Barron interviewing Matt Stauffer about his blog post on contributing to PHP. Sara praised Matt as a great addition to the Foundation Board, and the crew noted his deep experience getting people to contribute to open source projects, plus his well-known Laravel: Up & Running book. The next episode lands next month with another guest on the theme of contributing to PHP.

The PHP Documentary and 8.6 vs. GTA 6

On the release side, Holly noted developer beta 3 is out with the RC approaching, at which point she’ll start pushing her RFCs out for discussion and voting. Joe revealed the general release date: Thursday, November 19th, PHP 8.6.0 — the very same day a small indie title called Grand Theft Auto 6 arrives. The last of the 8.6 deprecations only just merged, so even beta 3 didn’t have everything yet.

The CDN Bug That Cached the Wrong Homepage

Sara pointed out the CDN was actually doing something reasonable in normalizing the path; the real bug was serving a different page than the one you’d get requesting the root. Joe praised the provider’s support team, who confirmed the issue, escalated it to engineering, and validated his mitigation of disabling caching for those status codes. The conversation broadened into how AI crawlers and more sophisticated, high-unique-IP bot traffic are surfacing long-dormant bugs — and the uncomfortable centralization that comes from everyone hiding behind the same few CDN providers.

Foldables, Front-End, and the WoW Detour

Joe weighed in from a consumer angle, worrying about hinge durability on $2,000 foldables and whether they’ll last the three-to-four years he now expects from a phone. Somewhere in between, the show detoured hard into gaming — WoW Classic “Forever,” the November 4th launch, tank builds, and even the naming of shadow priests — before circling back to remind everyone you can, in fact, write MMOs in PHP.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

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

https://www.epidemicsound.com/

Youtube Channel

Got feedback? Join us on Discord at discord.phparch.com

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

<span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span><span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span>

In this episode, Scott talks with Stanislav Khromov about his project bun-php, which allows PHP to be run through the Bun JavaScript runtime.

Subscribe to our magazine: https://www.phparch.com/subscribe/

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

Music Provided by Epidemic Sound https://www.epidemicsound.com/

#phpc #php #communityCornerPodcast #podcast #phptek

The post Community Corner Podcast: bun-php with Stanislav Khromov appeared first on PHP Architect.

<br />

Hosts: Elizabeth Barron & Matt Stauffer

Welcome to the First Community Hour

The original concept was just a Zoom call where anyone could drop in and ask questions, but it evolved into something with a purpose and a theme. Big thanks went to the folks at PHP Architect for providing the platform and infrastructure, and to Joe Ferguson for producing behind the scenes.

Matt introduced himself and his work leading a PHP (and Laravel) consultancy that specializes in rescuing and modernizing legacy applications. He shared why he loves that space: PHP powers functional code spread across the internet doing real good for real people, which is exactly why he cares so much about the language and the Foundation.

The Blog Post That Started It All

Matt admitted he’d often found it hard, even as an experienced open-source contributor, to contribute to PHP itself. Digging into why, he found both truth and misconception. Some contributions happen in ways we don’t call “contributing to PHP” but should, and some pathways genuinely need better communication and community building.

His goal was a single canonical starting place — a short blog post that says “start here” for anyone who’s always wanted to contribute. It’s also a reminder to himself to know the current reality rather than criticizing PHP based on how it worked 15 or 20 years ago.

The Lowest Barrier to Contributing

The most important point Matt hammered home: contributing to any individual component, framework, package, or meetup is contributing to PHP. Working on WordPress, Laravel, or Symfony all counts. It does not have to be the language itself to matter.

Elizabeth agreed wholeheartedly that the definition of contribution should be broad. Every interaction, every engagement, every time someone shows up somewhere is a contribution. Newcomers are especially valuable — they can spot the gaps and holes that long-time maintainers no longer see. For those who do want to work on the language itself, Matt suggested reproducing other people’s bugs from the PHP source repo as the easiest onboarding point.

Everybody Matters in the PHP Community

Elizabeth shared that the Foundation recently started an onboarding special interest group where mentorship will be a topic, aimed at improving the overwhelming newcomer experience. They discussed the idea of a central hub or resource for contribution opportunities. Matt was cautiously supportive — worried programmers might over-engineer a tool instead of doing the work, but open to something that points people to where each community already lists its opportunities, while the Foundation creates that space specifically for the PHP language itself.

Matt shared his own contribution origin story: his first pull requests, back in September and October 2012, were to jQuery responsive-design plugins. Neither was merged, but the experience taught him that open source doesn’t need to reflect every person’s specific needs, and that most people online are genuinely kind and well-intended.

User Groups, SIGs, and Timezone Challenges

Matt debunked the perception that user groups are expensive to run. Food is usually the biggest cost — and you don’t need food at all. The most valuable thing is a host willing to donate space. He described a recent Atlanta PHP meetup with nothing but a few six-packs and some leftover pastries that worked out perfectly fine.

The conversation turned to the eternal challenge of timezones and async collaboration. Both agreed async is great for inclusivity, especially for non-native English speakers, but some things simply can’t happen asynchronously with the same quality. In-person and real-time contact build trust and relationships in ways text alone can’t, whether for a company, a user group, or the Foundation’s own special interest groups.

Designers, Docs, and Making It Easier to Contribute

On what the Foundation can do to help, Matt suggested more universally accessible, perennial resources rather than blog posts that go stale. PHP’s own “how to contribute” page is out of date and language-focused. He proposed the Foundation website host a broader contribution guide that links out to each community’s canonical resources.

He noted the reality that anything on php.net mentioning a sub-community risks drama, so the Foundation website is a better place to start, prove things out, and eventually propose polished changes to php.net. They closed by celebrating internals contributors, infrastructure heroes like Derick Rethans and Joe Ferguson, and every kind of skill — social media included — that the PHP ecosystem needs.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

This podcast is made a little better thanks to our partners

https://www.epidemicsound.com/

Youtube Channel

Got feedback? Join us on Discord at discord.phparch.com

The post PHP Foundation Community Hour Podcast 2026.09.10 appeared first on PHP Architect.

<span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span>

In this episode, Scott talks with Nia Luckey about her new book “Trust Hacked: What Firewalls, Failures, and the Frontlines Taught Me About Trust”.

Links:

Nia’s Links:

Scott’s Links:

PHP Architect Social Media:

Subscribe to our magazine: https://www.phparch.com/subscribe/

This podcast is made a little better thanks to our partners.

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/

#phpc #php #communityCornerPodcast #podcast #phptek

The post Community Corner: Trust Hacked with Nia Luckey appeared first on PHP Architect.

<br />

Hosts: Eric Van Johnson & Joe Ferguson

New Intro, New Scenes, and a Last-Second Co-Host

The pair caught up on client work: Joe pulled off an Elastic Beanstalk environment flip that nobody noticed (which is exactly how you want those to go), while Frank got thrown right under the bus for deleting the wrong database. Fortunately, it wasn’t production, and the conversation turned into an appreciation session for point-in-time recovery on AWS RDS and DigitalOcean’s managed databases, both of which have saved plenty of bacon during cowboy-hat coding sessions.

The PHP Foundation Community Podcast

Eric and Joe used the moment to clear up a common misconception: people often conflate PHP internals with the Foundation, but they are not the same thing. The Foundation pays people to work on internals rather than steering the language itself. Its whole reason for existing is to get structure and funding around an old open-source project that billion-dollar companies have built empires on while contributing little back downstream.

They also touched on recent Foundation board turnover: Roman’s term ended, and he’s rotating off, with Brent Roose joining as JetBrains’ representative — a great fit given Brent’s reach and the volume of PHP content he pushes out.

Unlocking the PHP Architect Magazine Back Catalog

Big news for existing accounts: John has opened up everything published before 2022 to anyone with an account on the system, even without an active subscription. Log in, head to magazines, and check what you now have access to. The team also reminded listeners that the magazine pays every contributor, that they’ve built a solid roster of regular columnists, and that PHP Architect is a consulting group available to augment teams, evaluate systems, and more.

Where Developers Fit in an AI World

But Joe was candid about his concerns too: AI feels force-fed in a way CSS or JS frameworks never did, with a real fear of being replaced by “a bunch of Claude agents in a trench coat.” He raised ethical and environmental concerns, pointing to accusations about his own city’s AI data center and the ripple effects on hardware — RAM prices spiking 400–500%, with Apple reportedly paying far more for iPhone RAM, a cost that always flows back to consumers.

Eric compared the AI moment to crypto: a genuinely good technology released to the masses too soon, leading to misuse and eventual regulation. He shared a concrete win, though — using Claude to single-handedly bring a Laravel project shelved since COVID up to date, then using it to generate effort estimates (roughly three years of work) that helped set realistic expectations with a client who didn’t want to hear it. The pair debated whether those estimates accounted for AI-assisted velocity and stressed the importance of guardrails — especially for juniors, since even skilled devs leave S3 buckets open and AI is dangerously confident in its word guessing.

TypePHP: Interesting, But Not for Everyone

Joe pointed out the bigger practical problem: there’s far more talk about TypePHP than actual code being written in it, and it’s clearly geared toward long-running CLI processes rather than web requests. That excludes the kind of PHP most developers actually write, and as Nuno noted in the chat, it isn’t going anywhere until it works with Laravel and the rest of the ecosystem. The hosts agreed the real value would be extracting any gains and folding them back into native PHP, à la HHVM/Hack, and noted transpiling already solves the “I want a different syntax” itch.

Joe also pushed back on the “runs everywhere” selling point, arguing that Docker and Podman containers already make PHP CLI tools trivially portable — better than PHARs ever were. Eric landed on a mature take: he wants PHP everywhere and is happy to see it evolve, but he’s come to terms with the fact that he won’t personally use every direction it grows, TypePHP included.

ElePHPants, Laracon Archives, and Free Talks

Eric also highlighted the new Laracon Archive project, which collects Laracon conference talks across regions (US, EU, Online, India) with a clean year-by-year interface — great work for anyone who tries to manage conference content. He closed by plugging phptech.tv, which hosts PHP Architect conference talks, including a batch of free talks and even a full free conference this year, with the same back-catalog-unlock model as the magazine.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

This podcast is made a little better thanks to our partners

Displace

Infrastructure Management, Simplified

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

https://www.epidemicsound.com/

Youtube Channel

Got feedback? Join us on Discord at discord.phparch.com

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