Over Engineered

Simon Hamp and Marcel Pociot have been working on NativePHP for a number of years, and Simon just surprised with world at Laracon EU with a NativePHP for Mobile announcement. In this episode, Simon and Chris get deep into the the NativePHP innards, explore sustainable open source, and generally just have a good time for <<checks watch>> over two hours 😅

Links:

• NativePHP
• Zephpyr
• dagger

Zuzana Kunckova started Larabelles five years ago, and over that time it has grown into an important part of the Laravel community. In today's episode, Zuzana and Chris talk about the future of Larabelles now that she has more time to dedicate to it.

Links:

• Larabelles
• Sponsor Larabelles on GitHub
• Sponsor Larabelles on Patreon
• Other ways to support Larabelles

What happens when you get a bunch of Laravel podcasters + a bunch of mics in a room? Chaos, apparently.

Recorded live after PHP × NYC with Ben Holmen, John Drexler, Daniel Coulbourne, Chris Morrell, Ian Landsman, Dave Hicking, and Joe Tannenbaum.

There's lots of advice out there for running software teams, but much of it comes from large organizations with dozens or hundreds of developers. Smaller teams have different needs. On today's episode, we pick up from a question Dan asked on Bluesky and talk about how best to approach running a small development team.

Links:

• Dan's Bluesky Post
• Thunk

Shawn McCool has been talking about event sourcing for years, and recently started a new series of streams on the topic. In this episode, Chris and Shawn talk about event sourcing, Verbs, and community (among other things).

Links:

• Shawn on Twitch
• Event Sourcery
• Verbs

Design patterns can be very useful, but can also be weaponized as a way to "prove" that someone is doing something the "wrong" way. Mary has been thinking a lot about the good side of knowing design patterns, so we sat down to chat about them.

Joe Tannenbaum is thinking about starting a podcast about side projects. So we took an afternoon to talk through what that might look like.

Ben Holmen started his Pair-amid scheme as an experiment in meeting new people and experiencing new code. He shared his calendar with the world, and booked pairing sessions with 15 complete strangers. The outcome? A bunch of new friends and new experiences.

In this episode, Ben and Chris talk about pair programming, side projects, and how to find fulfillment and social connection as a remote programmer.

Links:

• The Pair-amid scheme
• The kilopixel display

ReactPHP is a low-level library for event-driven programming in PHP. It lets you write code that's much closer to the async/await style of JavaScript in PHP. In today's episode, Chris and Len talk about our experiments with ReactPHP.

Links:

• ReactPHP
• Whiskey
• Community Prompts
• Conductor
• Dawn

What set two developers on a quest to build custom tooling to enforce their code style preferences? Today's episode is a story that starts with two independent projects—Tighten's `tlint` and InterNACHI's `laralint`—but meanders to all the right places, including the future of PHP itself, the intersection of bikeshedding and art, and so much more.

Today we take a break from over engineering to talk about burnout. Both Chris and Ian have been working on the same products for multiple decades. We sit down to talk about that and what to do about the kind of burnout that comes from working on the same thing for so long.

Links:

• Brent is Leaving Twitter
• Join the RTSN.DEV mastodon instance

Steve McDougall (aka JustSteveKing) is known as the "API guy" on Twitter. In today's episode we start with the question, "what if the best option is just a single page app with a good, RESTful API?"

Links:

• HAL - Hypertext Application Language
• JSON:API Spec
• Laravel Sanctum
• API Versioning Blog Post
• Steve on Twitter (follow for updates on upcoming course)

The internet has been talking (yelling?) about full-stack javascript a lot lately. In today's episode, we sit down and talk about what it means to be "full stack" and whether there are really any truly full-stack javascript frameworks out there (spoiler: there are, but maybe not Next.js or Remix).

Links:

• Sails.js
• The Boring Javascript Stack
• AdonisJS
• NestJS
• 📻 The Future of the Laravel Frontend w/ Taylor Otwell

Jess Archer took something that was quite good—the Symfony console output features—and built something that was absolutely great: Laravel Prompts. In today's episode, we dig into some of the gnarly details around building prompts and working with ANSI escape sequences in the terminal.

Taylor Otwell has been finding ways to improve Laravel for over a decade, but has only more recently set his sights on the front-end side of things. In today's episode, we sit down and talk about the current state of building UIs in Laravel, and what the future might hold.

Links:

• Laravel Volt
• Aire Form Builder
• Laravel “Context” Feature
• Hooks Package
• Laravel Careers
• Blade Parser

Joe Tannenbaum took the internet by storm with his incredible SSH CLI "experiments." In today's episode, Chris and Joe sit down to get into the messy details of parsing ANSI escape sequences and dealing with multibyte strings, but spend as much time talking about programming as art and life as an actor.

Links:

• Joe Tannenbaum on Twitter
• Joe's "Lab" of CLI experiments
• "Kitchen" by Liza Lou
• Conveyor Belt package
• RTSN.DEV

What are the best processes for small software development teams with high trust? In today's episode the InterNACHI software development team sits down with John Rudolph Drexler to talk about whether or not we need to estimate tickets or even bother with sprints…

As the saying goes: "There are only two hard things in Computer Science: cache invalidation and naming things." So in today's episode we dig into all the ways Ian is taking on one of the hardest parts of programming in his rewrite of their decades-running helpdesk software, HelpSpot. We talk about caching, a little bit of Laravel history, and about what it's like to run a successful software business for 20+ years.

Complex view logic can be hard to get right—particularly in server-rendered templates like Blade. We recently had to decide just how much a Laravel Blade component should do, and decided to hash it out on the podcast.

When applications grow—in scope, sheer lines of code, or the number of team members—how you organize things starts to matter a whole lot more. In today's episode, we talk with Mateus Guimarães about modularization: breaking your application into smaller modules. We explore some of the topics in his new Laracasts course, and talk about the decisions that informed building the modular package at InterNACHI.