PHP can’t serialize closures by default, but Laravel bundles a package that handles it behind the scenes. This video walks through how laravel serializable-closure works, where Laravel uses it (like for queued jobs and route caching), and how you can leverage it in your own projects.

Explore implementing two-factor authentication (2FA) in Laravel. This tutorial covers using Laravel JetStream, Fortify, building from scratch, and third-party packages like pragmarx/google2fa and Laragear/TwoFactor.

Now you can conditionally fail queue jobs while throttling exceptions with a new failWhen method, scope your queue fakes using fakeFor and fakeExceptFor, and use Context::remember() to cache computed values only when needed. The release also introduces doesntStartWith() and doesntEndWith() helpers for Str, allows custom key/value callbacks in Collection::pluck(), and adds the JsonSerializable interface to the Uri class for proper JSON output. Other improvements include a new @context Blade directive, making the Fluent class iterable, and adding a collection() method to the Config repository.

Need to bypass a queued job under certain conditions? Laravel’s built-in Skip class makes this simple in your job’s middleware method.

Skip::when($condition)
Skip::unless(fn () => $this->shouldRun())

PHP 8.5 introduces the pipe operator (|>), simplifying complex function chaining by using output as input for subsequent calls, significantly enhancing code readability and flexibility for developers.

The long-awaited official support for PHP 8.4 has landed in PHP-CS-Fixer with the 3.80.0 release. While it took longer than hoped, the maintainers highlight the challenges of OSS work and encourage community contributions for future releases.

PHP 8.5 will now display backtraces for fatal errors by default, making debugging much easier. When a fatal error occurs, PHP’s error output will include a detailed stack trace, so you can pinpoint exactly where and why your application crashed—no extra setup needed.

Laravel Zap offers powerful schedule management for Laravel, featuring Eloquent integration, configurable business rules, smart conflict detection, and support for recurring schedules.

Rather than forcing AI tools or tying performance to usage metrics, managers should let engineers experiment, share real wins from their own teams, and adopt new workflows at their own pace. AI can speed up development, but only when integrated thoughtfully—outcomes matter more than tool adoption stats.

This article introduces the “Ship/Show/Ask” model for handling changes in software delivery. This approach classifies changes into three categories: Ship (just do it), Show (share with the team for visibility), and Ask (request explicit approval before proceeding). The framework helps teams clarify when autonomy is appropriate, when feedback is needed, and when consensus is required—leading to faster, more transparent, and less frustrating delivery workflows.