php[podcast] episodes from php[architect]

PHP Podcast – August 20, 2026

Hosts: Joe Ferguson, Sara Golemon & Holly Schilling

Shirley MacLaine is the answer — but what’s the question? RAM prices went up 500%, GitHub fell over for eight hours, and the crew figured out how you can actually contribute to PHP. Glasses optional.

Shirley MacLaine, Green Room Shade, and the Show’s New Normal

The episode opens with Joe flustered — not because it’s a “flustered day,” but because there’s shade being thrown in the green room backstage chat. Rather than spoil the drama, the crew turns a mysterious green-room answer into a running bit: “Shirley MacLaine” is the answer, and listeners are invited to submit what the question was. It’s declared the first round of PHP Architect’s Jeopardy, complete with its own Easter egg sound cue.

Joe also lays out where the show is heading. Eric and John took over the podcast the previous week to relive their glory days, and the plan is for the old guys to step back to roughly one episode a month. Joe and Sara are working on something to fill one slot, another mystery show is in the works pending signed contracts, and Alive and Kicking is confirmed still alive and kicking after a great recent episode with Derek. Joe also plugs the PHP 8.6 Beta 1 tag and Scott Keck-Warren’s PHP Community Podcast interview with release managers Daniel Scherzer and Matteo Bacotti.

The RAM Apocalypse: 500% in Twelve Months

The big topic of the week is the ongoing memory and chip crisis. Memory prices have climbed 500% in twelve months, and the crew commiserates about the parts they wish they’d bought bigger. Sara explains the brutal math: you can’t build a semiconductor fab fast enough — two or three years minimum — and by the time one comes online nobody knows if we’ll have overproduction or a burst bubble. Worse, Sara notes that essentially every RAM stick through the end of 2027 is already accounted for and sold to vendors.

The ripple effects are everywhere. Console prices are going up instead of down late in their cycle, with next-gen consoles projected to start at $1,000 or more. The hobbyist single-board computer market is getting crushed — Pine64 announced they’re stepping back from making hardware, and a Raspberry Pi 5 that debuted cheap now runs over 100 pounds. Holly’s new PC, bought at the start of 2025, ended up shipped 3,000 kilometers the wrong way to California and is stuck awaiting import paperwork, leaving her leaning on a laptop and some now-precious Raspberry Pi zeros.

The nostalgia gets thick as the crew reminisces about DIP chips, EDO RAM, Pentiums, Epson 486s, Tandy 1000s, and the TRS-80. Special venom is reserved for Packard Bell (“utter freaking trash”) and Gateway 2000’s cow-pattern branding — which Sara confirms sold better in Wisconsin than anywhere, though hay bales in a Berkeley storefront still boggle the mind. A chat comment about technicians de-soldering and reballing BGA RAM chips becoming economically viable gets a hearty “absolutely.”

Memory-Aware Development and Why PHP 7 Doubled Down

Bringing the RAM crisis back to PHP, Joe wishes more developers were aware of how their applications consume and release memory — a lesson he credits to learning enough C back in the day, where you have to manage memory yourself. He connects sloppy memory awareness to the N+1 query problems web developers keep tripping over.

Sara drops a great deep dive: a significant reason PHP 7 was roughly twice as fast as PHP 5 was changes in the memory layout. Every variable became referenced by one fewer pointer, and while eight bytes sounds trivial, every level of indirection adds time across every single instruction and access. Sara adds the CPU-level detail — one layer of indirection can be a single instruction on most architectures, but adding a second layer can push a lookup from one instruction to three.

That leads into a warm tangent about learning C to become game developers. Sara’s evergreen joke: “I’m going to be a game developer” is the programmer’s version of “I’m going to buy a bar.” Great people, brutal hours, endless competition, and the reality of hitting spacebar 400 times to figure out why you can phase through a wall. The cat-reading-the-paper “I should buy a boat” meme makes an appearance to seal it.

The GitHub Outage and the Monoculture Problem

