Freek.dev

Stan Daniels shares a practical checklist for tuning Laravel Horizon, from aligning timeouts and retry_after values to verifying deploy hooks and measuring real queue behavior before adding workers. It is a good reminder that queue performance issues often come down to configuration clarity and instrumentation, not just scaling up blindly.

Read more [standaniels.nl]

Nick Bevers argues that AI is pushing developers toward shallow, uncritical building, and that many teams are trusting generated code far too blindly. It's a thoughtful take on keeping a mental model of your codebase and using AI as a tool instead of handing over the craft.

Read more [www.nickbevers.dev]

How a slow dependency becomes an outage, and how deadlines, concurrency limits, retry budgets, and jitter protect useful work. A practical deep dive with PHP examples and a controlled overload test design.

Read more [wendelladriel.com]

Ryan Chandler makes a strong case for keeping PR descriptions human-written, even when agents handle most of the implementation. The piece focuses on ownership, review context, and why a concise explanation from the person driving the change is more useful than a long AI-generated summary.

Read more [laravel.com]

A practical post on hardening Laravel projects against destructive AI agent behavior. It walks through the PocketOS incident and shows concrete safeguards like deny rules, credential isolation, and production guardrails.

Read more [hafiz.dev]

What Agent Experience engineering means in practice: discoverable code paths, scoped agent instructions, useful feedback, and human ownership of risky decisions.

Read more [wendelladriel.com]

Laravel queues are great out of the box, until they bite. Over the years I’ve collected a few gotchas the hard way. Let me save you the headache.

Read more [oussama-mater.tech]

A deep dive into immutability in PHP, from readonly properties and interior mutability to immutable value objects, collections, dates, cloning, boundaries, and testing.

Read more [wendelladriel.com]

A sharp look at Tailwind's default rem-based breakpoints, and the accessibility tradeoff they make. It explains how browser font-size preferences can shift layouts, why that can help some users, and why px breakpoints are still a defensible choice.

Read more [spatie.be]

Michael explains why exit() can make parallel test workers crash without useful diagnostics, and why verbose flags do not help when the process dies outside PHPUnit's control. The fix is simple: throw an exception instead, so the failure is reported normally with a stack trace.

Read more [dyrynda.com.au]

Ankur Sethi argues that manually retyping LLM-generated code is a practical way to avoid cognitive debt. It slows you down, but helps you understand the code, catch bad suggestions, and keep a strong mental model of your codebase.

Read more [ankursethi.com]

Every year I dread coming back from vacation not because of the work, but because I have no idea where I left off. A failing test, a well-written TODO, and a slow first day back are all you need to ease back in.

Read more [lukapeharda.com]

A look at the new experimental headingoffset attribute, which lets heading levels adapt to their context instead of hardcoding h2s and h3s. A thoughtful explanation of where this could be genuinely useful, especially in component-based UIs.

Read more [www.matuzo.at]

A concise explanation of ADRs: short documents that capture an important decision, the context behind it, and its consequences. Good practical advice on keeping them lightweight, readable, and useful over time.

Read more [martinfowler.com]

How we use class-based Laravel Pennant features, with a kill switch on every flag and a config-driven path to general availability.

Read more [koomai.net]

Your Agent::fake() tests prove your Laravel AI feature runs — not that its output is any good. This evals a real ticket classifier with the AI SDK: a golden dataset for the fields you can check, an LLM-as-judge for the free text you can't, and a regression gate that catches a bad prompt before your customers do.

Read more [mujahidabbas.dev]

Michael Dyrynda shows how Laravel's distinct validation rule can protect nested request payloads from duplicate reference values before they corrupt relationship mapping. He also highlights the strict and ignore_case options for cases where loose comparison is not enough.

Read more [dyrynda.com.au]

Josh Comeau shares a thoughtful take on AI, arguing that deep technical skill becomes more valuable, not less, as these tools improve. His point is that strong developers can use AI to amplify their work, while less experienced builders still struggle without solid architectural judgment.

Read more [www.joshwcomeau.com]

Anthony Hobday shares a thoughtful framework for thinking about software quality, from reliability and speed to clarity, efficiency, and beauty. I liked his argument that quality depends on both individual care and organisational appetite.

Read more [anthonyhobday.com]

A deep dive into idempotency, from the theory behind safe retries to a practical Laravel implementation using the Laravel Idempotency package.

Read more [wendelladriel.com]