PHP Alive And Kicking: Episode 17 - TJ Miller
๐ **Source:** [PHP Alive And Kicking: Episode 17 - TJ Miller](https://www.youtube.com/watch?v=nzeTSCQLd3M)
> [!note]+ Document Notes
> tags: [php, laravel, prism, ai-integration]
> author: PHP Architect
> source: YouTube
> reference: [https://www.youtube.com/watch?v=nzeTSCQLd3M]
> date created: 2024-12-03 14:30
>
> # ๐ท๏ธ Title: PHP Alive And Kicking: Episode 17 - TJ Miller
>
<!-- deep-read:sections start -->
## ๐งฐ Action Inbox
- [H1] Consider PHP Foundation AI integration opportunities โ Prism success shows demand #ai #community
- [H2] Research local model deployment with Ollama โ reduce token costs for testing #development #cost-optimization
- [H3] Pitch Laravel-focused AI talk for conferences โ bridge PHP/JS communities #speaking #outreach
## ๐งญ Table of Contents
- [๐ Summary](#-summary)
- [๐ Main Content](#-main-content)
- [๐๏ธ Notes](#๏ธ-notes)
- [๐ References](#-references)
- [๐ฃ๏ธ Paraphrase](#๏ธ-paraphrase)
- [๐ฐ Newsletter](#-newsletter)
- [โ
Action Items](#-action-items)
- [๐งช Hypotheses](#-hypotheses)
- [๐ Methodology](#-methodology)
- [โ Questions](#-questions)
- [๐ฎ Future Research](#-future-research)
- [๐ก Implications](#-implications)
- [๐ง Learning Styles Assessment](#-learning-styles-assessment)
- [๐ Accessibility Assessment](#-accessibility-assessment)
- [๐ DEIB Assessment](#-deib-assessment)
- [โ
Logical Validity](#-logical-validity)
- [๐ก๏ธ DARVO Analysis](#-darvo-analysis)
- [๐ฏ Conclusion](#-conclusion)
### ๐ References
- [Prism - AI SDK for PHP](https://github.com/prism-ai)
- [Geocodio](https://geocodio.com)
- [PHP Tech Conference](https://phptech.dev)
## ๐ Summary
- TJ Miller discusses his journey from HTML/CSS to PHP, creation of Prism AI SDK, and current role at Geocodio
- Prism emerged from need for Laravel-native AI tooling, inspired by Vercel's AI SDK
- PHP community faces image problem affecting junior developer recruitment
- Strong emphasis on community building and conference participation as key to PHP's growth
- Technical discussion covers Neo Vim configuration, local model testing, and multi-provider AI integration
## ๐ Main Content
TJ Miller, creator of the Prism AI SDK and developer at Geocodio, shares his evolution from basic web development to building sophisticated AI integrations in PHP. Starting with simple HTML templating needs in high school, Miller discovered PHP's power for dynamic content generation and database connectivity.
His journey led through WordPress development, a brief consideration of Ruby on Rails, and ultimately deep commitment to Laravel. The turning point came when Taylor Otwell mentioned wondering what a Laravel version of Vercel's AI SDK would look like, sparking the creation of Prism.
The conversation addresses PHP's ongoing image problem, particularly in recruiting junior developers who gravitate toward JavaScript and Python bootcamps. Miller advocates for positive messaging about PHP's capabilities rather than defensive responses to "is PHP dead" narratives.
Technical insights include strategies for managing AI token costs through local model testing with Ollama, the importance of API-first design in developer tools, and the challenge of supporting multiple AI providers with evolving APIs.
## ๐๏ธ Notes
#### โฑ๏ธ [00:00](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=0) โ [H1] Introduction and Setup
- Key idea: Live podcast format with Discord integration for audience questions
- Evidence: "Please head over into our discord. You can ask questions of our guests"
#### โฑ๏ธ [02:30](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=150) โ [H2] TJ's PHP Origin Story
- Key idea: Started with basic templating needs in high school web development
- Evidence: "I wanted a way to templatize some of the work instead of having to copy and paste the sidebar, the header"
#### โฑ๏ธ [05:15](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=315) โ [H2] The Laravel Discovery
- Key idea: Laravel transformed Miller's perception of what PHP could be
- Evidence: "I was blown away. I'm like you could write PHP this way. That changed everything for me"
#### โฑ๏ธ [08:45](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=525) โ [H2] Vim/Neovim Mastery
- Key idea: 20-year commitment to Vim has created deep muscle memory dependencies
- Evidence: "There are key bindings that have been in there for 20 years that are so ingrained in muscle memory"
#### โฑ๏ธ [12:30](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=750) โ [H1] Prism Genesis Story
- Key idea: Prism emerged from Taylor Otwell wondering about a Laravel version of Vercel's AI SDK
- Evidence: "He said in passing, 'I wonder what a Laravel version of that would look like' and the API just kind of hit me"
#### โฑ๏ธ [15:20](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=920) โ [H2] API-First Development Philosophy
- Key idea: Developer experience drives design decisions before implementation
- Evidence: "It was very much API first and then backfilling the functionality to meet that API"
#### โฑ๏ธ [18:10](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=1090) โ [H2] Geocodio Employment Reality
- Key idea: Prism is passion project, not full-time income source
- Evidence: "I chew through a ton of tokens every month running tests and experiments"
#### โฑ๏ธ [21:45](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=1305) โ [H2] Token Cost Management Strategy
- Key idea: Local models with Ollama reduce development costs significantly
- Evidence: "The OpenAI GPT-O OSS model is very impressive. So for building out integrations you can get pretty decent mileage"
#### โฑ๏ธ [25:30](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=1530) โ [H1] PHP's Image Problem Analysis
- Key idea: PHP suffers from perception issues affecting junior developer recruitment
- Evidence: "PHP suffers from an image problem. That's where JS is snagging everyone at the top of the funnel"
#### โฑ๏ธ [29:15](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=1755) โ [H2] Negative Messaging Impact
- Key idea: "Is PHP dead" posts harm perception even when defending PHP
- Evidence: "People are just seeing the 'is PHP dead' and assuming PHP is dead. They're not going to open it up and read"
#### โฑ๏ธ [33:20](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=2000) โ [H2] Demographic Challenge
- Key idea: PHP conferences show concerning age demographics
- Evidence: "They asked anyone over 35 to put their hands up and pretty much the whole room put their hands up"
#### โฑ๏ธ [37:45](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=2265) โ [H2] Technology Accessibility Revolution
- Key idea: Modern PHP frameworks make cutting-edge technologies accessible
- Evidence: "With Prism, now you're not bound to Python. You want to work with AI, not a problem working in PHP"
#### โฑ๏ธ [41:30](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=2490) โ [H1] Community as Core Value
- Key idea: PHP community relationships drive long-term engagement and innovation
- Evidence: "The thing that gets me most excited about PHP is the community. Every time I go to conferences I come back so inspired"
#### โฑ๏ธ [44:10](https://www.youtube.com/watch?v=nzeTSCQLd3M?t=2650) โ [H2] Conference Accessibility Culture
- Key idea: PHP conferences maintain inclusive, approachable environments
- Evidence: "There's no barrier between speakers and general public. Everyone mingles and there's no clicks"
## ๐ References
- [PHP Architect Magazine](https://phparchitect.com)
- [Prism AI SDK](https://github.com/prism-ai)
- [PHP Tech Conference](https://phptech.dev)
- [Geocodio API](https://geocodio.com)
- [Laravel Framework](https://laravel.com)
- [Ollama Local Models](https://ollama.ai)
## ๐ฃ๏ธ Paraphrase
- TJ Miller's path to PHP began with simple templating needs in high school, evolving through WordPress development until Laravel revealed PHP's true potential for elegant code architecture
- The Prism AI SDK originated from Taylor Otwell's casual suggestion about creating a Laravel equivalent to Vercel's AI SDK, leading to API-first development focused on developer experience
- PHP faces significant challenges in attracting junior developers due to perception issues and negative messaging, requiring positive community initiatives and better marketing of modern capabilities
## ๐ฐ Newsletter
**TJ Miller Shares Prism AI Journey and PHP Community Insights**
This week's episode features TJ Miller, creator of the popular Prism AI SDK for Laravel, discussing his evolution from basic web templating to building sophisticated AI integrations in PHP. Miller's story demonstrates how modern PHP frameworks enable developers to work with cutting-edge technologies without leaving their preferred ecosystem.
Key takeaways for WordPress developers include strategies for managing API costs through local model testing and the importance of community engagement for professional growth. Miller's emphasis on API-first design offers valuable lessons for plugin and theme development.
The discussion also addresses PHP's demographic challenges and the need for positive messaging about the language's modern capabilities, particularly relevant for agencies positioning themselves in the current market.
Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/)
## โ
Action Items
#### DevRel
- Developer advocacy: Promote positive PHP messaging in content and presentations
- Education: Create workshops bridging traditional PHP and modern AI integration
- Developer experience: Document local model testing workflows for cost-effective development
- Developer marketing: Position PHP as modern choice for AI/ML applications
- Community management: Foster inclusive conference environments that welcome newcomers
#### OSPO
- Policy & Governance: Evaluate AI SDK licensing compatibility with enterprise requirements
- Software Inventory: Track AI integration dependencies in SBOM processes
- Developer Support: Provide guidance on managing API costs and local model deployment
- Community Engagement: Support PHP Foundation AI initiatives and related projects
#### Community
- Contributors: Support Prism development through testing and documentation
- Sponsors: Consider sponsoring key infrastructure projects like Prism
- Ecosystem: Coordinate AI integration standards across PHP frameworks
#### WordPress
- Core AI: Evaluate Prism integration possibilities for WordPress AI features
- Community: Address age demographic concerns through targeted junior developer outreach
- Documentation: Create guides for modern PHP development practices
- Marketing: Develop positive messaging strategies highlighting WordPress PHP advantages
## ๐งช Hypotheses
- Local model testing with Ollama can reduce AI development costs by 70-90% during prototyping phases
- API-first design methodology produces more intuitive developer experiences than implementation-first approaches
- Positive PHP messaging increases junior developer interest more effectively than defensive responses to criticism
- Conference participation significantly increases long-term community engagement and project contributions
### ๐ Methodology
- Compare token costs between cloud and local model development workflows across multiple projects
- A/B test different messaging strategies in PHP recruitment materials and measure application rates
- Survey conference attendees on community engagement levels before and after event participation
- Analyze developer experience metrics for API-first vs implementation-first package designs
### โ Questions
- How can PHP better compete with JavaScript/Python bootcamps for junior developer mindshare?
- What specific features would make Prism attractive for WordPress core AI integration?
- How might demographic challenges affect PHP's long-term sustainability and innovation capacity?
### ๐ฎ Future Research
- Quantitative analysis of PHP community age demographics across different regions and specializations
- Comparative study of AI SDK adoption patterns across different programming language ecosystems
- Investigation of local model performance characteristics for different development use cases
### ๐ก Implications
- Practice: Local model testing becomes viable cost-reduction strategy for AI integration development
- Policy: PHP Foundation should prioritize initiatives addressing junior developer recruitment challenges
- Security: Multi-provider AI integration requires robust API key management and rotation practices
- Education: Developer tooling education should emphasize cost optimization and efficiency techniques
- Funding: Community sponsorship models need refinement to support critical infrastructure projects sustainably
### ๐ง Learning Styles Assessment
Reading level estimate: 12-14 (technical discussion with specialized terminology)
#### ๐ Visual learners
- Present: Conference footage, code examples in discussion
- Improve: API architecture diagrams, cost comparison charts, community growth visualizations
#### ๐ Aural learners
- Present: Full podcast audio with multiple speakers
- Improve: 5-minute audio summary highlighting key technical concepts
#### ๐ฃ๏ธ Verbal learners
- Present: Extensive analogies, clear technical term definitions
- Improve: Glossary of AI/ML terms, framework comparison narratives
#### ๐งฉ Kinesthetic learners
- Present: Step-by-step development stories, hands-on tool discussions
- Improve: Interactive Prism tutorials, local model setup checklists
#### ๐ง Logical learners
- Present: Clear cause-effect relationships in technology adoption
- Improve: Decision trees for AI provider selection, cost-benefit analysis frameworks
#### ๐งโ๐คโ๐ง Social learners
- Present: Strong emphasis on community interaction and conference networking
- Improve: Structured mentorship program guidance, community onboarding checklists
#### ๐งโโ๏ธ Solitary learners
- Present: Individual developer journey narratives, self-directed learning paths
- Improve: Self-assessment tools for AI integration readiness, reflection prompts
#### ๐ฟ Naturalistic learners
- Present: Ecosystem analogies for PHP community growth
- Improve: Sustainability considerations for long-term community health
### ๐ Accessibility Assessment
#### Screen reader semantics
- Present: Clear heading structure, descriptive link text in show notes
- Improve: Detailed alt text for any referenced visual materials, ARIA landmarks
#### Keyboard navigation
- Present: Standard podcast controls accessible via keyboard
- Improve: Transcript navigation shortcuts, chapter jumping functionality
#### Contrast and readability
- Present: Standard text meets basic contrast requirements
- Improve: High contrast theme option, adjustable text sizing
#### Text resizing and reflow
- Present: Responsive layout supports zoom up to 200%
- Improve: Optimize for 400% zoom, ensure no content clipping
#### Media and captions
- Present: Full transcript available
- Improve: Timestamped captions, downloadable transcript formats
#### Forms and interactions
- Present: Simple interaction model with clear feedback
- Improve: Error handling for media playback issues
#### Standards reference
- Align with WCAG 2.2 AA standards for media accessibility
### ๐ DEIB Assessment
#### Cultural breadth
- Present: Discussion of global PHP community, conference diversity
- Improve: Include international perspective on PHP adoption patterns
#### Inclusive language
- Present: Gender-neutral terms, welcoming community messaging
- Improve: Define technical jargon consistently, avoid cultural idioms
#### Neurodiversity support
- Present: Well-structured conversation with clear topic transitions
- Improve: Provide content warnings for rapid topic changes, offer transcript navigation
#### Representation
- Present: Discussion of community accessibility and welcoming culture
- Improve: Highlight diverse voices in PHP community, inclusive imagery
#### Psychological safety
- Present: Respectful technical disagreement, supportive community framing
- Improve: Explicit community guidelines reference, safe reporting mechanisms
### โ
Logical Validity
#### Strong reasoning
- Deductive strength: Clear logical progression from community demographics to sustainability concerns
- Inductive strength: Well-supported generalizations based on conference experience and industry observation
- Causal reasoning: Solid connection between messaging strategies and perception outcomes
- Analogical strength: Effective comparisons between PHP and other language ecosystems
#### Fallacies
- Survivorship bias: Focus on successful community members may not represent broader developer experience
- Hasty generalization: Conference demographics may not represent entire PHP
---
## Full Transcript
[00:00] Heat.<br>[00:11] Heat.<br>[00:31] Heat. Heat.<br>[00:59] Heat. Hey, Heat.<br>[01:07] Hey.<br>[01:34] Heat.<br>[01:50] Heat.<br>[02:16] Heat. Heat.<br>[02:21] Heat up<br>[02:43] here.<br>[02:55] Do you lie awake at night? Are you<br>[02:58] afraid to turn out the lights? Is there<br>[03:01] something you're scared of?<br>[03:05] What's there out in the dark? Make sure<br>[03:09] to keep all your windows locked. Do you<br>[03:12] do you surrender?<br>[03:15] Try to try to stay awake. These walls<br>[03:18] you can't escape.<br>[03:21] Here's one for the lonely hearts. For<br>[03:24] the ones that fear the dark. You better<br>[03:26] run out. Run out. Out of here. Bet you<br>[03:29] can't look the other way. Here's one for<br>[03:32] the broken road. That's the only one you<br>[03:36] know. You better run out. Run out. Truth<br>[03:38] or dare. Get me out. Take me anywhere<br>[03:41] but here.<br>[03:46] anywhere but here.<br>[03:52] Wanting something good to come. Waiting<br>[03:56] for things to run away from. Are you Are<br>[03:59] you just hiding?<br>[04:02] Yeah. Walking into the fire, talking<br>[04:06] like you never die. Like you're like<br>[04:09] you're immortal.<br>[04:13] Try and try to stay awake. These walls<br>[04:16] you can't escape.<br>[04:18] Here's one for the lonely hearts. For<br>[04:21] the ones that fear the dark. You better<br>[04:23] run out. Run out of here. Bet you can't<br>[04:27] look the other way. Here's one for the<br>[04:30] broken road. That's the only one you<br>[04:33] know. You better run out. Truth or dare.<br>[04:36] Get me out. Take me anywhere but here.<br>[05:00] Do you lie awake at night? Are you<br>[05:04] afraid to turn out the lights? Is there<br>[05:06] something you're scared of?<br>[05:13] Make sure to keep all your windows.<br>[05:41] Hello and welcome to PHP Alive and<br>[05:43] Kicking brought to you by PHP Architect<br>[05:46] and our partners over at PHP Score. More<br>[05:49] about them later. This is a podcast that<br>[05:51] explores the developments in PHP and<br>[05:54] what it's like to earn a living in PHP<br>[05:56] today. I'm one of your hosts, Mike<br>[05:58] Paige. I'm a developer at PHP Architect<br>[06:02] and my co-host is a longtime contributor<br>[06:04] to our magazine and now team member<br>[06:06] Chris Miller. Hi Chris.<br>[06:08] >> Hey Mike. How you doing?<br>[06:09] >> I'm good, thank you. I've been trying<br>[06:11] you've been chat putting messages in the<br>[06:14] private chat on the left hand side but<br>[06:15] all of a sudden I can't open it. So I<br>[06:17] don't know what you're saying to me<br>[06:18] anymore.<br>[06:19] >> I haven't said anything for<br>[06:22] >> There's messages popping up but I can't<br>[06:23] open it for some reason.<br>[06:25] >> I'm ling I guess I guess.<br>[06:27] >> Yeah. Good, good old good old uh reream.<br>[06:30] Um anyway, today is live everyone. So if<br>[06:33] you are listening right now, um please<br>[06:36] head over into our discord. Uh you can<br>[06:38] ask questions of our guests or us if you<br>[06:41] want to know anything about us. Uh but<br>[06:43] do uh do head over there. You don't have<br>[06:45] to stay there just for the show. You can<br>[06:47] we're in there all week long. There's<br>[06:49] lots of great people you can interact<br>[06:51] with and have conversations with. Uh<br>[06:54] please do like and subscribe to our<br>[06:55] YouTube channel.<br>[06:58] And um that<br>[07:00] >> that is not the YouTube channel.<br>[07:01] >> That's not the YouTube channel.<br>[07:02] >> That's the YouTube channel.<br>[07:04] >> That's the YouTube channel. There we go.<br>[07:06] Um I did mention in the intro there that<br>[07:09] we do have a magazine and we do have a<br>[07:13] discount code for our listeners. A live<br>[07:15] three will give you the first three<br>[07:17] months of a yearly dis<br>[07:21] digital that's the one digital<br>[07:23] subscription.<br>[07:24] Uh, so yeah, do head over there, check<br>[07:26] out the articles in the the magazine.<br>[07:28] Um, always great content each month. I<br>[07:32] cannot talk. I think I should just stop.<br>[07:35] >> No. Okay, I'll carry on. We're not going<br>[07:37] to we're not going to in keep swapping<br>[07:39] over like Eric and John tried on on<br>[07:41] Thursday. No,<br>[07:42] >> no, no,<br>[07:42] >> no, you're leaving to me. All right,<br>[07:43] then. Okay. As well as uh being a a<br>[07:47] development studio and having the<br>[07:48] magazine, we also run annual conference<br>[07:52] PHP Tech uh tickets are now on sale for<br>[07:57] next year. So it'd be great to see as<br>[07:59] many people there as possible. But not<br>[08:03] only that, alongside PHP tech, we are<br>[08:05] also going to be running JStech. The<br>[08:08] same time, same location,<br>[08:11] but purely about uh about JavaScript.<br>[08:14] And I believe the call for papers is<br>[08:17] still open.<br>[08:19] >> It is.<br>[08:19] >> Yes, it is. It's in Is it the first week<br>[08:22] of December it closes?<br>[08:23] >> I have no idea because the date's moved<br>[08:25] twice.<br>[08:26] >> Well, at the moment it's open. So, get<br>[08:28] those talks in. Uh if you've got some<br>[08:31] ideas about uh uh Java uh JavaScript<br>[08:34] ccentric talks, um we also have a swag<br>[08:38] store where you can get some lovely<br>[08:40] t-shirts, hats, caps, all sorts of<br>[08:42] things. Um I think Eric keeps adding new<br>[08:45] new things every now and then. Every<br>[08:47] time he comes up with something that he<br>[08:48] wants, he'll add it to the store. So<br>[08:51] >> um badge him. If there's something not<br>[08:53] in the store, badge him. He might<br>[08:54] actually stick it in there.<br>[08:55] >> Okay, that's all our housekeeping, uh<br>[08:58] Chris. So,<br>[08:59] >> so without further ado comment,<br>[09:04] >> uh, not quite yet. Not yet. A little bit<br>[09:08] early. I know I'm in the UK and it's in<br>[09:10] the evening, but I'm not quite yet. Not<br>[09:11] yet. No, it's it's it's actually the<br>[09:14] opposite. I'm just tired.<br>[09:16] >> So, we're definitely not going to try<br>[09:19] and convert you to become a PHP<br>[09:21] developer at JStech right next to PHP<br>[09:23] Tech.<br>[09:24] >> Oh, we're not. I thought that was our<br>[09:25] whole idea. That was the plan.<br>[09:26] >> Shush. We're not letting that bit out in<br>[09:28] public.<br>[09:29] >> I just I I just thought we were going to<br>[09:30] have to hire security to have PHP<br>[09:32] developers and J and JS developers in<br>[09:36] the same vicinity at the same time is a<br>[09:38] bit scary.<br>[09:39] >> I mean to be honest, PHP will just win.<br>[09:42] So it's fine. And and JStech CFP closes<br>[09:45] on December the 1st.<br>[09:47] >> Oh, thank you. Thank you very much. Um,<br>[09:51] so we we better stop nering because we<br>[09:54] got someone in the green room that's<br>[09:56] sitting there waiting.<br>[09:58] >> Um, they were even dialed in to reream<br>[10:00] before either of us.<br>[10:02] >> They were sitting here waiting when I<br>[10:03] came and I was in there early early. So<br>[10:06] uh Chris over to you to uh introduce our<br>[10:09] guest. So, we have a fellow PHP<br>[10:13] developer, creator of Prism, works at<br>[10:15] Geocodio,<br>[10:17] does streaming, does basically<br>[10:20] everything. We have TJ Miller. Hey, how<br>[10:23] you doing?<br>[10:24] >> Hey, how's it going?<br>[10:25] >> Hi, TD.<br>[10:28] It's been uh it's been one of these this<br>[10:30] is one we've been trying to get in the<br>[10:31] diary for a while.<br>[10:32] >> Yeah.<br>[10:33] >> Yeah.<br>[10:33] >> And then it see once we finally got in<br>[10:35] the diary, it seemed to take ages to<br>[10:37] actually get around to today. But we're<br>[10:40] here and we have<br>[10:42] >> we're here. We're doing it.<br>[10:43] >> Yeah. And of course the important things<br>[10:47] are caffeine.<br>[10:48] >> Yes. Absolutely.<br>[10:51] >> So TJ, you've been watching this for a<br>[10:54] while. You're going to know what the<br>[10:55] first question is. How did you get into<br>[10:56] BHP?<br>[10:58] >> Oh man, this is such a super boring<br>[11:01] story. So um this is many years ago. I<br>[11:05] think like 2004ish,<br>[11:09] maybe a little sooner. Uh I was like I<br>[11:13] was building websites with just like<br>[11:15] HTML and CSS for like lots of local<br>[11:17] businesses. I was in high school and I<br>[11:21] wanted I wanted a way to like templatize<br>[11:24] some of the work instead of having to<br>[11:26] like you know copy and paste over all<br>[11:28] the sidebar, the header and everything<br>[11:30] over to these like across all the HTML<br>[11:32] templates and everything. Um, I wanted<br>[11:34] something like dynamic and that's when I<br>[11:37] like discovered PHP and was able to<br>[11:40] start templatizing some of these<br>[11:42] websites that I was building so that<br>[11:43] like the header and the sidebar could<br>[11:45] stay static but we could swap out the<br>[11:48] contents on the inside of the page. Uh,<br>[11:50] and like that was so cool to me. And<br>[11:53] then like started getting into like<br>[11:55] database stuff a little bit. I'm like,<br>[11:57] oh my gosh, you can like connect<br>[11:58] databases to this. Well, that's a whole<br>[12:00] another world to like learn on top of<br>[12:02] it. Uh, so that's kind of like my entry<br>[12:05] point into PHP was just like needing<br>[12:08] some dynamicism to like that's not even<br>[12:10] a word, but uh I needed just to kind of<br>[12:13] like be a little bit more efficient<br>[12:14] about what I was doing. Um, and<br>[12:18] needed at some point like access to like<br>[12:20] data layers. How am I going to do that?<br>[12:22] Well, we can do that through PHP. So<br>[12:24] dove further into that but all just got<br>[12:26] started building like websites for local<br>[12:28] businesses.<br>[12:30] >> Yeah. So that would have been at that<br>[12:32] point you would have been using uh PHP<br>[12:34] includes.<br>[12:36] >> Mhm.<br>[12:36] >> Oh yeah.<br>[12:38] >> I remember building websites like that.<br>[12:41] My entire website was just one big<br>[12:43] include file.<br>[12:44] >> It was<br>[12:46] >> I mean to be fair that is what most of<br>[12:48] my code looks like now.<br>[12:53] So, interestingly, you seem to have<br>[12:56] journeyied on just a little bit from<br>[12:58] there, seeing as you're now writing one<br>[13:00] of the greatest AI integrations in<br>[13:03] Laravel.<br>[13:04] >> Oh, thank you.<br>[13:06] Yeah. Yeah. We've come a long way from<br>[13:08] there for sure. Like, you know, I I<br>[13:12] early career like I got started in<br>[13:14] WordPress doing like lots of just<br>[13:16] pumping out like marketing websites.<br>[13:18] Here's PSDs, turn them into websites.<br>[13:21] um did that for quite a while and that's<br>[13:23] where I dove like much much deeper into<br>[13:26] PHP and uh I was actually at one point<br>[13:31] um working on a uh the agency I was<br>[13:35] working for uh had a a cake PHP product<br>[13:38] that they they were working on and I<br>[13:41] hated it. Uh just like the way it was<br>[13:43] written was like kind of crazy. I I<br>[13:46] don't know. I just like I hated it. Uh,<br>[13:47] so I was about ready to jump ship for<br>[13:50] Ruby on Rails, but I decided to go look<br>[13:52] at like the other PHP frameworks out<br>[13:54] there. So I went and looked at uh like<br>[13:56] Falcon looked really interesting. I was<br>[13:58] thinking about going down that route and<br>[14:00] then I discovered Laravel and I was<br>[14:03] blown away. I'm like you could write PHP<br>[14:05] this way. Like that changed everything<br>[14:08] for me. And from that point on, I just<br>[14:10] made a commitment to be inside of PHP<br>[14:13] and work with work with it like<br>[14:16] explicitly ever since.<br>[14:19] >> Yeah. Cake PHP is an interesting one,<br>[14:22] isn't it? It's you either love it or<br>[14:25] hate it and nowhere in between.<br>[14:29] >> Yeah, I haven't looked at it since. Um,<br>[14:31] but it was it the I I think the one<br>[14:34] thing that drove me crazy about it, uh,<br>[14:36] and this was all like pre-omposer and<br>[14:38] everything too. Um, but what drove me<br>[14:42] crazy about it is like the the developer<br>[14:44] that worked on it at the time kind of<br>[14:46] made it his life's mission to make the<br>[14:48] the templating engine was like an<br>[14:50] object-oriented templating engine that<br>[14:51] you could opt into and he tried to to<br>[14:54] make every template like a single echo<br>[14:56] call. So it was these deeply nested<br>[14:58] chained like this div this like the span<br>[15:04] like just nested all the way down into a<br>[15:07] single echo statement for like building<br>[15:09] out an entire templated page. And so<br>[15:11] that just drove me insane.<br>[15:14] >> Yeah, that is not how you use<br>[15:17] templating. Yeah, it was it was fun to<br>[15:20] to play some code golf with it, but it<br>[15:22] was very frustrating when it was like,<br>[15:24] yeah, you got to add a whole new like<br>[15:26] div in here to do some styling. Oh no,<br>[15:29] like where the hell is this closing<br>[15:30] bracket going to go? 25 files is further<br>[15:34] on, obviously.<br>[15:34] >> Yeah, basically.<br>[15:37] >> Yes, I have worked on sites like that.<br>[15:41] They're they're interesting beasts to<br>[15:42] work on when you when you're looking at<br>[15:44] code and you're going, "Right, I know<br>[15:47] that the other half of this is<br>[15:48] somewhere, but it isn't in this file or<br>[15:51] that one or that one." And by the time<br>[15:53] you've got halfway down the list, it's<br>[15:55] like, "Where did I even start?"<br>[15:59] >> Yep. Yep. I don't know what I would do<br>[16:01] without my uh uh my find files in Neoam.<br>[16:04] Like, I just I don't I don't look<br>[16:06] through directories ever anymore. It's<br>[16:08] just Yeah. Start finding me a file.<br>[16:10] fuzzy finding it or I like grip through<br>[16:11] it and find it. Uh but yeah, back back<br>[16:15] then I didn't have any of those tools.<br>[16:17] So it was definitely like clicking<br>[16:18] through and deep deep searching nested<br>[16:21] files<br>[16:23] >> and of course not knowing how to search<br>[16:24] inside the file. You having to read the<br>[16:26] whole thing?<br>[16:27] >> Yep. Oh yeah.<br>[16:29] >> So So when did you learn how to quit<br>[16:31] Vim?<br>[16:32] Uh very early on I uh my early even<br>[16:37] before I really started building<br>[16:38] websites uh my grandmother had given me<br>[16:41] an old laptop and I just started like<br>[16:44] playing with DOSs like yeah I'm like let<br>[16:46] me let me get into the command line and<br>[16:48] felt like such a cool little hacker that<br>[16:50] I could like list directories and stuff<br>[16:52] and uh kind of broke into like nano and<br>[16:55] vim from there like as soon as I got<br>[16:57] into Linux and you got got stuck once<br>[17:00] figured out how to get out of it and uh<br>[17:02] but was hooked. I I've been uh a Vim and<br>[17:05] Neo Vim user for<br>[17:09] 15 20 years, maybe 20 years now. So big<br>[17:14] fan. I got hooked.<br>[17:16] >> I think the thing I like about it is the<br>[17:18] fact that it is so customizable.<br>[17:21] >> If if you want to change something about<br>[17:23] VI, go ahead. You can just change it.<br>[17:24] It's fine.<br>[17:27] Yeah, it's funny to go through like my<br>[17:29] my Vim config has evolved a lot over the<br>[17:31] years, but uh there are there are key<br>[17:34] bindings that have been in there for<br>[17:35] yeah 20 years that are just so ingrained<br>[17:38] in muscle memory that it makes it hard<br>[17:40] for me to really use any other editor at<br>[17:42] this point. Yeah, I I occasionally I log<br>[17:46] into PHP Storm and it's like right<br>[17:50] >> how do I do anything and and I keep<br>[17:52] doing like control S to save the file<br>[17:54] and oh yeah this is PHP Storm I don't<br>[17:57] need to do that and<br>[17:59] >> yeah<br>[18:01] oh yeah yeah like losing my leader key I<br>[18:04] get so lost in like any other ID at this<br>[18:06] point like I I've tried I've tried a<br>[18:08] whole bunch recently with all the like<br>[18:10] the wave of AI editors and everything.<br>[18:13] You know, I wanted to try them out, give<br>[18:15] them a shot, but I'm so unproductive in<br>[18:17] them.<br>[18:18] >> Uh, thank God for cloud code and I can<br>[18:21] stick in my terminals.<br>[18:24] >> Well, I um I I use PHP Storm, but for a<br>[18:28] while I did use uh Neovim and um then I<br>[18:35] can't remember why I wanted to try PHP<br>[18:37] Storm. I think it was because a lot of I<br>[18:39] I was very new to Neoim. I'd followed<br>[18:42] Jess Archer's um tutorial on Larcast on<br>[18:46] how to set up near Vim for PHP<br>[18:49] developers. I knew there was just so<br>[18:51] much more that could be done, but I<br>[18:54] didn't have the time to do the research<br>[18:56] and figure out how to get it working in<br>[18:58] near them. So, I just went<br>[19:00] >> go to PHP Storm because there's a lot of<br>[19:01] features built into PHP Storm. But one<br>[19:04] of the first things I did was um change<br>[19:07] it over to use um Vim bindings. So I've<br>[19:11] I've brought a lot of my bindings from<br>[19:12] Neo Vim into PHP Storm and that's always<br>[19:16] still evolving and and getting bigger<br>[19:18] and bigger and bigger as I'm discovering<br>[19:20] more and more things.<br>[19:21] >> Yeah,<br>[19:22] >> there's a lot more I can be doing. I<br>[19:24] know that. Um, but yeah, I like I<br>[19:28] unfortunately it means that my Neovim<br>[19:30] setup has been neglected for so long and<br>[19:32] I went to go and try and do some stuff<br>[19:33] in my dot files and my Neim just doesn't<br>[19:36] work.<br>[19:38] >> Cannot get it working anymore. I was<br>[19:39] like, uh, okay.<br>[19:42] So, um, my Oh, um, just just a quick<br>[19:45] one. I think that Eric's got the uh call<br>[19:49] for papers for JStech wrong because<br>[19:52] John's just jumped in. John John has<br>[19:55] said the JST closes on the 7th. Eric has<br>[19:58] said the first. So what we'll do is<br>[20:01] we'll say the fourth and then everybody<br>[20:02] will get them in early.<br>[20:05] >> Yeah, we could say well.<br>[20:08] >> Yes. Right.<br>[20:09] >> The fourth, but but if Yeah,<br>[20:13] >> John is being very clear there. It<br>[20:15] closes on the 7th of December.<br>[20:17] >> Right. Seventh.<br>[20:18] >> It is the seventh.<br>[20:19] >> Okay.<br>[20:20] >> Unless we move it again. back to back to<br>[20:23] Neim. So yeah, unfortunately I went into<br>[20:25] Nevin the other week to try and uh do<br>[20:28] some dot file changes and just try<br>[20:30] change a few text files which I don't<br>[20:32] actually do very often outside of PHP at<br>[20:34] the re recently. Um and even things like<br>[20:38] markdown I do I've been doing in PHP<br>[20:41] store but yeah um it's all broken so I'm<br>[20:44] going to have to call on someone to help<br>[20:45] me fix it. I did try to I did try to do<br>[20:47] it in uh get it fixed in Claude, I<br>[20:50] think, but it just got a bit messy. It<br>[20:53] didn't quite work.<br>[20:55] >> Claude has no idea how to do Neo Vim<br>[20:57] configs. I've noticed this.<br>[21:00] >> I'm I'm pretty sure none of the edit<br>[21:02] none of the staff there use Neoim.<br>[21:05] >> Nothing about it.<br>[21:06] >> Yeah. And all configed in Lua and yeah,<br>[21:10] it's it did uh I had it update. had<br>[21:13] write a couple plugins for me recently<br>[21:15] to uh to offload a few like things I<br>[21:18] wanted to try out and it it did a pretty<br>[21:20] okay job, but yeah, it's it's not super<br>[21:24] well educated on configuring Neoim with<br>[21:26] with Lua for sure.<br>[21:31] >> So, mommy and daddy are fighting.<br>[21:33] >> Yes.<br>[21:35] John says he moved the conference<br>[21:37] because I'm speaking at a diff moved the<br>[21:39] call for papers because I'm speaking at<br>[21:40] a different conference which is a JS<br>[21:43] conference<br>[21:44] and um<br>[21:47] >> we could just do that. Yeah. And<br>[21:49] >> we'll do that. So we we can follow<br>[21:50] follow the follow the argument.<br>[21:54] >> So the rest of this is just going to be<br>[21:55] watching John and Eric decide who moved<br>[21:57] it. Um<br>[22:00] so MVPOP says that Claude Code is<br>[22:02] actually good at Neoim configs. Right.<br>[22:04] What what's your secret? Because<br>[22:06] whenever I ask it to configure anything,<br>[22:07] it just gets it wrong.<br>[22:09] >> And I'm glad you say that, Chris,<br>[22:10] because I started to think it was me.<br>[22:18] >> Oh, yeah. Yeah. I've had I've had to<br>[22:19] build um two I was experimenting with<br>[22:23] some like Prism and AI stuff and trying<br>[22:26] to integrate it into like some Neoim<br>[22:29] things and I was having a really hard<br>[22:31] time with it. So, I had Claude like<br>[22:33] knock it out. It's nothing interesting.<br>[22:36] I've like abandoned the project at this<br>[22:37] point, but uh it did a pretty good job<br>[22:40] being able to like put most of the<br>[22:42] things together and you can always point<br>[22:44] it over to the docs now and you know<br>[22:46] have it go crawl the docs and it's got<br>[22:47] it's got web fetch so it can go go crawl<br>[22:50] web pages.<br>[22:52] >> So, so was this the um ability to use<br>[22:55] Prism in Neoim that you've abandoned?<br>[22:59] Uh it was a way to<br>[23:02] it was a way that I could like get a<br>[23:04] popover window with prism output uh<br>[23:07] using like a PHP script invoked by<br>[23:10] Neoim.<br>[23:11] >> Nice.<br>[23:12] >> And like passing in like like buffer<br>[23:14] context and all sorts of other<br>[23:16] information. So it was it was a I just<br>[23:18] wanted to see if I could do it and I<br>[23:21] could do it and then I've never used it<br>[23:23] since but it was just kind of a itch to<br>[23:27] scratch.<br>[23:28] Well, I I really want to see what that<br>[23:31] code looks like now.<br>[23:33] >> Yeah,<br>[23:36] I I'm mad like that. I like seeing<br>[23:37] things that are just weird experiments<br>[23:39] that usually end up being something<br>[23:41] cool. You you look at something like um<br>[23:45] not claude code and cursor that started<br>[23:48] as somebody's idea of what happens if we<br>[23:50] put AI in an IDA.<br>[23:52] >> Yeah, sure. M<br>[23:55] >> and if you could put AI inside a good<br>[23:57] IDE like Neoim,<br>[23:59] you you end up with quite a powerful<br>[24:01] little tool.<br>[24:03] >> Yeah, it's uh there's much better like<br>[24:06] AI integrations into Neoim than than<br>[24:09] that. It was uh at the time I was like I<br>[24:12] I have these system prompts that I<br>[24:15] really like to use these like personas<br>[24:17] and uh<br>[24:20] I I leverage those a lot through through<br>[24:22] Prism. I've got like a little open web<br>[24:24] UI app that I have like running<br>[24:26] persistently on my computer and then<br>[24:28] that uses a Laravel like that connects<br>[24:31] to like a Laravel API uh through Prism<br>[24:34] and so I can like chat these custom<br>[24:36] personas without having to you know do<br>[24:38] weird things about trying to like reset<br>[24:40] system prompts or or other stuff. I can<br>[24:42] just kind of like interact with them<br>[24:44] just like I'd interact with like pulling<br>[24:45] up like claw desktop or something. So,<br>[24:48] I uh I like to like pipe a lot of stuff<br>[24:51] like through Prism because I can just,<br>[24:53] you know, make make them do whatever I'd<br>[24:55] like super easily.<br>[24:58] >> I I threw that up because Eric said to<br>[25:02] one of the people watching on YouTube,<br>[25:03] "Come and join us in Discord." And<br>[25:05] they're now in Discord, which is cool.<br>[25:08] >> Yeah. to it. Um, on that note, I think<br>[25:11] it's time to um um hang on, find the<br>[25:15] right video. Uh, go to our uh our<br>[25:18] partners for today.<br>[25:23] Thank you to our partners at<br>[25:24] phpscore.com.<br>[25:26] Every app builds up technical debt over<br>[25:28] time. It's the price we pay for shipping<br>[25:30] new features and moving fast. When we<br>[25:33] build up too much of it, though, it can<br>[25:34] start to impact how we work. Team<br>[25:37] velocity suffers. bugs become more<br>[25:39] frequent and take longer to fix and<br>[25:41] everyone starts to get a little<br>[25:42] frustrated. The key to managing debt is<br>[25:45] to measure it. A credit score can help<br>[25:48] you understand how well you're managing<br>[25:49] your financial debt. And now there's a<br>[25:52] credit score for your technical debt. Go<br>[25:54] to phpsscore.com to get a free technical<br>[25:57] debt score and monitoring for all of<br>[25:59] your PHP applications today.<br>[26:04] >> Thank you. PHP school. PHP score.<br>[26:09] >> I'll do I'll do the echo today.<br>[26:13] I was reading some of the chat. I was<br>[26:14] catching up with chat, but you know what<br>[26:16] it's what it's like for me. I'm always<br>[26:18] three or four messages behind.<br>[26:21] >> So am I. And they're usually my<br>[26:22] messages.<br>[26:26] >> Yes. Well, so um I think it's a good<br>[26:29] transition to start talking about this<br>[26:31] package that you've been<br>[26:33] >> working on recently that's got everyone<br>[26:37] excited.<br>[26:39] >> How did that come about? Where did you<br>[26:41] where did the idea come from to begin<br>[26:43] with?<br>[26:43] >> So it started uh when I did the a little<br>[26:47] while before the Laravel worldwide<br>[26:49] meetup I did. Uh I forgot what year that<br>[26:52] was. Um I think it was a couple years<br>[26:53] ago at this point and like sort of<br>[26:58] getting ready for that talk but um kind<br>[27:01] of my journey getting into AI led me to<br>[27:05] a point where um this was like very<br>[27:08] early in AI. This was uh when I got<br>[27:10] started with it. It was uh maybe like 6<br>[27:12] months before chat GBT came out<br>[27:15] and I just kind of got bit by the AI bug<br>[27:20] and I could I saw like a ton of<br>[27:22] potential with it. Um I've got like<br>[27:24] pretty severe ADHD and I saw so much<br>[27:26] potential for me to be able to like<br>[27:28] build things to help augment my reality<br>[27:31] and like things to be able to like help<br>[27:33] me through like day-to-day work life,<br>[27:36] whatever. um through through AI and like<br>[27:40] the potential I could see it having as<br>[27:42] it got more powerful and uh I didn't<br>[27:45] know Python at the time. All the A IML<br>[27:47] stuff at the that point was like pretty<br>[27:51] solidly in Python. There was some<br>[27:52] TypeScript stuff starting to come out.<br>[27:54] Um Langchain was like getting getting<br>[27:58] popular. There was a a TypeScript<br>[28:00] version of that that came out. Um, but I<br>[28:04] missed spending all of my time in<br>[28:06] Laraveo. Like I've spent so much time<br>[28:09] like so much of my development career<br>[28:11] has been spent with it. I love the<br>[28:13] framework. I live and bleed it. Um,<br>[28:16] but I I wanted to be back in Laravel and<br>[28:20] like working on these experiments and<br>[28:21] continuing to learn more about AI and<br>[28:23] like building like these tool sets. Uh,<br>[28:26] I just really I I wanted to be back<br>[28:29] inside of like PHP and Laravel and like<br>[28:31] there wasn't really any tools at the<br>[28:33] time. Um, so I decided to like start<br>[28:37] working on a little framework. At the<br>[28:39] time I called it Sparkle and<br>[28:42] it was kind like this like similar to<br>[28:45] Prism but definitely different. It was<br>[28:46] like an agent focused library. um it<br>[28:50] didn't it had nowhere near as like well<br>[28:54] ststructured uh like multi-provider<br>[28:56] support but it did support multiple<br>[28:58] providers um so it was kind of this like<br>[29:00] early iteration of Prism but uh I had<br>[29:04] been showing progress on it to Taylor<br>[29:07] and Taylor had just like we were talking<br>[29:09] about the AI SDK from Verscell and he<br>[29:12] said uh he just like in passing was like<br>[29:14] yeah I wonder what a Laravel version of<br>[29:16] that would look like and I sat there for<br>[29:19] a second and the API just kind of like<br>[29:22] hit me and I sat down and like started<br>[29:24] sketching out the API and like how you<br>[29:26] would interact with it and how like<br>[29:28] multi-provider support would kind of<br>[29:30] work and uh then just started like<br>[29:33] fulfilling that contract. So it was like<br>[29:35] very very much API first and then<br>[29:37] backfilling the functionality to meet<br>[29:39] that API.<br>[29:42] >> Nice.<br>[29:43] >> So the right way around you thought<br>[29:45] about the the developer experience<br>[29:47] first. Oh, for sure. And then just it's<br>[29:49] always it's always kind of started<br>[29:51] there, you know, and as I'm facing like<br>[29:53] developing a few new features for it<br>[29:55] now, it's it's right back to that API<br>[29:58] development. It's like how do I want to<br>[29:59] make these interactions work? How is it<br>[30:01] going to feel? Um, and I think that's<br>[30:03] something that I've just gleaned from<br>[30:05] working with Laravel for so long, like<br>[30:07] that that really clean, uh, fluent, easy<br>[30:11] to work with, like where you start<br>[30:13] assuming you work with it long enough,<br>[30:14] you start like assuming methods are<br>[30:16] there and then magically they're just<br>[30:18] there for you. There's like it's a very<br>[30:20] intuitive thing to work with. And so I<br>[30:22] took a lot of that inspiration and<br>[30:23] applied that to the API of Prism.<br>[30:28] >> And that that is one of the things that<br>[30:30] Laravel always does.<br>[30:34] The the developer experience is the<br>[30:36] first thing of Laravel. So much so that<br>[30:39] we actually for a while had people who<br>[30:42] would call themselves Laravel developers<br>[30:44] and not PHP developers.<br>[30:46] >> Oh, sure.<br>[30:47] >> I mean, you see that in like the<br>[30:48] JavaScript community, too.<br>[30:49] >> Oh, yeah. Yeah.<br>[30:50] >> Yeah. like you get you get really like<br>[30:52] locked in like framework lock in um you<br>[30:55] know where that's you you learned you<br>[30:58] learned PHP by working with Laravel and<br>[31:00] like I know a ton of people that that<br>[31:02] that's how that's how they learned PHP<br>[31:03] was by starting like and picking up<br>[31:05] working with Laravel and then they<br>[31:07] learned PHP from there.<br>[31:09] >> Yeah. And and Laravel makes it easy to<br>[31:12] make that bridge because helps you with<br>[31:15] stuff until you need to do more than the<br>[31:19] framework.<br>[31:21] And that's when you start diving into<br>[31:24] into the more complex stuff of okay now<br>[31:28] we're into business logic and how we all<br>[31:30] that then we're into how do we do<br>[31:33] multi-threaded in PHP and<br>[31:36] >> the answer is I don't think you can yet<br>[31:42] >> we've got Nico on Twitter saying thanks<br>[31:44] for prison.<br>[31:45] >> Oh very welcome. It's it's such a<br>[31:47] passion project for me. Like I I love<br>[31:50] working on it. It's it's something I<br>[31:52] like I think about and and am constantly<br>[31:54] tinkering with. So um very welcome. Do<br>[31:59] >> do you know the point I realized that<br>[32:01] Prism wasn't your full-time job?<br>[32:04] >> Which was that?<br>[32:06] >> When I saw an advert for a job at<br>[32:08] Geocodio that you were recruiting for.<br>[32:14] >> Yeah.<br>[32:18] So, yes, that that's when I found out<br>[32:19] that Prism wasn't actually making you<br>[32:22] any money.<br>[32:23] >> No, I have uh I do have like a handful<br>[32:26] of of sponsors that I I deeply<br>[32:29] appreciate and I'm I'm very thankful<br>[32:30] for. So, uh but I I do I chew through a<br>[32:34] ton of tokens every month like running<br>[32:36] tests and experiments and, you know,<br>[32:38] trying to like push Prism further and<br>[32:40] like, you know, even just driving out a<br>[32:43] new provider. um or like testing like<br>[32:47] with Gemini 3.0 Pro that came out, there<br>[32:50] were a bunch of changes in the API that<br>[32:52] kind of needed to be made and we're<br>[32:54] still working through those with other<br>[32:55] contributors because that's it's just<br>[32:57] not a model and provider that I I use<br>[32:59] very often. Um so I don't have a lot of<br>[33:02] reasons to be testing it. So, uh,<br>[33:04] there's been a lot of really solid<br>[33:06] contributors coming back in, uh, and and<br>[33:09] bringing more support for Gemini, but,<br>[33:11] uh, I have to like manually test all of<br>[33:14] that stuff, too. So, it's I I've chew<br>[33:17] through a ton of tokens with Google over<br>[33:19] the last like month or so, you know,<br>[33:21] driving out functionality, then they<br>[33:23] drop a new model, and then I got to go<br>[33:25] test all of that stuff. So, the<br>[33:27] sponsorships go a long way, but it's far<br>[33:29] from being a full-time gig.<br>[33:31] >> Yeah. And any sponsorship is going to<br>[33:34] help. And<br>[33:35] >> oh, it makes such a huge difference for<br>[33:37] sure. Like if I could get to a point<br>[33:39] like I think<br>[33:41] >> for me the dream would be to be able to<br>[33:45] make enough in sponsorships that I could<br>[33:47] like maybe drop a day a week at<br>[33:49] Geocodio. Like be able to just like just<br>[33:52] dedicate Fridays to Prism all day every<br>[33:56] week, you know? Like that would be<br>[33:58] awesome if I could get to that point. Um<br>[34:00] but we'll see. or or talk Taylor into<br>[34:03] taking it on as first party. Oh,<br>[34:04] >> sure.<br>[34:08] >> Yeah. I mean, I you say about you you<br>[34:10] churn through lots of credits. I I I can<br>[34:14] imagine because I I with um chat GPT<br>[34:18] I've only got the free account and I'm<br>[34:20] always running out. I'm always asking<br>[34:22] random questions and it's just things I<br>[34:24] come up with. I just like ask it a<br>[34:26] question then leave it running for a<br>[34:28] little while and I'll go and do<br>[34:28] something else. come back to it churned<br>[34:30] out and I'm always running out of credit<br>[34:32] so I can imagine you going through quite<br>[34:34] a lot.<br>[34:36] >> Yeah. Yeah. I definitely chew through<br>[34:38] them and you know it's it's<br>[34:41] like spinning up accounts at all the<br>[34:43] different providers and like you know<br>[34:46] having to juggle all the API keys for<br>[34:47] everyone and<br>[34:49] >> you know it's remembering which one<br>[34:51] supports what thing and it's it's a it's<br>[34:55] a wild time out there. I mean, look at<br>[34:56] the last week alone, we've had, you<br>[34:59] know, three new premier models drop.<br>[35:02] >> And with that, new new features and<br>[35:05] functionality, too. So, it's it's been<br>[35:08] uh a busy busy couple weeks with with<br>[35:11] Prism and and we're like I said, we're<br>[35:13] still churning through some of the API<br>[35:15] changes for the new stuff.<br>[35:19] >> Yeah, I can I can I can imagine. I<br>[35:21] hadn't thought I hadn't appreciated or<br>[35:23] thought really about the the the cost of<br>[35:26] all the testing you must go through. And<br>[35:28] I'm now thinking about the the little<br>[35:30] idea that I we were talking about just<br>[35:31] before the show that I'm hoping at some<br>[35:33] point uh probably in the new year to get<br>[35:35] time to play around with. I'm thinking,<br>[35:37] yeah, I'm going to go through quite a<br>[35:38] lot of credits just testing that to get<br>[35:40] make sure it works. So, yeah. Yeah,<br>[35:43] that's that's that's very interesting.<br>[35:45] >> Yeah. One of the cool things I found out<br>[35:47] recently, I started playing well, I<br>[35:49] started playing a little bit more with<br>[35:50] um Olama and local models for test<br>[35:54] experiments<br>[35:55] >> because uh a lot of times what I'll end<br>[35:59] up doing is like I'll I'll build a<br>[36:01] streaming chat app just to like get the<br>[36:04] feel for how Prism behaves in there. Uh<br>[36:06] like one of the things I'm working on<br>[36:08] right now is uh like message<br>[36:10] persistence. like how can we make<br>[36:12] persisting these conversations through<br>[36:14] building chat apps like a really clean<br>[36:17] experience.<br>[36:18] >> So like I I would be like chewing<br>[36:23] through tokens building that thing out<br>[36:25] and like testing different<br>[36:26] configurations and different things, but<br>[36:29] um you know I I made the investment in a<br>[36:31] pretty like maxed out MacBook uh<br>[36:35] somewhat recently. So, I have the<br>[36:36] affordance to be able to run some of the<br>[36:38] bigger the the bigger local models and<br>[36:41] I've been pretty blown away like the the<br>[36:44] OpenAI's GPTO OSS model is very<br>[36:48] impressive. So for building out<br>[36:51] integrations and like experimenting with<br>[36:53] stuff, I think you can get pretty decent<br>[36:55] mileage and like a pretty good idea of<br>[36:57] how a large language model is going to<br>[36:59] handle the task at hand through some<br>[37:03] local models and then you can kind of<br>[37:05] upgrade to like test on some of the more<br>[37:07] powerful stuff or if you're running into<br>[37:09] it just like not being effective, you<br>[37:11] know, scale up a little bit, you know,<br>[37:13] try try the next level up model. Um<br>[37:16] because I think from the efficiency side<br>[37:18] of things, you really want to nail on<br>[37:21] using the smallest model possible to<br>[37:23] complete the task. So you can kind of<br>[37:25] scale up that way, kind of starting with<br>[37:27] local and then kind of upgrading through<br>[37:29] the smaller models. And the smaller the<br>[37:31] model, the less expensive they are. So<br>[37:33] you can kind of get away with, you know,<br>[37:35] sort of testing a little bit less<br>[37:37] expensive. And then you can also kind<br>[37:39] through that process of like leveling up<br>[37:42] a little bit at a time as you're trying<br>[37:44] to figure out what it's capable of,<br>[37:46] you'll also probably land on the<br>[37:47] smallest capable model for the job, too.<br>[37:51] >> Yeah.<br>[37:51] >> Yeah. That's really interesting, really<br>[37:54] helpful advice.<br>[37:55] >> And a lot of people don't realize you<br>[37:57] can even do that in some of the IDEs<br>[37:59] like claw code.<br>[38:00] >> You can actually tell it which to use.<br>[38:05] the<br>[38:06] it was either yesterday uh tight article<br>[38:11] on their blog about how to use like O<br>[38:13] Lama and self-hosted. So that's that's<br>[38:16] like a great resource for kind of like<br>[38:18] getting into that as well.<br>[38:21] >> Oh, definitely. So we've had um a lot of<br>[38:24] conversation in a very short space of<br>[38:25] time, which is good. Um first up is<br>[38:28] Jimmy um who has a question. I'm a PHP<br>[38:32] developer for 15 years. Sure, I know<br>[38:35] other languages. I began with assembly<br>[38:36] and C. Now I'm tired with the bullies of<br>[38:39] PHP. I see JS like React and other stuff<br>[38:42] very complicated. I've got the<br>[38:44] impression some juniors don't see PHP<br>[38:47] because PHP is old and not the actual<br>[38:49] hype.<br>[38:51] Oh man, there is<br>[38:54] this is so loaded. Um, yeah.<br>[38:58] >> Yeah. This is this is a gold mine of of<br>[39:00] of<br>[39:01] stuff for like hot takes around PHP.<br>[39:04] Like I I definitely think PHP suffers<br>[39:06] from an image problem. Uh I've thought<br>[39:09] that for a long time. Like that's one of<br>[39:11] the things that I appreciate about<br>[39:14] Laravel and the Laravel community is<br>[39:16] like I think everyone really pushes hard<br>[39:18] to like elevate the language alongside<br>[39:20] like the the frameworks and like you<br>[39:22] don't you don't get to be using PHP<br>[39:25] without you know using a framework at<br>[39:26] this point for a lot of things. So um<br>[39:32] I think a lot of PHP suffers from an<br>[39:34] image problem and I think we suffer<br>[39:37] because of that we end up sort of<br>[39:39] suffering at the top of the funnel right<br>[39:41] when we get new junior devs and people<br>[39:43] entering the industry like we suffer at<br>[39:46] that top of the funnel and that's where<br>[39:48] like JS is kind of snagging everyone at<br>[39:50] this point um is like that's where all<br>[39:52] the boot camps are like using like<br>[39:54] Python or JavaScript like that I think<br>[39:57] that's like 90% of the boot camps that I<br>[40:01] see. Uh I see I mean I'm in based in<br>[40:03] Metro Detroit with a lot of like auto<br>[40:05] industry. So we see a lot of like Java<br>[40:06] boot camps around here too.<br>[40:08] >> Um but the vast majority of it is like<br>[40:11] JavaScript and Python.<br>[40:13] >> So you know we we as a<br>[40:17] brand PHP right we need to figure out<br>[40:19] how we can like capture at that top of<br>[40:21] the funnel. And I think part of that is<br>[40:23] like sort of with like the image issue.<br>[40:25] Um, so I was like really happy to see<br>[40:28] with uh the 8.5 release like they had<br>[40:32] like a really nice branded web page for<br>[40:34] that. I think that was like super clean.<br>[40:36] I love how they approached that. Uh I<br>[40:39] think more more of things like that. Um<br>[40:43] are going to be helpful. So<br>[40:46] >> and I think some of the image we don't<br>[40:49] help ourselves with this and I keep<br>[40:52] seeing I've seen another one the other<br>[40:54] day. um where someone's posting<br>[40:59] maybe in LinkedIn for example this one<br>[41:00] was in LinkedIn and the the like the<br>[41:03] headline says something about PHP<br>[41:06] was actually the question is PHP dead<br>[41:09] and there's a massive sort of the post<br>[41:11] then go if you extend the post there's a<br>[41:12] big explanation why it's not dead but<br>[41:15] the problem is no people are just seeing<br>[41:17] the is PHP dead and assuming PHP is dead<br>[41:21] that's it they're not going to open it<br>[41:23] up and read the rest of it. So those<br>[41:25] things we we've got to try and turn<br>[41:27] those around. Um and that's kind of<br>[41:30] where this this show was born from was a<br>[41:33] a me I was at PHP UK earlier this year<br>[41:37] and there was there was a conversation<br>[41:38] about that about using more positive<br>[41:42] languages language to talk about PHP and<br>[41:45] not keep saying no PHP isn't dead. We we<br>[41:47] should just forget about that and not<br>[41:49] say that anymore. certainly don't title<br>[41:51] websites or posts with those words. Even<br>[41:54] if it's PHP isn't dead, people just read<br>[41:57] PHP dead. They don't get the rest of the<br>[42:00] the rest of the the sentence. So, I<br>[42:02] think as a a community, we we need to<br>[42:05] change the way that we're trying to<br>[42:06] present.<br>[42:09] >> These posts aren't trying to damage PHP<br>[42:11] and I understand that they are trying to<br>[42:13] encourage people, but it's not working<br>[42:15] because people are seeing the negative<br>[42:17] before they see the positive. I think<br>[42:19] it's a little bit of like chicken and<br>[42:21] egg though too. Um I think those types<br>[42:24] of posts exist because there is this<br>[42:26] like connotation that it's dead<br>[42:29] >> and so I I think it it you have to be<br>[42:31] careful that it doesn't get too<br>[42:32] cyclical. But<br>[42:34] >> um<br>[42:36] >> yeah, I don't know. It's it's been<br>[42:38] something that has been on my mind for<br>[42:40] for years as like someone who's like<br>[42:42] passionate about education and like<br>[42:44] sharing this stuff. Um it's like how<br>[42:47] yeah how can we get get more people in<br>[42:50] the door because<br>[42:54] there<br>[42:55] it's like just so advantageous like I I<br>[42:59] look at like setting up Ruby on like<br>[43:02] even just from like a CIS admin level<br>[43:03] like how much it takes to set up Ruby on<br>[43:06] a server, right? Verse how much it sets<br>[43:08] like takes to set up like PHP on a<br>[43:10] server. Maybe I've just been doing it<br>[43:11] for so long, but like it's<br>[43:16] it's like an easy process to walk<br>[43:19] through. It's like it's well documented.<br>[43:21] It's it's because PHP has been around<br>[43:24] for so long.<br>[43:25] >> Um<br>[43:27] granted with that too, there's a lot of<br>[43:29] bad PHP around as well.<br>[43:31] >> Um but I don't know. I don't know. It's<br>[43:35] been something on my mind for a while<br>[43:36] and I love seeing that there is such an<br>[43:39] initiative now kind of across the board,<br>[43:42] you know, internally in PHP, you know,<br>[43:45] podcasts like this, you know, the<br>[43:48] initiative for the 8.5 website, like I<br>[43:50] think I think there's a really healthy<br>[43:53] conversation going on about it now. And<br>[43:56] I think one of the things that's that's<br>[43:58] helping<br>[43:59] >> and you'll know the conversation we had<br>[44:01] in Chicago,<br>[44:02] >> but one of the things that I think is<br>[44:04] helping is actually the marketing<br>[44:06] machine that goes around a lot of the<br>[44:08] frameworks. So you've got Laravel<br>[44:10] drawing people in because they're good<br>[44:13] at marketing for themselves, which in<br>[44:15] turn promotes PHP<br>[44:18] and then you got native PHP who just<br>[44:20] goes, "By the way, we can do mobile apps<br>[44:22] now."<br>[44:22] >> Yeah. And it's like, okay, cool. And<br>[44:26] >> yeah, and and with Prism, like I I don't<br>[44:28] want to like toot my own horn too much,<br>[44:30] but with like with Prism, like now<br>[44:33] you're not bound to like look at my use<br>[44:36] case. Now you're not bound to Python,<br>[44:38] >> you know? You want to work with AI,<br>[44:41] >> not a problem working in PHP. And I know<br>[44:43] there's like a fantastic symphony<br>[44:45] package for working with AI as well.<br>[44:47] Mhm.<br>[44:47] >> So it's it's like more accessible than<br>[44:49] ever inside the language to be able to<br>[44:51] like be be accessing like new hot<br>[44:53] technologies, you know,<br>[44:55] >> and you've got the the official M MCP<br>[44:58] SDK.<br>[44:59] >> Yeah. Yeah. The investment from from the<br>[45:02] actual PHP Foundation to, you know, be<br>[45:06] involved inside of of of AI. I think<br>[45:09] that's<br>[45:10] >> so fantastic. And then and then you get<br>[45:13] some weirdo who's started a series of<br>[45:15] articles in a magazine that's published<br>[45:17] every month by PHP architect on the<br>[45:20] basics of machine learning in PHP. So<br>[45:22] teaching linear regression and all sorts<br>[45:24] in PHP. I have no idea who's writing<br>[45:26] that series. Me.<br>[45:32] >> Yeah.<br>[45:33] And these sort of things are all<br>[45:36] possible in PHP. And it's almost like we<br>[45:40] don't shout about it enough. We don't it<br>[45:44] at the lowest level we don't say<br>[45:45] actually all of the cool things you can<br>[45:47] do in JavaScript. Yeah, we can do that.<br>[45:51] >> Yeah.<br>[45:52] >> And if there's not like direct solutions<br>[45:54] with it, there's a lot of affordances<br>[45:56] inside of frameworks to be able to do<br>[45:57] those things.<br>[45:59] So, I mean, you look at like Livewire,<br>[46:02] like being able to being able to do that<br>[46:05] inside of Laravel gets you so close to<br>[46:07] the JavaScript experience for a lot of<br>[46:09] things.<br>[46:10] >> Um,<br>[46:12] you know, I<br>[46:14] >> think it's a more exciting time than<br>[46:16] ever to be getting into PHP with like<br>[46:17] all all the things that are are at our<br>[46:20] fingertips now.<br>[46:24] >> Yeah.<br>[46:24] >> Yeah. Yeah, I mean um just to just to<br>[46:27] point on what Nico just said about the<br>[46:29] PHP is dead title being a clickbait and<br>[46:32] when you then read the article it says<br>[46:35] it isn't. I I get that the the<br>[46:39] concern that I think a lot of people<br>[46:41] have that I talk to is that people read<br>[46:43] that and they don't click on it. They<br>[46:45] don't read the article to find out.<br>[46:47] >> You're just you're doom scrolling,<br>[46:48] right? You scroll past the title, you<br>[46:50] read the title, but you're not reading<br>[46:51] the article. And so you see the post on<br>[46:53] Reddit. You scroll past the title and<br>[46:55] it's like, "Yeah, is PHP dead?" You're<br>[46:57] like, "Well, I don't know. Is it?" But<br>[46:59] you don't, you're not clicking through<br>[47:00] to read the article because we don't<br>[47:02] have the attention spans anymore. But<br>[47:03] you're scrolling past it. You're seeing<br>[47:05] those titles like, "Is it dead? Is it<br>[47:07] dead? Is it dead?" Well, now you're<br>[47:08] starting to question it. So, I see where<br>[47:10] you're coming from, too.<br>[47:11] >> Yeah. Yeah. Um, there was another<br>[47:14] question, but I now can't find it.<br>[47:18] >> There was It was um<br>[47:22] Yes, that's one<br>[47:26] of<br>[47:27] >> is joining us because he's finished<br>[47:28] dinner and he's done the dishes and he<br>[47:31] wonders if some kind of PR um which Pton<br>[47:35] the Python light LLM model details would<br>[47:37] be of value<br>[47:39] maybe. Uh I'd be open to like checking<br>[47:41] out the PR like we don't have uh<br>[47:44] explicit light LLM support inside of<br>[47:47] Prism. um I think if you're going<br>[47:50] through it as like an open AI<br>[47:52] compatibility layer um<br>[47:55] you might have access to I I don't know<br>[47:57] check it out. I open the PR like I'll<br>[47:59] I'll be happy to take a look at it or<br>[48:02] shoot me a DM on any platform. You go to<br>[48:05] my website. I've got a links page. You<br>[48:07] can find me everywhere. Shoot me a DM<br>[48:09] and we can talk a little bit more about<br>[48:10] it. Um but I don't I don't see why I'd<br>[48:14] be opposed to it.<br>[48:15] >> Yeah. And uh he went on to say that he<br>[48:18] uses light LLM a lot for prototyping and<br>[48:20] it includes all the stats and the<br>[48:22] costings. I think that's more what he's<br>[48:24] getting out of the fact that you could<br>[48:25] pull out the stats and costings.<br>[48:27] >> Yeah. Yeah. You can um it we we do<br>[48:31] expose like all the like tokens and<br>[48:34] stuff that you're using through your<br>[48:36] requests with Prism, but you're you're<br>[48:38] it's still on you to be like totaling<br>[48:40] and exposing them. uh light LLM<br>[48:42] operating as a proxy to providers gives<br>[48:45] it that opportunity to like kind of<br>[48:48] build those stats up for you and store<br>[48:50] them. Um it's I I've not used light LLM<br>[48:54] in a long time, but um it looks pretty<br>[48:57] nice. It's come a long way.<br>[49:01] >> Nico wants to know if you've ever<br>[49:02] accidentally committed an API key.<br>[49:04] >> Yep, 100%.<br>[49:08] >> I think that's a good everyone's<br>[49:10] response. Yeah,<br>[49:11] >> it's 100%.<br>[49:14] >> I I definitely haven't.<br>[49:17] I definitely haven't. And I'm now going<br>[49:19] to check every reaper.<br>[49:24] >> And uh Marian.<br>[49:26] >> Yeah. What is it? What is it? The the<br>[49:28] BFG. Uh is that is that what you use to<br>[49:31] to scrub repos of things?<br>[49:33] >> I'm pretty sure that's the CLI. Yeah,<br>[49:35] I'm I'm I'm familiar. Definitely<br>[49:38] committed keys. So Marian says, "Let<br>[49:41] them think PHP is dead." Um I I get your<br>[49:45] point, but actually I'd rather they<br>[49:48] didn't think PHP was dead and came and<br>[49:50] programmed with us.<br>[49:53] >> Yeah. No, I mean uh the one of the scary<br>[49:56] things I I experienced was that being at<br>[49:58] the PHP UK conference when they were<br>[50:01] doing a um<br>[50:04] a panel and that was one of the<br>[50:06] questions was talking about bringing in<br>[50:08] junior devs and before they answered the<br>[50:10] question um they did ask anyone over the<br>[50:13] age of I think it was 35 if I remember<br>[50:16] rightly to put their hands up that are<br>[50:18] full-time dead and pretty much the whole<br>[50:20] room put their hands up.<br>[50:22] That's a scary position to be in when<br>[50:24] you've not got anyone in their 20ies and<br>[50:27] coming into into the language. What's<br>[50:30] gonna happen in 30 years time<br>[50:34] >> when all those 35 year olds are now 65<br>[50:37] and trying to retire and no one else is<br>[50:39] coming back in? So I would say we we<br>[50:42] don't want to let people think PHP is<br>[50:44] dead.<br>[50:46] We want to bring in bring bring in the<br>[50:48] new blood. We want to bring in new<br>[50:49] people and that's the way how how<br>[50:52] society and and communities thrive is<br>[50:54] bringing in new blood.<br>[50:56] >> Yeah.<br>[50:57] >> No.<br>[50:58] >> One of two things will happen if we<br>[51:00] don't bring in 20 year olds. One, the<br>[51:03] language will eventually go away. Two,<br>[51:07] those of us that are in our 60s are<br>[51:09] going to be paid a hell of a lot more<br>[51:11] money.<br>[51:14] >> There is that. There is that. Okay.<br>[51:16] PHP's dead. Yeah,<br>[51:22] >> I know. This is exactly why I've been<br>[51:24] all in. I've been in the Strat for<br>[51:26] years, right? I'm just waiting for it to<br>[51:27] die so I can capitalize on all the<br>[51:29] legacy code.<br>[51:30] >> That's exactly how Cobalt did it.<br>[51:35] >> I I have seen Cobalt jobs now advertised<br>[51:38] at ยฃ150,000,<br>[51:39] about $200,000<br>[51:42] for editing cobalt.<br>[51:44] >> Oh, sure. All right, I'm going to start<br>[51:45] googling some tutorials.<br>[51:47] >> Yeah,<br>[51:49] >> I I will give you a clue. Anything<br>[51:51] that's on YouTube about Coal is going to<br>[51:53] be at least 15 years old.<br>[51:57] >> Yes, that's fine.<br>[51:59] >> Yeah, I haven't changed since like 1985.<br>[52:02] So,<br>[52:03] >> right.<br>[52:07] >> Nico makes a fair point. Cobalt guys<br>[52:09] make bank with banks. Yeah,<br>[52:10] >> it's true.<br>[52:11] >> Yeah.<br>[52:12] >> Yeah. I mean,<br>[52:13] >> the the real money's in Forran. That's<br>[52:15] that's where you make the real money.<br>[52:17] >> Jeez.<br>[52:19] >> I I I was once responsible for writing<br>[52:22] Fortran for a very short space of time,<br>[52:27] mainly because it was bloody awful.<br>[52:33] It It's It's like Python in that the<br>[52:35] intend indentation of your code matters.<br>[52:38] >> Oh, yeah. It's It's weird because it's<br>[52:41] like got to be in the right columns and<br>[52:43] it's<br>[52:44] >> Oh, sure.<br>[52:45] >> No, I My brain doesn't work that way.<br>[52:49] Don't Don't give me columns.<br>[52:51] >> Yeah. This is This is also why I don't<br>[52:52] like YAML, you know.<br>[52:54] >> Yeah.<br>[52:57] >> I I do love YAML though. I mean, I I<br>[53:00] hate working with it, but I love it.<br>[53:04] >> I I don't know who wants to tell Marian.<br>[53:07] >> He can't do maths.<br>[53:10] He says he's from 89, so he's 26 years<br>[53:13] old, in which case I'm only 30.<br>[53:19] Yes.<br>[53:21] I wish<br>[53:24] I wish maths work that way.<br>[53:27] >> I mean, we we could just make up maths.<br>[53:31] >> I think I was doing that earlier.<br>[53:37] >> Oh, was it yesterday? I can't remember.<br>[53:39] I'm I'm I'm lost. The last last couple<br>[53:41] of days have merged a bit. Um<br>[53:46] >> maybe I am drunk. Maybe that's what's<br>[53:49] going on. I sniffed the whiskey when I<br>[53:53] went downstairs. That was enough.<br>[53:54] >> There you go. Gotcha.<br>[53:56] >> That was it. It's got me. Yeah.<br>[53:59] >> So,<br>[54:00] >> so I guess the next important question<br>[54:02] then TJ is, are you coming to tech this<br>[54:05] year?<br>[54:05] >> Oh, yeah. I'll be there.<br>[54:07] >> Good. Cool.<br>[54:08] >> Yeah. Yeah. I missed uh I unfortunately<br>[54:11] uh I missed the CFP so I don't I don't<br>[54:15] think I'll be talking this year. Uh but<br>[54:17] I will be there for sure. Have another<br>[54:20] CFP open.<br>[54:21] >> Yeah. What you should do is do a talk on<br>[54:24] PHP for JavaScript developers and put it<br>[54:26] into JStech.<br>[54:28] >> I thought about it. I'm not going to<br>[54:30] lie.<br>[54:32] Not going to lie. Um, I I mean I almost<br>[54:35] thought about doing a like a Versel AI<br>[54:38] SDK talk as well cuz it is such a<br>[54:41] similar realm that like I should be able<br>[54:43] to like pick up and run with it. But uh<br>[54:47] >> I don't know. I'm my my JavaScript is so<br>[54:49] rusty at this point. I think I'd be<br>[54:50] doing myself a disservice to like try to<br>[54:53] do a JavaScript talk and re like relearn<br>[54:56] the language.<br>[54:58] If only you had some sort of system that<br>[55:00] let you integrate with multiple AIs that<br>[55:02] would help you.<br>[55:03] >> I know, right?<br>[55:06] >> That'd be great.<br>[55:08] >> Just Yeah, just get AI to write it for<br>[55:11] you. No one will know. Honest.<br>[55:14] >> Yeah. No, it should be gone.<br>[55:15] >> You're absolutely right.<br>[55:17] >> Yeah.<br>[55:18] I just got to memorize it, right? That's<br>[55:20] good to go.<br>[55:21] >> No, no, no, no. Then you<br>[55:23] >> What you do then is you go to 11 Labs.<br>[55:25] You teach it your voice and<br>[55:29] Let me just get on stage and hit play<br>[55:31] like DJ style, right?<br>[55:32] >> And then just go and sit in the front<br>[55:34] row and then ask yourself some<br>[55:35] questions.<br>[55:39] >> Oh, I should have pitched that one.<br>[55:41] >> Oh, that'd be great.<br>[55:43] >> I may do it.<br>[55:44] >> I may pitch the AI talk.<br>[55:47] >> Yeah,<br>[55:49] >> it's totally doable.<br>[55:52] I think the funny the funniest<br>[55:54] conference talk I ever gave was one on<br>[55:56] how to do conference talks. I said<br>[55:59] precisely nothing in the talk. It was<br>[56:02] just on like raising your voice and<br>[56:04] lowering your voice and all I was doing<br>[56:07] was demonstrating it with and now I'm<br>[56:08] going to raise my voice and then I'm<br>[56:10] going to lower it so that people think<br>[56:11] I'm talking about something important<br>[56:13] and<br>[56:16] >> nice. I love that.<br>[56:20] So, um, we're we're getting up to to our<br>[56:24] time now, unfortunately. It's been a<br>[56:26] been a a laugh and, uh, but we do have<br>[56:29] one more question for you.<br>[56:31] >> Yeah, that's um, what I mean, you've<br>[56:35] probably touched on quite a bit of it<br>[56:36] already, but what excites you about PHP<br>[56:39] now today or what's coming up?<br>[56:43] >> Oh, man. Uh, there's a whole bunch of<br>[56:47] interesting stuff, right? Like I want to<br>[56:49] I want to play with some pipe operators<br>[56:51] a little bit and like brand new<br>[56:53] >> feature out. I want to mess with those<br>[56:54] some more. Um that's that's an exciting<br>[56:57] exciting feature ad for me.<br>[57:00] >> Uh I don't know.<br>[57:02] I thought about this question a little<br>[57:04] bit um early on like while we were<br>[57:07] chatting before the show and honestly<br>[57:10] like the thing that gets me the most<br>[57:12] excited about PHP and like it's the same<br>[57:14] thing that's made me the most excited<br>[57:16] about PHP<br>[57:18] >> for years is just the community. It's<br>[57:21] it's the people that are involved in it.<br>[57:23] It's the,<br>[57:26] you know, the the things that we're<br>[57:28] doing. Like every time I go to like PHP<br>[57:31] Tech or Laracon or, you know, something,<br>[57:36] I come back so inspired to like do more<br>[57:40] and better things like especially now<br>[57:42] that I'm like working with Prism, you<br>[57:44] know, I came back from like all these<br>[57:46] conferences so inspired to like make it<br>[57:48] better and like contribute more. Um, I<br>[57:53] don't know. It's like the<br>[57:55] it's always been the community for me.<br>[57:57] Like that's that's something that bit me<br>[57:59] early on in my like serious PHP career<br>[58:02] when I started, you know, got out of the<br>[58:03] marketing stuff and got into like<br>[58:05] building real world apps. Um, I went to<br>[58:08] Laracon. Let me check the badge.<br>[58:12] 2016 was my first Laracon. So that was<br>[58:14] like my first conference I had ever been<br>[58:16] to. Um, anything. And I walked away from<br>[58:20] that conference just so committed to<br>[58:23] PHP, to Laravel, to the community. Um, I<br>[58:27] was just blown away by that and and I've<br>[58:30] been to a bunch of conferences since<br>[58:32] then. Uh, spoke at a handful and I just<br>[58:36] always come back to for me the most like<br>[58:38] one of the most exciting things is the<br>[58:39] community. So, like if you're watching<br>[58:42] this, like if you can get if you haven't<br>[58:44] been to a conference, like<br>[58:46] >> try and get to one. Like PHP Tech is<br>[58:49] like one of my favorites because uh it's<br>[58:54] it's a wellorganized conference. It's I<br>[58:57] love the venue's like I think great for<br>[58:59] a conference. I've always enjoyed<br>[59:01] speaking at it, but it's such a great<br>[59:04] blend of like, you know, you got<br>[59:07] Laracon, which is like very Laravel<br>[59:09] heavy. I've been to a bunch of Laracons.<br>[59:11] I love it. Um, but this like PHP tech, I<br>[59:14] think, does such a good job of like<br>[59:15] giving you the exposure to like PHP as a<br>[59:18] broader language and like the broader<br>[59:20] PHP community. It's<br>[59:23] >> such a great entry point into that. So,<br>[59:25] like I think that's a great conference<br>[59:26] to go to. Laracon, highly recommend.<br>[59:29] love it. They're all over. The Laravel<br>[59:31] live conferences are fantastic, too. Um,<br>[59:34] so if you can like get out there and get<br>[59:35] involved in the community, like highly<br>[59:38] recommend it. It's I think one of like<br>[59:40] the very special pieces about the<br>[59:42] language.<br>[59:44] >> Yeah, you I love the fact that you said<br>[59:46] the community. I'm afraid you have to<br>[59:48] forgive me. My dog is now barking at<br>[59:49] some idiot setting off fireworks.<br>[59:52] So, if you can hear hear my dogs<br>[59:54] barking, I do apologize, but I wanted to<br>[59:57] weigh in here and not just keep muted<br>[59:59] because um I've said this on the show<br>[60:01] before on other episodes, but the PHP<br>[60:06] tech community um was so welcoming to me<br>[60:10] when I went to it first time last year.<br>[60:13] Um,<br>[60:15] I was obviously I was fly flown over as<br>[60:17] part of the team. Um, and I was working<br>[60:19] on it, but it was everyone was just just<br>[60:23] sit there chatting away with you and you<br>[60:25] would you would be sitting talking to<br>[60:27] someone then you realize it's it's some<br>[60:30] someone from internals or or you're<br>[60:34] talking to Derek or or you're talking to<br>[60:37] Ben Ramsey and you go, "This been Ben<br>[60:40] Ramsey I'm talking to." And and one of<br>[60:42] the big things I think from that from<br>[60:44] especially from tech um is that there's<br>[60:49] no<br>[60:51] there's no clicks is what we would say<br>[60:54] there there's no sort of barrier between<br>[60:55] the speakers and the the general public<br>[60:58] that going to watch the speakers mingle<br>[61:00] um all and there's so many people there.<br>[61:02] It's it's it is such a great experience.<br>[61:04] Um, I would<br>[61:06] >> highly recommend<br>[61:09] that anyone can go. Even if you have to<br>[61:11] get your your company to sponsor you to<br>[61:13] come over, come over and if you don't<br>[61:16] know anyone, just talk to one of us.<br>[61:18] >> You've seen our faces enough. You know<br>[61:20] who we are. We're we're all going to be<br>[61:22] there working and TJ is going to<br>[61:24] obviously be there. Just come and say<br>[61:25] hi.<br>[61:26] >> Say hi to Eric or John or any of any of<br>[61:28] the team and we'll we'll introduce you<br>[61:30] to people.<br>[61:31] >> Um, and I I understand what it's like. I<br>[61:34] I have um social anxiety, so I I know<br>[61:37] what it's like trying to be in a in a in<br>[61:38] a building full of people that I don't<br>[61:40] know. Um and I had never felt at ease so<br>[61:44] quickly when I turned up to tech last<br>[61:47] year when I came to the first one. Um<br>[61:50] and I think it's I think it helps that<br>[61:51] we we do over a spread of a few over<br>[61:54] three days as well. So you start to see<br>[61:56] the same faces the next day and the next<br>[61:58] day and start talking to people. uh not<br>[62:00] knocking any of these on one day<br>[62:01] conferences because I've been to quite a<br>[62:03] few and you do pick up a lot of stuff<br>[62:05] you don't get that social time to<br>[62:08] actually um meet people properly um I<br>[62:12] feel um although I the the conference<br>[62:16] Chris was talking at was it last week or<br>[62:18] the week before um and I went along I<br>[62:20] went along<br>[62:20] >> last game<br>[62:21] >> yeah I can't remember when it was the<br>[62:23] days are emerging now um we I I've I<br>[62:27] obviously sp met a of Chris's con sort<br>[62:31] of people he knows because I didn't know<br>[62:33] anyone there um and he introduced and um<br>[62:35] luckily got to chatting to a few people<br>[62:37] that was it was nice but I found when<br>[62:40] I've gone to conferences on my own when<br>[62:43] there's only it's only one day you don't<br>[62:45] always get that that connection with<br>[62:47] people um but again I've learned a lot<br>[62:50] from those conferences so I'm not<br>[62:52] knocking them it's they're brilliant to<br>[62:53] go to um I wouldn't say don't go to them<br>[62:56] um you might be more easy to talk to<br>[62:59] than I am<br>[63:01] and meet people. But uh yeah, no tech<br>[63:04] tech over the three days with the<br>[63:05] socializing in the evening.<br>[63:07] >> Um it I've not experienced anything like<br>[63:11] it since um all the same. So I I<br>[63:14] absolutely absolutely love it and really<br>[63:16] really recommend it. Really recommend it<br>[63:19] to anyone. Um it's a long flight from<br>[63:21] where we are, but if you can get over<br>[63:23] there, get over there. Submit to submit<br>[63:26] to JST because we'll fly you over if you<br>[63:28] get selected.<br>[63:30] >> Not only fly you over, we'll put you up<br>[63:32] in the hotel.<br>[63:33] >> Oh, yeah. Well, no. Yeah, we'll put you<br>[63:34] in the hotel as well. We won't make you<br>[63:35] sleep on the streets. You can you can<br>[63:37] have a hotel room as well.<br>[63:38] >> You can if you want to, but<br>[63:40] >> Well, yeah, it's it's optional.<br>[63:43] >> But yeah, no, definitely definitely get<br>[63:46] in there. You got a few more weeks<br>[63:47] before they that call for papers close.<br>[63:50] And if you've missed it this year and<br>[63:52] you don't get this the um the ability to<br>[63:55] come over, uh there is virtual tickets.<br>[63:58] Um so you can get a get a virtual ticket<br>[64:00] to to watch the talks, but try try for<br>[64:03] I'm sure I'm sure 27's going to happen<br>[64:06] as well.<br>[64:08] It's a it's a coming up to the stage<br>[64:09] where Eric and John were never doing it<br>[64:11] again, but they will still do it again,<br>[64:12] I'm sure.<br>[64:14] >> But yeah, so try again next time and and<br>[64:17] come along. It is it is a great<br>[64:19] experience. Um,<br>[64:20] >> I mean, as stupid as it sounds, going<br>[64:23] from not knowing a single person in that<br>[64:25] room other than to have met them on<br>[64:27] Discord to sitting around a table eating<br>[64:30] sushi with TJ and Daniel Cobborn and<br>[64:33] it's like, what am I even doing here in<br>[64:35] the middle of Chicago eating sushi with<br>[64:38] people that wrote packages I use? Oh<br>[64:40] man, I'll tell you what, like my like<br>[64:43] handful of best friends that I've the<br>[64:46] longest these these are friends that<br>[64:48] I've had for the longest amount of time<br>[64:50] in my life. Um people that I talk to<br>[64:53] like all the time. Uh I met them in 2016<br>[64:56] at a Laracon going out to like we went<br>[64:59] out to like dinner together. Like<br>[65:00] someone had just like posted on Twitter<br>[65:02] that like, "Yeah, hey, we're at Laracon.<br>[65:04] We're going out to dinner." And I think<br>[65:06] I met Eric at the same dinner. like it<br>[65:08] was just this like wild experience where<br>[65:11] uh you know just I went along for the<br>[65:13] ride on a whim. I didn't know anybody at<br>[65:15] the conference beforehand and then<br>[65:16] walked away with like four or five like<br>[65:18] my my best friends.<br>[65:20] >> Um so like it's it's<br>[65:23] >> the magic of of of being at some of<br>[65:25] these conferences. So, and it's for me<br>[65:28] it's been ubiquitous across uh Laracon,<br>[65:33] Laravel Live Denmark, uh PHP Tech, like<br>[65:37] this like the PHP community. It's so<br>[65:40] welcoming across the board. Um it's not<br>[65:43] it's not just PHP tech, but like just<br>[65:46] this community in general. Uh you can<br>[65:48] like I landed in uh Larvo Live Denmark.<br>[65:51] I didn't know anybody. first time<br>[65:53] overseas. Uh, and I left with like a<br>[65:56] whole bunch of new friends. Um, it's<br>[65:58] just like the scene like the PHP scene<br>[66:01] is just welcoming. It's friendly. It's<br>[66:03] inviting. Um,<br>[66:05] >> you know, I can't tell you like how many<br>[66:06] conferences we go up to and there's like<br>[66:08] gaps and circles of people talking. Like<br>[66:10] plenty of room for you to just like walk<br>[66:11] in, you know, just listen in, drop in.<br>[66:14] Um, and yeah, just, you know, you see<br>[66:16] the people out there that are are doing<br>[66:18] live streams that are like, you know,<br>[66:20] talking. And if you find them, just go<br>[66:22] like introduce yourself, say hi. Like I<br>[66:24] think one of the the most rewarding<br>[66:26] experiences for me was of of Laracon<br>[66:28] this year was I was walking between the<br>[66:31] venue and the expo center and someone<br>[66:33] ran up to me and they were like, "Hey,<br>[66:34] let me show you what I built with<br>[66:35] Prism." It blew my mind. Like just like<br>[66:39] somebody is using this thing that I<br>[66:41] built. Um but I had never never met them<br>[66:44] before. They just ran up to me and was<br>[66:45] like, "Hey, you got a second? Let me<br>[66:46] show you what I built with Prism." And<br>[66:48] like that was one of the more meaningful<br>[66:50] experiences that I walked away from the<br>[66:52] conference with. So yeah, just walk up,<br>[66:54] introduce yourself, and say hi.<br>[66:56] >> Yeah.<br>[66:57] >> And I I have yet to find a person in PHP<br>[67:00] who doesn't say hi back.<br>[67:02] >> Yep.<br>[67:03] >> For sure.<br>[67:05] >> And that is one of the things that makes<br>[67:07] this such a good language. The the<br>[67:10] community is the center of it. like you<br>[67:12] said it, you can't not have the<br>[67:16] community in PHP<br>[67:18] and not see success.<br>[67:21] >> I mean, I can put a question on Twitter<br>[67:23] and it's highly likely that the person<br>[67:26] that wrote the package I'm asking about<br>[67:27] replies to me<br>[67:29] >> and that that's just weird.<br>[67:33] >> But also, I think being involved in the<br>[67:35] community, going to conferences and<br>[67:36] things like that, how many people have<br>[67:38] got jobs through that those networking<br>[67:40] as well?<br>[67:42] Oh, my entire career was based on my My<br>[67:46] entire career has been based on the<br>[67:47] decision to be involved in the Laravel<br>[67:48] community.<br>[67:51] >> You're going to have to give us some<br>[67:53] context to this one, TJ.<br>[67:59] >> We know I I I think I might know some of<br>[68:01] it.<br>[68:03] >> I definitely didn't crash at his place<br>[68:05] over the summer for a long weekend and<br>[68:08] it was not creepy. Mostly.<br>[68:12] >> Was this the weekend where you didn't<br>[68:13] appear on the podcast, too?<br>[68:15] >> Yes, that was definitely the weekend I<br>[68:17] didn't appear on the podcast.<br>[68:20] >> Yeah, he's just CGIed you into the back<br>[68:23] of the video.<br>[68:26] >> Yes.<br>[68:28] Okay. Um, so, um, we do need to start<br>[68:32] wrapping things up. Um, I think we could<br>[68:35] sit here for hours longer just chatting<br>[68:37] away and like a lot of most of our<br>[68:40] guests we or all of our guests we could<br>[68:42] carry on talking for ages. So, we will<br>[68:44] definitely have you on the short list<br>[68:46] for next year to come on the show. We'll<br>[68:49] catch up with you, see what Prism's up<br>[68:51] to, what new stuff is coming.<br>[68:53] >> Yeah, if you want if if you want, we're<br>[68:55] not going to kidnap you and force you to<br>[68:56] be on the show.<br>[68:58] >> You're not. I clearly am.<br>[69:02] No, I'd love to come back anytime.<br>[69:03] >> You know who's good cop bad cop now.<br>[69:05] >> Yeah, there we go.<br>[69:07] >> Um, so yeah, I mean we we'll we'll start<br>[69:10] wrapping thing things up, but uh Tina,<br>[69:12] thank you very much for coming on. It's<br>[69:15] been one of those episodes that we've<br>[69:16] we've been trying to get in. It's not<br>[69:18] been very easy to find when we you're<br>[69:20] available to jump on and I love the fact<br>[69:22] we've done live uh with you and we've<br>[69:24] been able to get some questions in. Um,<br>[69:27] and definitely we'll get you in again<br>[69:29] next year and we'll we'll chat about all<br>[69:31] sorts. Um,<br>[69:32] >> perfect.<br>[69:34] >> So, I need to bring my script up because<br>[69:35] I will forget something otherwise.<br>[69:38] So, um, yeah. So, thank you very much.<br>[69:40] Uh, thank you very much everyone for<br>[69:41] watching or listening or however you are<br>[69:44] consuming this uh this show. Um, one<br>[69:47] thing we are going to and have I got it<br>[69:49] ready? Have I got it ready? It's there.<br>[69:50] It's there.<br>[69:52] It is there. But I've got to remember<br>[69:55] how to share my screen.<br>[70:02] There it is. Ah, there we go.<br>[70:07] Speakers are starting to be announced<br>[70:09] for tech next year. Um, I probably<br>[70:13] should scroll down the page a bit. I<br>[70:14] can't see what I'm doing when I'm in<br>[70:16] this screen, but yeah. So, we have a a<br>[70:20] really good selection of to uh speakers<br>[70:23] already already selected.<br>[70:27] So, if you haven't got your ticket yet,<br>[70:30] get your tickets<br>[70:31] >> and come and join us.<br>[70:33] >> There's some there's some blooming good<br>[70:34] speakers in amongst who've already been<br>[70:36] selected and there's still more to go.<br>[70:39] >> Yep. Yep. So, keep an eye on the on the<br>[70:42] the website. Um, have you got the link<br>[70:44] there to show Chris? Ready?<br>[70:47] >> You mean that one?<br>[70:48] >> This is This is This is going so smooth,<br>[70:51] so professional.<br>[70:52] >> We We're just learning from John and<br>[70:54] Eric. That's all.<br>[70:55] >> We We've got the best teachers in the<br>[70:57] world. Uh, phpech.io.<br>[71:00] Head over there. You can keep an eye on<br>[71:01] what uh who's uh who's going to be<br>[71:03] appearing. Um, also don't forget to join<br>[71:06] us in Discord. Uh, people are in there<br>[71:09] all the time. Uh, including TJ will be<br>[71:12] in there. If you if you tag him, I'm<br>[71:14] sure he'll answer.<br>[71:15] >> Yeah.<br>[71:15] >> Um,<br>[71:15] >> I I summoned him the other day.<br>[71:17] >> Yeah. If you summon me, I'll show up.<br>[71:19] >> Yeah. Do you have to say your name<br>[71:21] twice? Three times. It's three. You have<br>[71:23] to say your name three times before you<br>[71:24] show up.<br>[71:24] >> It's five times into a mirror. It's like<br>[71:27] handyman.<br>[71:28] >> Right. It's that one. Right. There's so<br>[71:30] many different rules. I can't remember<br>[71:32] who goes by which rules.<br>[71:34] >> It's bloody Mary if you want it three<br>[71:36] times into a mirror.<br>[71:37] >> I'm I'm more preferential to to<br>[71:39] Beetlejuice. So, three will work.<br>[71:41] >> Yeah,<br>[71:43] >> that's what I was going off of. There<br>[71:44] you go.<br>[71:45] >> So, discord.phparch.com.<br>[71:47] Come and join us for the chat. And uh<br>[71:49] we're loads of great people in there all<br>[71:51] week long chatting along. Um so, do join<br>[71:54] us. Uh if you're on our YouTube channel,<br>[71:56] please uh like and subscribe. If you're<br>[71:58] not on the YouTube channel, go over<br>[72:00] there, like and subscribe, and you can<br>[72:02] see all the other episodes. And uh the<br>[72:05] other podcasts that we we do as part of<br>[72:07] the same channel. We have the main show<br>[72:08] on a Thursday evening with Eric and<br>[72:11] John. Got us, which I don't know what<br>[72:13] our schedule is anymore because it's<br>[72:14] like<br>[72:16] >> one out Thursday. I don't know who it is<br>[72:18] yet.<br>[72:19] >> Yeah. Yeah. We'll we'll be taking place.<br>[72:21] We'll have something going out on<br>[72:22] Thursday. Taking place as the main one.<br>[72:24] Uh because our fellow friends over the<br>[72:27] pond will be celebrating its<br>[72:29] Thanksgiving. Have I got that one right?<br>[72:31] >> Yep.<br>[72:32] >> Thanksgiving over there.<br>[72:33] >> It is.<br>[72:34] >> Yeah. So, we'll be we'll be uh putting<br>[72:36] something up on Thursday. Are we doing<br>[72:38] something Friday as well then? As well<br>[72:41] as Thursday. We're just doing Thursday,<br>[72:43] not Friday. We're just putting<br>[72:44] >> Not Friday. We We'll bring it forward.<br>[72:45] >> We're just doing So, we're just doing<br>[72:47] one more this week. Originally, we were<br>[72:49] going to do one every other week and now<br>[72:52] we're doing two a week.<br>[72:54] >> Yeah. This is episode 17<br>[72:58] and we've been going for three weeks.<br>[73:02] Um so, okay. So that's our YouTube<br>[73:04] channel. Uh don't forget magazine<br>[73:06] discount for our lovely listeners. Alive<br>[73:08] 3 will give you the first three months<br>[73:10] of a annual digital subscription.<br>[73:14] We keep talking about it. I'm going to<br>[73:15] say it again. Tech PHP Tech 26. Do come<br>[73:20] and join us over in Chicago. It is a<br>[73:22] it's a lovely lovely week. Um great<br>[73:25] bunch of people as we've we've tal<br>[73:27] talked about already. So I won't keep<br>[73:29] pushing but don't forget JStech. Uh,<br>[73:32] call for papers is still open till the<br>[73:34] 7th of December. TJ, 7th of December.<br>[73:37] You can learn JavaScript by then, can't<br>[73:39] you?<br>[73:39] >> I think I can probably pull that off.<br>[73:42] >> There you go. There's There's your talk.<br>[73:43] There's your talk. How to learn<br>[73:45] JavaScript in two weeks.<br>[73:47] >> Claude, teach me JavaScript.<br>[73:50] >> Exactly.<br>[73:50] >> No, don't do that.<br>[73:55] >> Yeah, that'll be interesting. Um, and<br>[73:56] then we've got our swag sort. We have<br>[74:00] >> head over there and you can see t-shirts<br>[74:03] and uh some hats and caps and things at<br>[74:07] store at p uh sorry store.phparch.com.<br>[74:11] Head over there and grab some swag for<br>[74:13] it. And uh that is everything. We have<br>[74:17] ticked all the boxes.<br>[74:19] >> Thank you very much again TJ for joining<br>[74:22] us today. Uh thank you everyone. Thank<br>[74:24] you everyone for watching live and we
<!-- deep-read:sections end -->
## ๐บ Video

---
# ๐ Full Transcript
*Auto-generated from YouTube captions ยท timestamps roughly every 30 seconds ยท [watch on YouTube](https://www.youtube.com/watch?v=nzeTSCQLd3M)*
**[00:00]** Heat. Heat.
**[00:59]** Heat. Hey, Heat. Hey.
**[01:34]** Heat. Heat.
**[02:21]** Heat up here.
**[02:55]** Do you lie awake [music] at night? Are you afraid to turn out the lights? Is there something you're scared of? What's there [music] out in [singing] the dark? Make sure to keep all your windows locked. Do you do you surrender? Try to try to stay awake. These walls you [music] can't escape. Here's one for the lonely hearts. For the ones that fear the dark. You better
**[03:26]** run out. [music] Run out. Out of here. Bet you can't look the other way. Here's one for the broken road. That's the only one you know. You better run out. [music] Run out. Truth or dare. Get me out. Take me anywhere but here. anywhere but here. Wanting something good [music] to come. Waiting for things to run away from. Are
**[03:58]** you Are you just hiding? [music] Yeah. Walking into the fire, talking [music] like you never die. Like you're like you're immortal. [music] Try and try to stay awake. These walls you can't escape. Here's one [music] for the lonely hearts. For the ones that fear the dark. You better run out. Run out of here. Bet you [music] can't look the other way.
**[04:29]** Here's one for the broken road. That's the only [music] one you know. You better run out. Truth or dare. Get me out. Take me anywhere but here.
**[05:00]** Do you lie awake at night? Are you afraid to turn out the lights? Is there something you're scared of? Make sure to keep all your windows.
**[05:30]** [music] Hello and welcome to PHP Alive and Kicking brought to you by PHP Architect and our partners over at PHP Score. More about them later. This is a podcast that explores the developments in PHP and what it's like to earn a living in PHP today. I'm one of your hosts, Mike Paige. I'm a developer at PHP Architect
**[06:02]** and my co-host is a longtime contributor to our magazine and now team member Chris Miller. Hi Chris. >> Hey Mike. How you doing? >> I'm good, thank you. I've been trying you've been chat putting messages in the private chat on the left hand side but all of a sudden I can't open it. So I don't know what you're saying to me anymore. >> I haven't said anything for [laughter] >> There's messages popping up but I can't open it for some reason. >> I'm ling I guess I guess. >> Yeah. Good, good old good old uh reream. Um anyway, today is live everyone. So if
**[06:33]** you are listening right now, um please head over into our discord. Uh you can ask questions of our guests or us if you want to know anything about us. Uh but do uh do head over there. You don't have to stay there just for the show. You can we're in there all week long. There's lots of great people you can interact with and have conversations with. Uh please do like and subscribe to our YouTube channel. And um that >> that is not the YouTube channel. >> That's not the YouTube channel. >> That's the YouTube channel. There we go.
**[07:06]** Um I did mention in the intro there that we do have a magazine and we do have a discount code for our listeners. A live three will give you the first three months of a yearly dis digital that's the one digital subscription. Uh, so yeah, do head over there, check out the articles in the the magazine. Um, always great content each month. I cannot talk. I think I should just stop. >> No. Okay, I'll carry on. We're not going
**[07:37]** to we're not going to in keep swapping over like Eric and John tried on on Thursday. No, >> no, no, >> no, you're leaving to me. All right, then. Okay. As well as uh being a a development studio and having the magazine, we also run annual conference PHP Tech uh tickets are now on sale for next year. So it'd be great to see as many people there as possible. But not only that, alongside PHP tech, we are also going to be running JStech. The
**[08:08]** same time, same location, but purely about uh about JavaScript. And I believe the call for papers is still open. >> It is. >> Yes, it is. It's in Is it the first week of December it closes? >> I have no idea because the date's moved twice. [laughter] >> Well, at the moment it's open. So, get those talks in. Uh if you've got some ideas about uh uh Java uh JavaScript ccentric talks, um we also have a swag store where you can get some lovely
**[08:40]** t-shirts, hats, caps, all sorts of things. Um I think Eric keeps adding new new things every now and then. Every time he comes up with something that he wants, he'll add it to the store. So >> um badge him. If there's something not in the store, badge him. He might actually stick it in there. >> Okay, that's all our housekeeping, uh Chris. So, >> so without further ado comment, >> uh, not quite yet. Not yet. A little bit early. I know I'm in the UK and it's in
**[09:10]** the evening, but I'm not quite yet. Not yet. No, it's it's it's actually the opposite. I'm just tired. [laughter] >> So, we're definitely not going to try and convert you to become a PHP developer at JStech right next to PHP Tech. >> Oh, we're not. I thought that was our whole idea. That was the plan. >> Shush. We're not letting that bit out in public. >> I just I I just thought we were going to have to hire security to have PHP developers and J and JS developers in the same vicinity at the same time is a bit scary. >> I mean to be honest, PHP will just win.
**[09:42]** So it's fine. And and JStech CFP closes on December the 1st. >> Oh, thank you. Thank you very much. Um, so we we better stop nering because we got someone in the green room that's sitting there waiting. >> Um, they were even dialed in to reream before either of us. >> They were sitting here waiting when I came and I was in there early early. So uh Chris over to you to uh introduce our guest. So, we have a fellow PHP
**[10:13]** developer, creator of Prism, works at Geocodio, does streaming, does basically everything. We have TJ Miller. Hey, how you doing? >> Hey, how's it going? >> Hi, TD. It's been uh it's been one of these this is one we've been trying to get in the diary for a while. >> Yeah. >> And then it see once we finally got in the diary, it seemed to take ages to actually get around to today. But we're here and we have >> we're here. We're doing it.
**[10:43]** >> Yeah. And of course the important things are caffeine. >> Yes. Absolutely. >> So TJ, you've been watching this for a while. You're going to know what the first question is. How did you get into BHP? >> Oh man, this is such a super boring story. So um this is many years ago. I think like 2004ish, maybe a little sooner. Uh I was like I
**[11:13]** was building websites with just like HTML and CSS for like lots of local businesses. I was in high school and I wanted [clears throat and cough] I wanted a way to like templatize some of the work instead of having to like you know copy and paste over all the sidebar, the header and everything over to these like across all the HTML templates and everything. Um, I wanted something like dynamic and that's when I like discovered PHP and was able to start templatizing some of these websites that I was building so that like the header and the sidebar could
**[11:45]** stay static but we could swap out the contents on the inside of the page. Uh, and like that was so cool to me. And then like started getting into like database stuff a little bit. I'm like, oh my gosh, you can like connect databases to this. Well, that's a whole another world to like learn on top of it. Uh, so that's kind of like my entry point into PHP was just like needing some dynamicism to like that's not even a word, but uh I needed just to kind of like be a little bit more efficient about what I was doing. Um, and
**[12:18]** needed at some point like access to like data layers. How am I going to do that? Well, we can do that through PHP. So dove further into that but all just got started building like websites for local businesses. >> Yeah. So that would have been at that point you would have been using uh PHP includes. >> Mhm. >> Oh yeah. >> I remember building websites like that. My entire website was just one big include file. >> It was [laughter] >> I mean to be fair that is what most of my code looks like now. [laughter]
**[12:53]** So, interestingly, you seem to have journeyied on just a little bit from there, seeing as you're now writing one of the greatest AI integrations in Laravel. >> Oh, thank you. [laughter] Yeah. Yeah. We've come a long way from there for sure. Like, you know, I I early career like I got started in WordPress doing like lots of just pumping out like marketing websites. Here's PSDs, turn them into websites. um did that for quite a while and that's
**[13:23]** where I dove like much much deeper into PHP and uh I was actually at one point um working on a uh the agency I was working for uh had a a cake PHP product that they they were working on and I hated it. Uh just like the way it was written was like kind of crazy. I I don't know. I just like I hated it. Uh, so I was about ready to jump ship for Ruby on Rails, but I decided to go look at like the other PHP frameworks out
**[13:54]** there. So I went and looked at uh like Falcon looked really interesting. I was thinking about going down that route and then I discovered Laravel and I was blown away. I'm like you could write PHP this way. Like that changed everything for me. And from that point on, I just made a commitment to be inside of PHP and work with work with it like explicitly ever since. >> Yeah. Cake PHP is an interesting one, isn't it? It's you either love it or
**[14:25]** hate it and nowhere in between. >> Yeah, I haven't looked at it since. Um, but it was it the I I think the one thing that drove me crazy about it, uh, and this was all like pre-omposer and everything too. Um, but what drove me crazy about it is like the the developer that worked on it at the time kind of made it his life's mission to make the the templating engine was like an object-oriented templating engine that you could opt into and he tried to to make every template like a single echo
**[14:56]** call. So it was these deeply nested chained like this div this like the span like just nested all the way down into a single echo statement for like building out an entire templated page. And so that just drove me insane. >> Yeah, that is not how you use templating. Yeah, it was it was fun to to play some code golf with it, but it was very frustrating when it was like, yeah, you got to add a whole new like div in here to do some styling. Oh no,
**[15:29]** like [laughter] where the hell is this closing bracket going to go? 25 files is further on, obviously. >> Yeah, basically. >> Yes, I have worked on sites like that. [clears throat] They're they're interesting beasts to work on when you when you're looking at code and you're going, "Right, I know that the other half of this is somewhere, but it isn't in this file or that one or that one." And by the time you've got halfway down the list, it's like, "Where did I even start?" [gasps] >> Yep. Yep. I don't know what I would do
**[16:01]** without my uh uh my find files in Neoam. Like, I just I don't I don't look through directories ever anymore. It's just Yeah. Start finding me a file. fuzzy finding it or I like grip through it and find it. Uh but yeah, back back then I didn't have any of those tools. So it was definitely like clicking through and deep deep searching nested files >> and of course not knowing how to search inside the file. You having to read the whole thing? >> Yep. Oh yeah. >> So So when did you learn how to quit Vim?
**[16:32]** Uh very early on I uh my early even before I really started building websites uh my grandmother had given me an old laptop and I just started like playing with DOSs like yeah I'm like let me let me get into the command line and felt like such a cool little hacker that I could like list directories and stuff and uh kind of broke into like nano and vim from there like as soon as I got into Linux and you got got stuck once figured out how to get out of it and uh but was hooked. I I've been uh a Vim and
**[17:05]** Neo Vim user for 15 20 years, maybe 20 years now. [sighs and gasps] So big fan. I got hooked. >> I think the thing I like about it is the fact that it is so customizable. >> If if you want to change something about VI, go ahead. You can just change it. It's fine. [laughter] Yeah, it's funny to go through like my my Vim config has evolved a lot over the years, but uh there are there are key bindings that have been in there for yeah 20 years that are just so ingrained
**[17:38]** in muscle memory that it makes it hard for me to really use any other editor at this point. Yeah, I I occasionally I log into PHP Storm and it's like right >> how do I do anything and and I keep doing like control S to save the file and oh yeah this is PHP Storm I don't need to do that and [laughter] >> yeah oh yeah yeah like losing my leader key I get so lost in like any other ID at this point like I I've tried I've tried a
**[18:08]** whole bunch recently with all the like the wave of AI editors and everything. You know, I wanted to try them out, give them a shot, but I'm so unproductive in them. >> Uh, thank God for cloud code and I can stick in my terminals. [laughter] >> Well, I um I I use PHP Storm, but for a while I did use uh Neovim and um then I can't remember why I wanted to try PHP Storm. I think it was because a lot of I
**[18:39]** I was very new to Neoim. I'd followed Jess Archer's um tutorial on Larcast on how to set up near Vim for PHP developers. I knew there was just so much more that could be done, but I didn't have the time to do the research and figure out how to get it working in near them. So, I just went >> go to PHP Storm because there's a lot of features built into PHP Storm. But one of the first things I did was um change it over to use um Vim bindings. So I've
**[19:11]** I've brought a lot of my bindings from Neo Vim into PHP Storm and that's always still evolving and and getting bigger and bigger and bigger as I'm discovering more and more things. >> Yeah, >> there's a lot more I can be doing. I know that. Um, but yeah, I like I unfortunately it means that my Neovim setup has been neglected for so long and I went to go and try and do some stuff in my dot files and my Neim just doesn't work. >> Cannot get it working anymore. I was like, uh, okay.
**[19:42]** So, um, my Oh, um, just just a quick one. I think that Eric's got the uh call for papers for JStech wrong because John's just jumped in. John John has said the JST closes on the 7th. Eric has said the first. So what we'll do is we'll say the fourth and then everybody will get them in early. >> Yeah, we could say well. >> Yes. Right. >> The fourth, but but if Yeah,
**[20:13]** >> John is being very clear there. It closes on the 7th of December. >> Right. Seventh. >> It is the seventh. >> Okay. >> Unless we move it again. [laughter] back to back to Neim. So yeah, unfortunately I went into Nevin the other week to try and uh do some dot file changes and just try change a few text files which I don't actually do very often outside of PHP at the re recently. Um and even things like markdown I do I've been doing in PHP store but yeah um it's all broken so I'm
**[20:44]** going to have to call on someone to help me fix it. I did try to I did try to do it in uh get it fixed in Claude, I think, but it just got a bit messy. It didn't quite work. [laughter] >> Claude has no idea how to do Neo Vim configs. I've noticed this. [laughter] >> I'm I'm pretty sure none of the edit none of the staff there use Neoim. >> Nothing about it. >> Yeah. And all configed in Lua and yeah, it's it did uh I had it update. had write a couple plugins for me recently
**[21:15]** to uh to offload a few like things I wanted to try out and it it did a pretty okay job, but yeah, it's it's not super well educated on configuring Neoim with with Lua for sure. >> So, mommy and daddy are fighting. >> Yes. [laughter] John says he moved the conference because I'm speaking at a diff moved the call for papers because I'm speaking at a different conference which is a JS conference and um
**[21:47]** >> we could just do that. Yeah. And >> we'll do that. So we we can follow follow the follow the argument. [laughter] >> So the rest of this is just going to be watching John and Eric decide who moved it. Um [laughter] so MVPOP says that Claude Code is actually good at Neoim configs. Right. What what's your secret? Because whenever I ask it to configure anything, it just gets it wrong. >> And I'm glad you say that, Chris, because I started to think it was me. [laughter]
**[22:18]** >> Oh, yeah. Yeah. I've had I've had to build um two I was experimenting with some like Prism and AI stuff and trying to integrate it into like some Neoim things and I was having a really hard time with it. So, I had Claude like knock it out. It's nothing interesting. I've like abandoned the project at this point, but uh it did a pretty good job being able to like put most of the things together and you can always point it over to the docs now and you know have it go crawl the docs and it's got it's got web fetch so it can go go crawl
**[22:50]** web pages. >> So, so was this the um ability to use Prism in Neoim that you've abandoned? Uh it was a way to it was a way that I could like get a popover window with prism output uh using like a PHP script invoked by Neoim. >> Nice. >> And like passing in like like buffer context and all sorts of other information. So it was it was a I just wanted to see if I could do it [laughter]
**[23:20]** and I could do it and then I've never used it since but it was just kind of a itch to scratch. Well, I I really want to see what that code looks like now. [laughter] >> Yeah, I I'm mad like that. I like seeing things that are just weird experiments that usually end up being something cool. You you look at something like um not claude code and cursor that started as somebody's idea of what happens if we put AI in an IDA.
**[23:52]** >> Yeah, sure. M >> and if you could put AI inside a good IDE like Neoim, you you end up with quite a powerful little tool. >> Yeah, it's uh there's much better like AI integrations into Neoim than than that. It was uh at the time I was like I I have these system prompts that I really like to use these like personas and uh I I leverage those a lot through through Prism. I've got like a little open web
**[24:24]** UI app that I have like running persistently on my computer and then that uses a Laravel like that connects to like a Laravel API uh through Prism and so I can like chat these custom personas without having to you know do weird things about trying to like reset system prompts or or other stuff. I can just kind of like interact with them just like I'd interact with like pulling up like claw desktop or something. So, I uh I like to like pipe a lot of stuff like through Prism because I can just, you know, make make them do whatever I'd
**[24:55]** like super easily. >> I I threw that up because Eric said to one of the people watching on YouTube, "Come and join us in Discord." And they're now in Discord, which is cool. >> Yeah. to it. Um, on that note, I think it's time to um um hang on, find the right video. Uh, go to our uh our partners for today. Thank you to our partners at phpscore.com.
**[25:26]** Every app builds up technical debt over time. It's the price we pay for shipping new [music] features and moving fast. When we build up too much of it, though, it can start to impact how we work. [music] Team velocity suffers. bugs become more frequent and take longer to fix and everyone starts to get a little frustrated. The key to managing debt is to measure it. A credit score can help you understand how well you're managing your financial debt. And now there's [music] a credit score for your technical debt. Go to phpsscore.com to get a free technical debt score and
**[25:58]** monitoring for all of your PHP applications today. >> Thank you. PHP school. PHP score. >> I'll do I'll do the echo today. [laughter] I was reading some of the chat. I was catching up with chat, but you know what it's what it's like for me. I'm always three or four messages behind. >> So am I. And they're usually my messages. [laughter] >> Yes. Well, so um I think it's a good
**[26:29]** transition to start talking about this package that you've been >> working on recently that's got everyone excited. >> How did that come about? Where did you where did the idea come from to begin with? >> So it started uh when I did the a little while before the Laravel worldwide meetup I did. Uh I forgot what year that was. Um I think it was a couple years ago at this point and like sort of getting ready for that talk but um kind
**[27:01]** of my journey getting into AI led me to a point where um this was like very early in AI. This was uh when I got started with it. It was uh maybe like 6 months before chat GBT came out and I just kind of got bit by the AI bug and I could I saw like a ton of potential with it. Um I've got like pretty severe ADHD and I saw so much potential for me to be able to like build things to help augment my reality and like things to be able to like help
**[27:33]** me through like day-to-day work life, whatever. um through through AI and like the potential I could see it having as it got more powerful and uh I didn't know Python at the time. All the A IML stuff at the that point was like pretty solidly in Python. There was some TypeScript stuff starting to come out. Um Langchain was like getting getting popular. There was a a TypeScript version of that that came out. Um, but I
**[28:04]** missed spending all of my time in Laraveo. Like I've spent so much time like so much of my development career has been spent with it. I love the framework. I live and bleed it. Um, but I I wanted to be back in Laravel and like working on these experiments and continuing to learn more about AI and like building like these tool sets. Uh, I just really I I wanted to be back inside of like PHP and Laravel and like there wasn't really any tools at the time. Um, so I decided to like start
**[28:37]** working on a little framework. At the time I called it Sparkle and it was kind like this like similar to Prism but definitely different. It was like an agent focused library. um it didn't it had nowhere near as like well ststructured uh like multi-provider support but it did support multiple providers um so it was kind of this like early iteration of Prism but uh I had been showing progress on it to Taylor and Taylor had just like we were talking
**[29:09]** about the AI SDK from Verscell and he said uh he just like in passing was like yeah I wonder what a Laravel version of that would look like and I sat there for a second and the API just kind of like hit me and I sat down and like started sketching out the API and like how you would interact with it and how like multi-provider support would kind of work and uh then just started like fulfilling that contract. So it was like very very much API first and then backfilling the functionality to meet
**[29:39]** that API. >> Nice. >> So the right way around you thought about the the developer experience first. Oh, for sure. And then just it's always it's always kind of started there, you know, and as I'm facing like developing a few new features for it now, it's it's right back to that API development. It's like how do I want to make these interactions work? How is it going to feel? Um, and I think that's something that I've just gleaned from working with Laravel for so long, like that that really clean, uh, fluent, easy
**[30:11]** to work with, like where you start assuming you work with it long enough, you start like assuming methods are there and then magically they're just there for you. There's like it's a very intuitive thing to work with. And so I took a lot of that inspiration and applied that to the API of Prism. >> And that that is one of the things that Laravel always does. The the developer experience is the first thing of Laravel. So much so that we actually for a while had people who
**[30:42]** would call themselves Laravel developers and not PHP developers. >> Oh, sure. >> I mean, you see that in like the JavaScript community, too. >> Oh, yeah. Yeah. >> Yeah. like you get you get really like locked in like framework lock in um you know where that's you you learned you learned PHP by working with Laravel and like I know a ton of people that that that's how that's how they learned PHP was by starting like and picking up working with Laravel and then they learned PHP from there. >> Yeah. And and Laravel makes it easy to
**[31:12]** make that bridge because helps you with stuff until you need to do more than the framework. And that's when you start diving into into the more complex stuff of okay now we're into business logic and how we all that then we're into how do we do multi-threaded in PHP and >> the answer is I don't think you can yet [laughter] [snorts]
**[31:42]** >> we've got Nico on Twitter saying thanks for prison. >> Oh very welcome. It's it's such a passion project for me. Like I I love working on it. It's it's something I like I think about and and am constantly tinkering with. So um very welcome. Do >> do you know the point I realized that Prism wasn't your full-time job? >> Which was that? [laughter] >> When I saw an advert for a job at Geocodio that you were recruiting for. [laughter]
**[32:14]** >> Yeah. So, yes, that that's when I found out that Prism wasn't actually making you any money. >> No, I have uh I do have like a handful of of sponsors that I I deeply appreciate and I'm I'm very thankful for. So, uh but I I do I chew through a ton of tokens every month like running tests and experiments and, you know, trying to like push Prism further and like, you know, even just driving out a new provider. um or like testing like
**[32:47]** with Gemini 3.0 Pro that came out, there were a bunch of changes in the API that kind of needed to be made and we're still working through those with other contributors because that's it's just not a model and provider that I I use very often. Um so I don't have a lot of reasons to be testing it. So, uh, there's been a lot of really solid contributors coming back in, uh, and and bringing more support for Gemini, but, uh, I have to like manually test all of that stuff, too. So, it's I I've chew through a ton of tokens with Google over
**[33:19]** the last like month or so, you know, driving out functionality, then they drop a new model, and then I got to go test all of that stuff. So, the sponsorships go a long way, but it's far from being a full-time gig. >> Yeah. And any sponsorship is going to help. And >> oh, it makes such a huge difference for sure. Like if I could get to a point like I think >> for me the dream would be to be able to make enough in sponsorships that I could like maybe drop a day a week at
**[33:49]** Geocodio. Like be able to just like just dedicate Fridays to Prism all day every week, you know? Like that would be awesome if I could get to that point. Um but we'll see. or or talk Taylor into taking it on as first party. Oh, >> sure. [laughter] >> Yeah. I mean, I you say about you you churn through lots of credits. I I I can imagine because I I with um chat GPT I've only got the free account and I'm
**[34:20]** always running out. I'm always asking random questions and it's just things I come up with. I just like ask it a question then leave it running for a little while and I'll go and do something else. come back to it churned out and I'm always running out of credit so I can imagine you going through quite a lot. >> Yeah. Yeah. I definitely chew through them and you know it's it's like spinning up accounts at all the different providers and like you know having to juggle all the API keys for everyone and >> you know it's remembering which one
**[34:51]** supports what thing and it's it's a it's a wild time out there. I mean, look at the last week alone, we've had, you know, three new premier models drop. >> And with that, new new features and functionality, too. So, it's it's been uh a busy busy couple weeks with with Prism and and we're like I said, we're still churning through some of the API changes for the new stuff. >> Yeah, I can I can I can imagine. I hadn't thought I hadn't appreciated or
**[35:23]** thought really about the the the cost of all the testing you must go through. And I'm now thinking about the the little idea that I we were talking about just before the show that I'm hoping at some point uh probably in the new year to get time to play around with. I'm thinking, yeah, I'm going to go through quite a lot of credits just testing that to get make sure it works. [clears throat] So, yeah. Yeah, that's that's that's very interesting. >> Yeah. One of the cool things I found out recently, I started playing well, I started playing a little bit more with um Olama and local models for test
**[35:54]** experiments >> because uh a lot of times what I'll end up doing is like I'll I'll build a streaming chat app just to like get the feel for how Prism behaves in there. Uh like one of the things I'm working on right now is uh like message persistence. like how can we make persisting these conversations through building chat apps like a really clean experience. >> So like I I would be like chewing through tokens building that thing out
**[36:25]** and like testing different configurations and different things, but um you know I I made the investment in a pretty like maxed out MacBook uh somewhat recently. So, I have the affordance to be able to run some of the bigger the the bigger local models and I've been pretty blown away like the the OpenAI's GPTO OSS model is very impressive. So for building out integrations and like experimenting with stuff, I think you can get pretty decent
**[36:55]** mileage and like a pretty good idea of how a large language model is going to handle the task at hand through some local models and then you can kind of upgrade to like test on some of the more powerful stuff or if you're running into it just like not being effective, you know, scale up a little bit, you know, try try the next level up model. Um because I think from the efficiency side of things, you really want to nail on using the smallest model possible to complete the task. So you can kind of
**[37:25]** scale up that way, kind of starting with local and then kind of upgrading through the smaller models. And the smaller the model, the less expensive they are. So you can kind of get away with, you know, sort of testing a little bit less expensive. And then you can also kind through that process of like leveling up a little bit at a time as you're trying to figure out what it's capable of, you'll also probably land on the smallest capable model for the job, too. >> Yeah. That's really interesting, really helpful advice.
**[37:55]** >> And a lot of people don't realize you can even do that in some of the IDEs like claw code. >> You can actually tell it which to use. the it was either yesterday uh tight article on their blog about how to use like O Lama and self-hosted. So that's that's like a great resource for kind of like getting into that as well. >> Oh, definitely. So we've had um a lot of conversation in a very short space of time, which is good. Um first up is
**[38:28]** Jimmy um who has a question. I'm a PHP developer for 15 years. Sure, I know other languages. I began with assembly and C. Now I'm tired with the bullies of PHP. I see JS like React and other stuff very complicated. [gasps] I've got the impression some juniors don't see PHP because PHP is old and not the actual hype. Oh man, there is this is so loaded. [laughter] Um, yeah. >> Yeah. This [snorts] is this is a gold
**[38:59]** mine of of of stuff for like hot takes around PHP. Like I I definitely think PHP suffers from an image problem. Uh I've thought that for a long time. Like that's one of the things that I appreciate about Laravel and the Laravel community is like I think everyone really pushes hard to like elevate the language alongside like the the frameworks and like you don't you don't get to be using PHP without you know using a framework at this point for a lot of things. So um
**[39:32]** I think a lot of PHP suffers from an image problem and I think we suffer because of that we end up sort of suffering at the top of the funnel right when we get new junior devs and people entering the industry like we suffer at that top of the funnel and that's where like JS is kind of snagging everyone at this point um is like that's where all the boot camps are like using like Python or JavaScript like that I think that's like 90% of the boot camps that I see. Uh I see I mean I'm in based in
**[40:03]** Metro Detroit with a lot of like auto industry. So we see a lot of like Java boot camps around here too. >> Um but the vast majority of it is like JavaScript and Python. >> So you know we we as a brand PHP right we need to figure out how we can like capture at that top of the funnel. And I think part of that is like sort of with like the image issue. Um, so I was like really happy to see with uh the 8.5 release like they had like a really nice branded web page for
**[40:34]** that. I think that was like super clean. I love how they approached that. Uh I think more more of things like that. Um are going to be helpful. So >> and I think some of the image we don't help ourselves with this and I keep seeing I've seen another one the other day. um where someone's posting maybe in LinkedIn for example this one was in LinkedIn and the the like the headline says something about PHP
**[41:06]** was actually the question is PHP dead and there's a massive sort of the post then go if you extend the post there's a big explanation why it's not dead but the problem is no people are just seeing the is PHP dead and assuming PHP is dead that's it they're not going to open it up and read the rest of it. So those things we we've got to try and turn those around. Um and that's kind of where this this show was born from was a a me I was at PHP UK earlier this year
**[41:37]** and there was there was a conversation about that about using more positive languages language to talk about PHP and not keep saying no PHP isn't dead. We we should just forget about that and not say that anymore. certainly don't title websites or posts with those words. Even if it's PHP isn't dead, people just read PHP dead. They don't get the rest of the the rest of the the sentence. So, I think as a a community, we we need to change the way that we're trying to present.
**[42:09]** >> These posts aren't trying to damage PHP and I understand that they are trying to encourage people, but it's not working because [clears throat] people are seeing the negative before they see the positive. I think it's a little bit of like chicken and egg though too. Um I think those types of posts exist because there is this like connotation that it's dead >> and so I I think it it you have to be careful that it doesn't get too cyclical. But >> um >> yeah, I don't know. It's it's been something that has been on my mind for
**[42:40]** for years as like someone who's like passionate about education and like sharing this stuff. Um it's like how yeah how can we get get more people in the door because there it's like just so advantageous like I I look at like setting up Ruby on like even just from like a CIS admin level like how much it takes to set up Ruby on a server, right? Verse how much it sets like takes to set up like PHP on a server. Maybe I've just been doing it
**[43:11]** for so long, but like it's it's like an easy process to walk through. It's like it's well documented. It's it's because PHP has been around for so long. >> Um granted with that too, there's a lot of bad PHP around as well. >> Um but I don't know. I don't know. It's been something on my mind for a while and I love seeing that there is such an initiative now kind of across the board,
**[43:42]** you know, internally in PHP, you know, podcasts like this, you know, the initiative for the 8.5 website, like I think I think there's a really healthy conversation going on about it now. And I think one of the things that's that's helping >> and you'll know the conversation we had in Chicago, >> but one of the things that I think is helping is actually the marketing machine that goes around a lot of the frameworks. So you've got Laravel drawing people in because they're good
**[44:13]** at marketing for themselves, which in turn promotes PHP and then you got native PHP who just goes, "By the way, we can do mobile apps now." >> Yeah. And it's like, okay, cool. And >> yeah, and and with Prism, like I I don't want to like toot my own horn too much, but with like with Prism, like now you're not bound to like look at my use case. Now you're not bound to Python, >> you know? You want to work with AI, >> not a problem working in PHP. And I know
**[44:43]** there's like a fantastic symphony package for working with AI as well. Mhm. >> So it's it's like more accessible than ever inside the language to be able to like be be accessing like new hot technologies, you know, >> and you've got the the official M MCP SDK. >> Yeah. Yeah. The investment from from the actual PHP Foundation to, you know, be involved inside of of of AI. I think that's >> so fantastic. And then and then you get some weirdo who's started a series of
**[45:15]** articles in a magazine that's published every month by PHP architect on the basics of machine learning in PHP. So teaching linear regression and all sorts in PHP. I have no idea who's writing that series. Me. [laughter] >> Yeah. And these sort of things are all possible in PHP. And it's almost like we don't shout about it enough. We don't it at the lowest level we don't say
**[45:45]** actually all of the cool things you can do in JavaScript. Yeah, we can do that. >> Yeah. >> And if there's not like direct solutions with it, there's a lot of affordances inside of frameworks to be able to do those things. So, I mean, you look at like Livewire, like being able to being able to do that inside of Laravel gets you so close to the JavaScript experience for a lot of things. >> Um, you know, I >> think it's a more exciting time than
**[46:16]** ever to be getting into PHP with like all all the things that are are at our fingertips now. >> Yeah. Yeah, I mean um just to just to point on what Nico just said about the PHP is dead title being a clickbait and when you then read the article it says it isn't. I I get that the the concern that I think a lot of people have that I talk to is that people read that and they don't click on it. They don't read the article to find out.
**[46:47]** >> You're just you're doom scrolling, right? You scroll past the title, you read the title, but you're not reading the article. And so you see the post on Reddit. You scroll past the title and it's like, "Yeah, is PHP dead?" You're like, "Well, I don't know. Is it?" But you don't, you're not clicking through to read the article because we don't have the attention spans anymore. But you're scrolling past it. You're seeing those titles like, "Is it dead? Is it dead? Is it dead?" Well, now you're starting to question it. So, I see where you're coming from, too. >> Yeah. Yeah. Um, there was another question, but I now can't find it.
**[47:18]** >> There was It was um Yes, that's one [laughter] of >> is joining us because he's finished dinner and he's done the dishes and he wonders if some kind of PR um which Pton the Python light LLM model details would be of value maybe. Uh I'd be open to like checking out the PR like we don't have uh explicit light LLM support inside of Prism. um I think if you're going
**[47:50]** through it as like an open AI compatibility layer um you might have access to I I don't know check it out. I open the PR like I'll I'll be happy to take a look at it or shoot me a DM on any platform. You go to my website. I've got a links page. You can find me everywhere. Shoot me a DM and we can talk a little bit more about it. Um but I don't I don't see why I'd be opposed to it. >> Yeah. And uh he went on to say that he uses light LLM a lot for prototyping and
**[48:20]** it includes all the stats and the costings. I think that's more what he's getting out of the fact that you could pull out the stats and costings. >> Yeah. Yeah. You can um it we we do expose like all the like tokens and stuff that you're using through your requests with Prism, but you're you're it's still on you to be like totaling and exposing them. uh light LLM operating as a proxy to providers gives it that opportunity to like kind of build those stats up for you and store them. Um it's I I've not used light LLM
**[48:54]** in a long time, but um it looks pretty nice. It's come a long way. >> Nico wants to know if you've ever accidentally committed an API key. >> Yep, 100%. [laughter] >> I think that's a good everyone's response. Yeah, [laughter] >> it's 100%. >> I I definitely haven't. I definitely haven't. And I'm now going to check every reaper. [laughter]
**[49:24]** >> And uh Marian. >> Yeah. What is it? What is it? The the BFG. Uh is that is that what you use to to scrub repos of things? >> I'm pretty sure that's the CLI. Yeah, I'm I'm I'm familiar. [laughter] Definitely committed keys. So Marian says, "Let them think PHP is dead." Um I I get your point, but actually I'd rather they didn't think PHP was dead and came and programmed with us. >> Yeah. No, I mean uh the one of the scary
**[49:56]** things I I experienced was that being at the PHP UK conference when they were doing a um a panel and that was one of the questions was talking about bringing in junior devs and before they answered the question um they did ask anyone over the age of I think it was 35 if I remember rightly to put their hands up that are full-time dead and pretty much the whole room put their hands up. That's a scary position to be in when you've not got anyone in their 20ies and
**[50:27]** coming into into the language. What's gonna happen in 30 years time >> when all those 35 year olds are now 65 and trying to retire and no one else is coming back in? So I would say we we don't want to let people think PHP is dead. [laughter] We want to bring in bring bring in the new blood. We want to bring in new people and that's the way how how society and and communities thrive is bringing in new blood. >> Yeah. >> No.
**[50:58]** >> One of two things will happen if we don't bring in 20 year olds. One, the language will eventually go away. Two, those of us that are in our 60s are going to be paid a hell of a lot more money. [laughter] >> There is that. There is that. Okay. PHP's dead. [laughter] Yeah, >> I know. This is exactly why I've been all in. I've been in the Strat for years, right? I'm just waiting for it to die so I can capitalize on all the
**[51:29]** legacy code. >> That's exactly how Cobalt did it. [laughter] >> I I have seen Cobalt jobs now advertised at ยฃ150,000, about $200,000 for editing cobalt. >> Oh, sure. All right, I'm going to start googling some tutorials. >> Yeah, [laughter] >> I I will give you a clue. Anything that's on YouTube about Coal is going to be at least 15 years old. >> Yes, that's fine. >> Yeah, I haven't changed since like 1985.
**[52:02]** So, [laughter] >> right. >> Nico makes a fair point. Cobalt guys make bank with banks. Yeah, >> it's true. >> Yeah. I mean, >> the the real money's in Forran. That's that's where you make the real money. >> Jeez. >> I I I was once responsible for writing Fortran for a very short space of time, mainly because it was bloody awful. [laughter]
**[52:33]** It It's It's like Python in that the intend indentation of your code matters. >> Oh, yeah. It's It's weird because it's like got to be in the right columns and it's >> Oh, sure. >> No, I My brain doesn't work that way. Don't Don't give me columns. [laughter] >> Yeah. This is This is also why I don't like YAML, you know. >> Yeah. [laughter] >> I I do love YAML though. I mean, I I hate working with it, but I love it.
**[53:04]** >> I I don't know who wants to tell Marian. >> He can't do maths. >> [laughter] >> He says he's from 89, so he's 26 years old, in which case I'm only 30. Yes. I wish [laughter] I wish maths work that way. >> I mean, we we could just make up maths. >> I think I was doing that earlier. [laughter]
**[53:37]** >> Oh, was it yesterday? I can't remember. I'm I'm I'm lost. The last last couple of days have merged a bit. Um [laughter] >> maybe I am drunk. Maybe that's what's going on. I sniffed the whiskey when I went downstairs. That was enough. >> There you go. Gotcha. >> That was it. It's got me. Yeah. >> So, >> so I guess the next important question then TJ is, are you coming to tech this year? >> Oh, yeah. I'll be there. >> Good. Cool.
**[54:08]** >> Yeah. Yeah. I missed uh I unfortunately uh I missed the CFP so I don't I don't think I'll be talking this year. Uh [snorts] but I will be there for sure. Have another CFP open. >> Yeah. What you should do is do a talk on PHP for JavaScript developers and put it into JStech. >> I thought about it. I'm not [laughter] going to lie. Not going to lie. Um, I I mean I almost thought about doing a like a Versel AI SDK talk as well cuz it is such a
**[54:41]** similar realm that like I should be able to like pick up and run with it. But uh >> I don't know. I'm my my JavaScript is so rusty at this point. I think I'd be doing myself a disservice to like try to do a JavaScript talk and re like relearn the language. [laughter] If only you had some sort of system that let you integrate with multiple AIs that would help you. >> I know, right? [laughter] >> That'd be great. [clears throat] >> Just Yeah, just get AI to write it for you. No one will know. Honest.
**[55:14]** >> Yeah. No, it should be gone. >> You're absolutely right. >> Yeah. [laughter] I just got to memorize it, right? That's good to go. >> No, no, no, no. Then you >> What you do then is you go to 11 Labs. You teach it your voice and >> [laughter] >> Let me just get on stage and hit play like DJ style, right? >> And then just go and sit in the front row and then ask yourself some questions. [laughter] >> Oh, I should have pitched that one. [laughter] >> Oh, that'd be great. >> I may do it.
**[55:44]** >> I may pitch the AI talk. >> Yeah, >> it's totally doable. [laughter] I think the funny the funniest conference talk I ever gave was one on how to do conference talks. I said precisely nothing in the talk. It was just on like raising your voice and lowering your voice and all I was doing was demonstrating it with and now I'm going to raise my voice and then I'm going to lower it so that people think I'm talking about something important and [laughter]
**[56:16]** >> nice. I love that. So, um, we're we're getting up to to our time now, unfortunately. It's been a been a a laugh and, uh, but we do have one more question for you. >> Yeah, that's um, what I mean, you've probably touched on quite a bit of it already, but what excites you about PHP now today or what's coming up? >> Oh, man. [clears throat] Uh, there's a whole bunch of interesting
**[56:47]** stuff, right? Like I want to I want to play with some pipe operators a little bit and like brand new >> feature out. I want to mess with those some more. Um that's that's an exciting exciting feature ad for me. >> Uh I don't know. I thought about this question a little bit um early on like while we were chatting before the show and honestly like the thing that gets me the most excited about PHP and like it's the same thing that's made me the most excited about PHP
**[57:18]** >> for years is just the community. It's it's the people that are involved in it. It's the, you know, the the things that we're doing. Like every time I go to like PHP Tech or Laracon or, you know, something, I come back so inspired to like do more and better things like especially now that I'm like working with Prism, you know, I came back from like all these conferences so inspired to like make it
**[57:48]** better and like contribute more. Um, I don't know. It's like the it's always been the community for me. Like that's that's something that bit me early on in my like serious PHP career when I started, you know, got out of the marketing stuff and got into like building real world apps. Um, I went to Laracon. Let me check the badge. 2016 was my first Laracon. So that was like my first conference I had ever been to. Um, anything. And I walked away from
**[58:20]** that conference just so committed to PHP, to Laravel, to the community. Um, I was just blown away by that and and I've been to a bunch of conferences since then. Uh, spoke at a handful and I just always come back to for me the most like one of the most exciting things is the community. So, like if you're watching this, like if you can get if you haven't been to a conference, like >> try and get to one. Like PHP Tech is like one of my favorites because uh it's
**[58:54]** it's a wellorganized conference. It's I love the venue's like I think great for a conference. I've always enjoyed speaking at it, but it's such a great blend of like, you know, you got Laracon, which is like very Laravel heavy. I've been to a bunch of Laracons. I love it. Um, but this like PHP tech, I think, does such a good job of like giving you the exposure to like PHP as a broader language and like the broader PHP community. It's >> such a great entry point into that. So,
**[59:25]** like I think that's a great conference to go to. Laracon, highly recommend. love it. They're all over. The Laravel live conferences are fantastic, too. Um, so if you can like get out there and get involved in the community, like highly recommend it. It's I think one of like the very special pieces about the language. >> Yeah, you I love the fact that you said the community. I'm afraid you have to forgive me. My dog is now barking at some idiot setting off fireworks. So, if you can hear hear my dogs barking, I do apologize, but I wanted to
**[59:57]** weigh in here and not just keep muted because um I've said this on the show before on other episodes, but the PHP tech community um was so welcoming to me when I went to it first time last year. Um, I was obviously I was fly flown over as part of the team. Um, and I was working on it, but it was everyone was just just sit there chatting away with you and you would you would be sitting talking to
**[60:27]** someone then you realize it's it's some someone from internals or or you're talking to Derek or or you're talking to Ben Ramsey and you go, "This been Ben Ramsey I'm talking to." And and one of the big things I think from that from especially from tech um is that there's no [clears throat] there's no clicks is what we would say there there's no sort of barrier between the speakers and the the general public that going to watch
**[60:59]** the speakers mingle um all and there's so many people there. It's it's it is such a great experience. Um, I would >> highly recommend that anyone can go. Even if you have to get your your company to sponsor you to come over, come over and if you don't know anyone, just talk to one of us. >> You've seen our faces enough. You know who we are. We're we're all going to be there working and TJ is going to obviously be there. Just come and say hi. >> Say hi to Eric or John or any of any of the team and we'll we'll introduce you
**[61:30]** to people. >> Um, and I I understand what it's like. I I have um social anxiety, so I I know what it's like trying to be in a in a in a building full of people that I don't know. Um and I had never felt at ease so quickly when I turned up to tech last year when I came to the first one. Um and I think it's I think it helps that we we do over a spread of a few over three days as well. So you start to see the same faces the next day and the next day and start talking to people. uh not
**[62:00]** knocking any of these on one day conferences because I've been to quite a few and you do pick up a lot of stuff you don't get that social time to actually um meet people properly um I feel um although I the the conference Chris was talking at was it last week or the week before um and I went along I went along >> last game >> yeah I can't remember when it was the days are emerging now um we I I've I obviously sp met a of Chris's con sort
**[62:31]** of people he knows because I didn't know anyone there um and he introduced and um luckily got to chatting to a few people that was it was nice but I found when I've gone to conferences on my own when there's only it's only one day you don't always get that that connection with people um but again I've learned a lot from those conferences so I'm not knocking them it's they're brilliant to go to um I wouldn't say don't go to them um you might be more easy to talk to than I am
**[63:01]** and meet people. But uh yeah, no tech tech over the three days with the socializing in the evening. >> Um [clears throat] it I've not experienced anything like it since um all the same. So I I absolutely absolutely love it and really really recommend it. Really recommend it to anyone. Um it's a long flight from where we are, but if you can get over there, get over there. Submit to submit to JST because we'll fly you over if you get selected. >> Not only fly you over, we'll put you up
**[63:32]** in the hotel. >> Oh, yeah. Well, no. Yeah, we'll put you in the hotel as well. We won't make you sleep on the streets. You can you can have a hotel room as well. >> You can if you want to, but >> Well, yeah, it's it's optional. [laughter] >> But yeah, no, definitely definitely get in there. You got a few more weeks before they that call for papers close. And if you've missed it this year and you don't get this the um the ability to come over, uh there is virtual tickets. Um so you can get a get a virtual ticket to to watch the talks, but try try for
**[64:03]** I'm sure I'm sure 27's going to happen as well. It's a it's a coming up to the stage where Eric and John were never doing it again, but they will still do it again, I'm sure. [laughter] >> But yeah, so try again next time and and come along. It is it is a great experience. Um, >> I mean, as stupid as it sounds, going from not knowing a single person in that room other than to have met them on Discord to sitting around a table eating sushi with TJ and Daniel Cobborn and it's like, what am I even doing here in
**[64:35]** the middle of Chicago eating sushi with people that wrote packages I use? [laughter] Oh man, I'll tell you what, like my like handful of best friends that I've the longest these these are friends that I've had for the longest amount of time in my life. Um people that I talk to like all the time. Uh I met them in 2016 at a Laracon going out to like we went out to like dinner together. Like someone had just like posted on Twitter that like, "Yeah, hey, we're at Laracon. We're going out to dinner." And I think I met Eric at the
**[65:07]** same dinner. like it was just this like wild experience where uh you know just I went along for the ride on a whim. I didn't know anybody at the conference beforehand and then walked away with like four or five like my my best friends. >> Um so like it's it's >> the magic of of of being at some of these conferences. So, and it's for me it's been ubiquitous across uh Laracon, Laravel Live Denmark, uh PHP Tech, like
**[65:37]** this like the PHP community. It's so welcoming across the board. Um it's not it's not just PHP tech, but like just this community in general. Uh you can like I landed in uh Larvo Live Denmark. I didn't know anybody. first time overseas. Uh, and I left with like a whole bunch of new friends. Um, it's just like the scene like the PHP scene is just welcoming. It's friendly. It's inviting. Um, >> you know, I can't tell you like how many conferences we go up to and there's like
**[66:08]** gaps and circles of people talking. Like plenty of room for you to just like walk in, you know, just listen in, drop in. Um, and yeah, just, you know, you see the people out there that are are doing live streams that are like, you know, talking. And if you find them, just go like introduce yourself, say hi. Like I think one of the the most rewarding experiences for me was of of Laracon this year was I was walking between the venue and the expo center and someone ran up to me and they were like, "Hey, let me show you what I built with Prism." It blew my mind. Like just like
**[66:39]** somebody is using this thing that I built. Um but I had never never met them before. They just ran up to me and was like, "Hey, you got a second? Let me show you what I built with Prism." And like that was one of the more meaningful experiences that I walked away from the conference with. So yeah, just walk up, introduce yourself, and say hi. >> Yeah. >> And I I have yet to find a person in PHP who doesn't say hi back. >> Yep. >> For sure. >> And that is one of the things that makes this such a good language. The the
**[67:10]** community is the center of it. like you said it, you can't not have the community in PHP and not see success. >> I mean, I can put a question on Twitter and it's highly likely that the person that wrote the package I'm asking about replies to me >> and that that's just weird. [laughter] >> But also, I think being involved in the community, going to conferences and things like that, how many people have got jobs through that those networking
**[67:40]** as well? Oh, my entire career was based on my My entire career has been based on the decision to be involved in the Laravel community. [clears throat and laughter] >> You're going to have to give us some context to this one, TJ. >> We know I I I think I might know some of it. [laughter] [snorts] >> I definitely didn't crash at his place over the summer for a long weekend and it was not creepy. Mostly. [laughter]
**[68:12]** >> Was this the weekend where you didn't appear on the podcast, too? >> Yes, that was definitely the weekend [laughter] I didn't appear on the podcast. >> Yeah, he's just CGIed you into the back [laughter] of the video. >> Yes. Okay. Um, so, um, we do need to start wrapping things up. Um, I think we could sit here for hours longer just chatting away and like a lot of most of our guests we or all of our guests we could
**[68:42]** carry on talking for ages. So, we will definitely have you on the short list for next year to come on the show. We'll catch up with you, see what Prism's up to, what new stuff is coming. >> Yeah, if you want if if you want, we're not going to kidnap you and force you to be on the show. >> You're not. I clearly am. [laughter] No, I'd love to come back anytime. >> You know who's good cop bad cop now. [laughter] >> Yeah, there we go. >> Um, so yeah, I mean we we'll we'll start wrapping thing things up, but uh Tina, thank you very much for coming on. It's
**[69:15]** been one of those episodes that we've we've been trying to get in. It's not been very easy to find when we you're available to jump on and I love the fact we've done live uh with you and we've been able to get some questions in. Um, and definitely we'll get you in again next year and we'll we'll chat about all sorts. Um, >> perfect. >> So, I need to bring my script up because I will forget something otherwise. So, um, yeah. So, thank you very much. Uh, thank you very much everyone for watching or listening or however you are consuming this uh this show. Um, one
**[69:47]** thing we are going to and have I got it ready? Have I got it ready? It's there. It's there. It is there. But I've got to remember how to share my screen. There it is. Ah, there we go. Speakers are starting to be announced for tech next year. Um, I probably should scroll down the page a bit. I can't see what I'm doing when I'm in this screen, but yeah. So, we have a a
**[70:20]** really good selection of to uh speakers already already selected. So, if you haven't got your ticket yet, get your tickets >> and come and join us. >> There's some there's some blooming good speakers in amongst who've already been selected and there's still more to go. >> Yep. Yep. So, keep an eye on the on the the website. Um, have you got the link there to show Chris? Ready? >> You mean that one? >> This is This is This is going so smooth,
**[70:51]** so professional. >> We We're just learning from John and Eric. That's all. [laughter] >> We We've got the best teachers in the world. Uh, phpech.io. Head over there. You can keep an eye on what uh who's uh who's going to be appearing. Um, also don't forget to join us in Discord. Uh, people are in there all the time. Uh, including TJ will be in there. If you if you tag him, I'm sure he'll answer. >> Yeah. >> Um, >> I I summoned him the other day. >> Yeah. If you summon me, I'll show up. [laughter] >> Yeah. Do you have to say your name
**[71:21]** twice? Three times. It's three. You have to say your name three times before you show up. >> It's five times into a mirror. It's like handyman. >> Right. It's that one. [laughter] Right. There's so many different rules. I can't remember who goes by which rules. >> It's bloody Mary if you want it three times into a mirror. >> I'm I'm more preferential to to Beetlejuice. So, three will work. >> Yeah, [laughter] >> that's what I was going off of. There you go. >> So, discord.phparch.com. Come and join us for the chat. And uh we're loads of great people in there all
**[71:51]** week long chatting along. Um so, do join us. Uh if you're on our YouTube channel, please uh like and subscribe. If you're not on the YouTube channel, go over there, like and subscribe, and you can see all the other episodes. And uh the other podcasts that we we do as part of the same channel. We have the main show on a Thursday evening with Eric and John. Got us, which I don't know what our schedule is anymore because it's like >> one out Thursday. I don't know who it is [laughter] yet. >> Yeah. Yeah. We'll we'll be taking place. We'll have something going out on
**[72:22]** Thursday. Taking place as the main one. Uh because our fellow friends over the pond will be celebrating its Thanksgiving. Have I got that one right? >> Yep. >> Thanksgiving over there. >> It is. >> Yeah. So, we'll be we'll be uh putting something up on Thursday. Are we doing something Friday as well then? As well as Thursday. We're just doing Thursday, not Friday. We're just putting >> Not Friday. We We'll bring it forward. >> We're just doing So, we're just doing one more this week. Originally, we were going to do one every other week and now we're doing two a week.
**[72:54]** >> Yeah. This is episode 17 [laughter] and we've been going for three weeks. Um so, okay. So that's our YouTube channel. Uh don't forget magazine discount for our lovely listeners. Alive 3 will give you the first three months of a annual digital subscription. We keep talking about it. I'm going to say it again. Tech PHP Tech 26. Do come and join us over in Chicago. It is a it's a lovely lovely week. Um great
**[73:25]** bunch of people as we've we've tal talked about already. So I won't keep pushing but don't forget JStech. Uh, call for papers is still open till the 7th of December. TJ, 7th of December. You can learn JavaScript by then, can't you? >> I think I can probably [laughter] pull that off. >> There you go. There's There's your talk. There's your talk. How to learn JavaScript in two weeks. >> Claude, teach me JavaScript. >> Exactly. >> No, don't do that. [laughter] >> Yeah, that'll be interesting. Um, and
**[73:56]** then we've got our swag sort. We have >> head over there and you can see t-shirts and uh some hats and caps and things at store at p uh sorry store.phparch.com. Head over there and grab some swag for it. And uh that is everything. We have ticked all the boxes. >> Thank you very much again TJ for joining us today. Uh thank you everyone. Thank you everyone for watching live and we