Monday’s eight-hour GitHub outage hit the crew directly. Holly couldn’t use a site that only offered “log in with GitHub,” and Joe got kicked out of his CLI auth session mid-PR with no way to re-authenticate. To GitHub’s credit, they published an incident update and a follow-up blog post: a service auto-scaled so aggressively to handle network traffic that the sidecar and supporting services couldn’t keep up, bringing the whole thing down.

The conversation turns to whether this is self-inflicted. Joe recalls GitHub’s pre-Microsoft, gold-standard reliability and wonders aloud how much the decline lines up with Copilot’s arrival and internal AI adoption, with uptime reportedly slipping below a single nine at points. Sara defends them somewhat — the number of actions, CPU cores, and pull requests has genuinely hockey-sticked, partly because AI has emboldened people who previously wouldn’t have opened a PR. But as Joe puts it, the call is coming from inside the house, since GitHub itself has been pushing AI.

On alternatives, Joe says the least-jarring migration for PHP Architect’s clients would be self-hosting GitLab, since GitHub Actions and GitLab runners are nearly identical in syntax — Atlassian’s Bitbucket, by contrast, is a bridge too far, mostly because the entire ecosystem assumes you’re on GitHub. Sara names this the core problem: monoculture. The crew discusses package mirrors, local caches, 12-factor thinking, and Composer’s support for custom mirrors, all while remembering the PHP repo intrusion years ago that came from an unmaintained self-hosted Git server. The takeaway: owning your pipeline end-to-end is the only way an outage can’t stop you — and Joe teases spinning up a self-hosted GitLab now that “the boss” (Sara) has signed off.

How to Contribute to PHP (and Handling Security Reports)

The crew highlights two PHP Foundation blog posts. First, Matt Stauffer’s “How to Contribute to PHP,” adapted from a talk he gave at Atlanta PHP. It goes well beyond “learn C,” clearly separating the PHP project, the PHP ecosystem, and the Foundation, and lays out approachable on-ramps: testing pre-releases (PHP 8.6 Beta 1 is out, Beta 2 lands next week), improving documentation, and writing tests — which, spoiler, are written in PHP, not C, using PHP’s own test format that’s simple enough to learn from any single example.

Other contribution paths include triaging and reviewing issues across PHP repositories — invaluable work that frees core developers from wading through AI-generated slop bug reports — and participating in internals via the well-documented mailing list process, up to and including running for release manager (8.7 managers will be needed before you know it). Sara points folks to discord.phpc.chat for the PHP Discord, with dedicated Internals and Foundation channels for anyone the mailing list intimidates.

Second, Sebastian Bergmann’s “So you received a security report. Now what?” is a jump-around reference for application developers rather than a front-to-back read, walking through roughly ten steps to triage, validate, and resolve reported issues the right way. Sara shares a real-world example from mobile: a flagged package that was only exploitable on a rooted device with an actively hostile package installed alongside it — a very different risk profile than a SQL injection on an API endpoint. Cue reminiscing about writing SQL against Access databases over ODBC from PHP (and Perl) back in the 90s, and Joe’s advice for handling any security report: don’t panic, and always know where your towel is.

Links from the show:

PHP Tek 2027 — April 27–29, 2027 in Chicago; early bird tickets & hotel available now

PHP Tek 2027 CFP

Audio versions of the podcast at phparch.com

Join us live on Discord at discord.phparch.com

PHP Discord — discord.phpc.chat

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

Memory prices climb 500% in 12 months

So You Received a Security Report. Now What?

How to Contribute to PHP

Shirley MacLaine

Host:

Joe Ferguson

Mastodon: @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

Displace



Infrastructure Management, Simplified

Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease.

https://displace.tech/





OurCVEs

Your security posture, on autopilot with OurCVEs



CodeRabbit



Cut code review time & bugs in half instantly with CodeRabbit.



PHP Architect Consulting

Your PHP codebase deserves a partner, not a contractor

PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on

https://www.phparch.com/consulting/



Music Provided by Epidemic Sound

https://www.epidemicsound.com/

Join Us Live Next Week

Youtube Channel

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

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

