Jack Yau

Laravel's Joe Tannenbaum demonstrates how they use a new Vite plugin called Wayfinder to perform 'alchemy': - Automatically generating TypeScript types and routes from a PHP backend to create a seamless - End-to-end type-safe development experience when building modern applications. Full Video: https://lnkd.in/dU9D-wbj

44

1 Comment

🤖 Laravel 🤝 Claude 🤖 "Taylor Otwell has released a new Laravel-focused plugin for Claude Code that brings automated code cleanup directly into Laravel and PHP workflows. The agent is designed to be run after long coding sessions or complex pull requests to simplify, clean up, and normalise code." Article Link: https://lnkd.in/e-_Aan_Q

12

💡 Laravel Tip: Reusable Relationship Conditions for Cleaner Code! If you find yourself repeatedly applying the same where or orderBy constraints on a relationship, there’s a cleaner way — define custom relationship methods! Instead of writing conditions everywhere, move them into dedicated relationship methods: ✅ This approach improves: Readability — No more cluttered queries throughout the codebase. Reusability — Call relationships like $post->approvedComments directly. Maintainability — Update logic in one place instead of everywhere! Write smart relationships, not repetitive ones. 😉 #Laravel #LaravelTips #Eloquent #CleanCode #PHP #WebDevelopment #BackendDevelopment #CodeQuality #Refactoring

12

Why most Laravel SaaS platforms become hard to evolve after ~2 years After working on several production Laravel SaaS, I’ve seen the same pattern. Most don’t hit a wall because of performance. They hit a wall because of architecture erosion. Year 1 Everything ships fast. Deadlines win. Controllers grow. Validation + auth + business rules start mixing. Year 2 - The same logic exists in 3 different “services/actions” - Authorization rules are scattered (policies, controllers, middleware, random ifs) - Frontend depends on backend internals (routes shape, hidden side-effects) - “Temporary” shortcuts became permanent - People stop refactoring because it feels risky Laravel isn’t the problem. The real issue is missing structural boundaries early: - No domain separation - Business rules leaking into controllers - No application layer to orchestrate use-cases - Unstable API contracts (Requests/Resources drifting) - UI coupled to internal implementation details A SaaS evolves. If the architecture doesn’t anticipate change, every feature adds entropy. What helps long term: - Domain / application / infrastructure separation (even inside a monolith) - Explicit contracts (Form Requests + Resources/DTOs + compatibility mindset) - Isolated business rules (Actions/Use-cases, not controllers) - Controlled authorization (RBAC/permissions centralized, policies consistent) - Frontend consuming stable boundaries, not internal logic Speed matters. But sustainable speed only exists when the system is designed to evolve. That’s the difference between shipping features… and building a platform. How do you structure your Laravel SaaS today? Modular monolith? Actions-based? DDD-lite? Curious what’s working in real teams.

4

Quick update on the Friday hackathon: got the first two charts working in a Next js app. First one's the Bank of England base rate, rising from near zero to 5.25 percent in under two years. Second is monthly house sale volumes, pulled from HM Land Registry's Price Paid Data. Still early, and there's more data to bring in before I'd call any of this a real story. More charts to come. Enjoying working with d3.js again Have a good weekend! #OpenToWork #FrontendDeveloper #NextJS #D3js #DataVisualization #UKHousingMarket #ReactJS

3