In this episode, Scott talks with Daniel Scherzer, release manager for PHP 8.5 and PHP 8.6, about the bug-fix release cycle, partial function application coming in 8.6, and his upcoming talks at Longhorn PHP on what’s new in 8.6 and building PHP extensions in Rust.

Links

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

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

Daniel’s Link

https://scherzer.dev/

LinkedIn – https://www.linkedin.com/in/daniel-scherzer-520539263/

Scott’s Links

Website – https://scott.keck-warren.com/

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

LinkedIn – https://www.linkedin.com/in/scott-keck-warren-91689810/

Mastodon – https://phpc.social/@scottkeckwarren

PHP Architect Social Media:

X: https://x.com/phparch

Mastodon: https://phparch.social/@phparch

Bluesky: https://bsky.app/profile/phparch.com

Discord: https://discord.phparch.com

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

Partners

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

Displace

Infrastructure Management, Simplified

Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease.

https://displace.tech/

PHPScore

Put Your Technical Debt on Autopay with PHPScore

https://phpscore.com/

CodeRabit

CodeRabbit – Cut code review time & bugs in half instantly with CodeRabbit.

https://www.coderabbit.ai/

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

#phpc #php #communityCornerPodcast #podcast #jscpd

The post Community Corner Podcast: PHP 8.5 + 8.6 Release Manager Daniel Scherzer appeared first on PHP Architect.

PHP Podcast – August 13, 2026

Hosts: Eric Van Johnson & John Congdon

Eric and John reunite after weeks apart to talk Laracon in Boston, more diverse voices coming to this time slot, CPX finally giving PHP an npx, a stripped-down PHPStorm Light, and PHP Tek’s extended CFP.

Stepping Back to Make Room for More Voices

Eric and John open by explaining a shift in the show: they’re not disappearing, but they’re stepping back a little so more people from the PHP Architect team can take the mic. As John put it, the goal is “more diverse voices of the community,” and folks like Joe, Sarah, and Holly have been stepping into this time slot.

Eric and John have committed to appearing at least once a month, since they have the most holistic view of what’s happening across the company. When they’re on, expect the “inside baseball” episodes — the behind-the-scenes look at what PHP Architect is up to. The rest of the time, this slot will keep going with other hosts, so the show never goes dark.

They also reminded listeners there’s both a live stream and an audio RSS feed. Some folks apparently only recently discovered the audio version, while longtime audio listeners never realize the show streams live. Either way, head to phparch.com, click on podcasts, and you’ll find every way to subscribe.

Eric’s Laracon Boston Recap

Eric attended Laracon in Boston and, as always, has a love/hate relationship with it. On the plus side, it’s where he catches up with a lot of friends, and the talks were solid — Pauline Voss gave a great presentation on JJ (Jujutsu) and atomic commits, and Nuno showed off Pest 5. Eric noted the framework itself is moving much slower now, which is actually a good thing for anyone running a business on it, even if it makes the conference less essential-viewing than it once was.

The venue was industrial and good-looking with a fantastic stage setup, but seating was a genuine problem this year. Eric arrived late to Nuno’s talk and there was nowhere to sit; the team scrambled to bring in more chairs. When it rained on day two, they ran out again. Despite that, staying in the same hotel as folks like Eric Barnes, TJ, Jake Bennett, and Michael Dorinda made for the kind of hallway-and-breakfast camaraderie he values most.

Eric also hit the social events he usually skips — he sat out dodgeball (bad knees, slip-on shoes, and being a big target), but went to the Laracon Prom, which required an RSVP and an approved request. It turned out to be way cooler than expected, with people fully decked out, DJs, and an after-party plus a VIP dinner where Laravel’s marketing team worked the room. He also caught up with folks like Matthew Weier O’Phinney of Zend/Perforce and had a chat with Taylor.

Running the Laravel Magazine Site and Taylor’s Blessing

Eric shared that PHP Architect is now running the Laravel Magazine website, which previously belonged to Marijn (Marion) Pop. He’s been publishing tutorials, keeping things current, and making changes to the site he’s proud of. The articles are short, quick reads — and one of the Laravel wrap-up pieces mirrors the same article on the PHP Architect site.

At the after-party dinner, Eric took the opportunity to run the name past Taylor directly, since he wasn’t sure the original owner had ever gotten official approval to use the Laravel name for a magazine. Taylor’s response was essentially “that’s fine, don’t worry about it” — so Laravel Magazine lives on. Eric even set up a newsletter signup, though he admits he’s not sure yet whether he’ll actually send a newsletter.

CPX — A PHP-World npx

One of Eric’s favorite discoveries from Laracon was CPX, essentially the PHP equivalent of npx. Just as npx lets you run JavaScript packages without installing them into a specific project, CPX lets you run tools without a global composer install or a per-project dependency. Eric already swapped his global PHP CS Fixer and Laravel Pint setup over to CPX aliases, so he now always runs the latest version without dependency headaches.

John pushed back a bit, pointing out that tools like PHP unit and Rector usually live in your vendor directory anyway because your CI pipeline depends on them. Eric agreed that’s a valid workflow, but framed CPX as ideal for the occasional-use tools and for lowering the barrier for people outside the PHP world who want to dip in without fully committing. Chat chimed in with Rector as a great CPX use case, and they walked through examples like spinning up a fresh Laravel app.

Laravel LSP and PHP Storm Light

Eric was genuinely excited that Laravel now has its own Language Server Protocol. Most IDEs had already built their own Laravel-aware workarounds, but for Eim’s Neovim setup, the LSP finally makes things like jumping from a route to the view it points to work correctly — something PHP Storm had solved long ago but Vim hadn’t.

He also spotted something called PHP Storm Light at the JetBrains booth: a trimmed-down, experimental build with faster startup, lower memory, and fewer features. It’s available through the Toolbox app as an EAP, so it’s free and explicitly experimental. John, who’d been hitting memory limits in regular PHP Storm, decided to install it on the spot, and Joe mentioned using it for one-off file edits — sparking a conversation about whether it fills the gap left by JetBrains’ old standalone editor.

PHP Tek CFP Extended + Ticket Options

John announced that the PHP Tek call for speakers has been extended through October 31st. The team experimented with opening the CFP very early this year to help attendees whose fiscal-year approvals depend on a locked schedule, but the community felt it was too early to know what would be relevant next April. So they extended the window and made cfp.phptek.io point straight to the call for presenters (thanks to a suggestion from A. Woods).

On tickets, they’ve broken out a bundle that includes hotel nights so attendees can hand their boss a single lump-sum figure (airfare not included). There are also food-and-beverage-only tickets for partners and kids, single-day track options, and dedicated days for Laravel, JavaScript, and DevOps — one track each, with the other two tracks running the usual PHP Tek content. John flagged a possible issue with DevOps being the default CFP track, since it’s pulling in a flood of generic, seemingly AI-submitted talks he’ll need to sort through.

Links from the show:

PHP Tek — CFP extended through October 31, conference + hotel bundle available

PHP Tek Call for Presenters

OurCVEs — watch your repos and servers for CVEs

Host:

Eric Van Johnson

X: @shocm

Mastodon: @eric@phparch.social

Bluesky: @ericvanjohnson.bsky.social

PHPArch.me: @eric

John Congdon

X: @johncongdon

Mastodon: @john@phparch.social

Bluesky: @johncongdon.bsky.social

PHPArch.me: @john

Streams:

Youtube Channel

Twitch

Connect & Hire

PHP Architect Website

Twitter/X

Mastodon

Hire PHP Developers

Looking to hire PHP developers? Email support@phparch.com – Eric, John, and the team are available for consulting, team augmentation, direction, code review, and even mobile development work.

Partner

This podcast is made a little better thanks to our partners

Displace



Infrastructure Management, Simplified

Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease.

https://displace.tech/





OurCVEs

Your security posture, on autopilot with OurCVEs



CodeRabbit



Cut code review time & bugs in half instantly with CodeRabbit.



PHP Architect Consulting



Your PHP codebase deserves a partner, not a contractor

PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on.

https://www.phparch.com/consulting/



Music Provided by Epidemic Sound

https://www.epidemicsound.com/

Join Us Live Next Week

Youtube Channel

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

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

PHP Podcast – August 6, 2026

Hosts: Joe Ferguson, Sara Golemon & Holly Schilling

A sick kitten steals the show, Sara loses a fight with her smart lights, PHP 8.6 beta is almost here, and the crew argues about roadmaps, deprecations, and why you shouldn’t be a meat proxy.

Cats, Ice Cream, and Bobbleheads

The episode opened with the usual chaos: Holly’s kitten Rosie made a full appearance, having spent the week battling a chest infection that turned into a sinus and ear infection and threw off her balance. Three vet visits later, Rosie was recovering but very cuddly — and apparently convinced Holly’s headset mic was a cat toy. Sara, catless but armed with ice cream, argued that ice cream beats cats because there’s no poop to clean up.

The conversation spun into merchandise ideas after Eric dropped a photo of a bobblehead in the Discord. The crew riffed on 3D-printing speaker action figures and bobbleheads for the conference, with Holly getting Eric on record that it “would not be expensive” — a statement immediately screenshotted for posterity. Sara and Holly quickly reminded everyone that multicolor prints are their own painful challenge, and someone with Warhammer 40k painting patience would be required.

PHP 8.6 Beta on the Horizon

With 8.6 beta 1 landing a week out, the hosts walked through the highlights from the Stitcher.io “what’s new” write-up. Sara was excited about partial function application finally arriving, though Holly isn’t thrilled with the `…` syntax — but couldn’t propose a better one either. They dug into an earlier, unshipped design that used `$1`/`$2` positional placeholders (similar to Swift), and Joe kept circling back to Python-style named arguments before admitting he wasn’t entirely sure he was describing the right feature.

They also covered read-only property defaults (a natural follow-on to 8.4’s property hooks on interfaces), the new polling API that’s largely future-facing for threading and concurrency work, the new `clamp()` function, and a long-overdue `Duration` class. Holly repeatedly questioned why something like `clamp()` needs to be in the language at all, with Sara conceding the point but noting PHP is a “kitchen sink language” and that ship has sailed. For `Duration`, Sara made the case that it genuinely belongs in core because it’s tied to the timezone knowledge baked into the underlying date/time library.

Deprecations and the Two Populations of PHP

Joe pulled up numbers comparing deprecation RFCs across recent versions — roughly 28 proposals for 8.6, 46 for 8.5, 26 for 8.4, just six for 8.3, and none actually voted on for 8.2 (which Sara guessed lined up with Nikita stepping back to work on LLVM, back when deprecations were called “Nikita’s hit list”). Many of the 8.6 deprecations, organized by Gina P. Banyard, aim to free up words to become reserved keywords in future versions.

The `list()` deprecation came up as a sore spot: Holly would love to see it gone and never uses it in new code, while Joe worries the blast radius across legacy codebases is enormous. That led Sara to articulate the core tension: there are two very different populations of PHP users — the ones aggressively upgrading and adopting new features (the podcast’s audience), and the ones who just want to run their WordPress site without the language shifting under them. Both groups matter, and the language has to push forward without needlessly breaking the second group.

The Roadmap Debate

Building on deprecations, the crew wished aloud that PHP had something resembling a roadmap — not set-in-stone dates, but broad aims like “a feature like X might justify bumping to 9.” Joe suggested borrowing from game dev studios, who publish colorful roadmaps with rough years instead of hard dates and don’t crucify anyone when things slip. Holly noted that even the AI she was workshopping a blog post with warned that PHP internals doesn’t handle the word “roadmap” well and to assume any such proposal will fail.

Sara, invoking her “lawyer’s advice” not to mention it was a recent meeting topic, pointed out the practical wrinkle: the foundation’s paid developers are largely self-directed, and no one is telling them what donors want them to build. Still, everyone agreed a shared set of goals would be valuable. Holly and Sara also gave a shout-out to the unsung, unsexy work — documentation, triage, bug fixing — that keeps the lights on, and to the foundation’s first quarterly progress report for showing what contractors are actually doing.

Longhorn PHP and Travel Logistics

Holly announced her Longhorn PHP talk, “That’s Your Website, Not Your Mobile App,” slotted at 2:30 in Austin on October 15–16. The talk is a venting session about her pet peeve: teams wrapping a Laravel/React/whatever website in a native shell and shipping it as an app without bridging the model differences — regardless of tech stack. She noted it’s her first time at Longhorn, though she recently spoke at a Chicago mobile developers meetup exactly one week shy of ten years after her last appearance there.

The travel talk sprawled into a would-be road-trip convoy (picking up Joe in Memphis, A. Woods from New York, and even attempting to ferry Sara’s car across the ocean), plus a tangent on how absurdly expensive Amtrak is compared to flying — versus Sara’s 20-euro monthly rail pass in Portugal that covers the entire length of the country.

Don’t Be a Meat Proxy

The show closed on Niklas Gruhn’s blog post “Don’t Be a Meat Proxy,” which argues against copy-pasting raw AI output at other humans. Joe described his own workflow: read the AI feedback, condense and distill it, rewrite it, and clearly label anything unvetted (robot emoji included) so teammates know he hasn’t verified it yet. Sara pushed the point harder — if you’re just regurgitating what Claude or Gemini said, the person asking could have done that themselves, so you’re not adding value.

Holly complicated it with real-world nuance: some coworkers ask questions they could’ve answered themselves, then call you rude when you give a condensed answer and keep poking at its edges. The crew acknowledged a whole gradient exists — from “let me Google that for you” territory to genuine “what’s the best way to approach X” conversations that aren’t fact lookups. Sara, self-professed AI hater, admitted the balance has shifted toward “just search it” because AIs are genuinely good at search — with plenty of deep irony noted about machines being good at reading and grokking information humans don’t want to. Bonus: Holly praised naming xAI’s bot “Grok” as genuinely clever.

Links from the show:

PHP Tek 2027 — Early bird tickets and hotel block available

PHP Tek CFP — Open until the end of the month

Longhorn PHP — October 15–16, Austin

What’s new in PHP 8.6 (Stitcher.io)

PHP Foundation’s quarterly report for Q2 2026
Eric’s Laracon 2026 wrap up
PHP Podcast Subscribe Page

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.

Partner

This podcast is made a little better thanks to our partners

Displace



Infrastructure Management, Simplified

Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease.

https://displace.tech/





OurCVEs

Your security posture, on autopilot with OurCVEs



CodeRabbit



Cut code review time & bugs in half instantly with CodeRabbit.





PHP Architect Consulting



Your PHP codebase deserves a partner, not a contractor

PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on

https://www.phparch.com/consulting/



Music Provided by Epidemic Sound

https://www.epidemicsound.com/

Join Us Live Next Week

Youtube Channel

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

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

In this episode, Scott talks with Andrey Kucherenko, creator of jscpd, about why copy-pasted code is an anti-pattern, how jscpd detects duplicate code across dozens of languages, and how the tool has evolved to work inside agentic coding workflows.

Links:

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

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

Andrey’s Links:

jscpd – https://jscpd.dev/

Scott’s Links:

Website – https://scott.keck-warren.com/

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

LinkedIn – https://www.linkedin.com/in/scott-keck-warren-91689810/

Mastodon – https://phpc.social/@scottkeckwarren

PHP Architect Social Media:

X: https://x.com/phparch

Mastodon: https://phparch.social/@phparch

Bluesky: https://bsky.app/profile/phparch.com

Discord: https://discord.phparch.com

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

Partners

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

Displace

Infrastructure Management, Simplified

Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease.

https://displace.tech/

PHPScore

Put Your Technical Debt on Autopay with PHPScore

https://phpscore.com/

CodeRabit

CodeRabbit – Cut code review time & bugs in half instantly with CodeRabbit.

https://www.coderabbit.ai/

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

#phpc #php #communityCornerPodcast #podcast #jscpd

The post Community Corner: JSCPD with Andrey Kucherenko appeared first on PHP Architect.