Amit Merchant argues that skills, prompts, plugins, and MCP servers are becoming dependencies of AI agents, and should be versioned and managed like application code. He also highlights APM as a way to install reproducible agent tooling, with Dependabot now able to keep those dependencies up to date.
Read more [www.amitmerchant.com]
– tighten.com – Edit
This tutorial shows how to build a PHP CLI tool that returns JSON, package it for Composer, and run it from anywhere with CPX. It also explains why CPX is a nicer alternative to globally installed Composer tools, thanks to isolated dependencies and automatic updates.
Read more [tighten.com]
Join 9,500+ smart developers
Get my monthly newsletter with what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
"Always fresh, useful tips and articles. Carefully selected community content. My favorite newsletter, which I look forward to every time."
– mackgrenfell.com – Edit
Using Stripe data across about 181,000 subscription businesses, Mack Grenfell argues the SaaS slowdown became visible in October, when median revenue growth turned negative across most peer groups. He suggests the bigger problem is fewer new signups, likely driven by AI-fueled competition rather than customer churn.
Read more [mackgrenfell.com]
Felix Rieseberg argues that AI is changing what makes junior engineers valuable. He makes the case that fresh perspective, ambition, and quick prototypes can beat tenure when execution is cheap.
Read more [felixrieseberg.com]
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]
Composer 2.11 adds a cooldown dependency policy that withholds newly published package versions for a configurable period. The release also includes several security fixes and faster dependency resolution.
Read more [blog.packagist.com]
– jasonmccreary.me – Edit
Jason McCreary explains how he went from using AI for tedious snippets to letting agents handle nearly all coding, testing, and review work. It is a clear account of the guardrails, workflow shifts, and mindset changes that got him there.
Read more [jasonmccreary.me]
Below MySQL 8.0.1, or on a server Laravel misreads, workers reserve jobs with a plain FOR UPDATE and can deadlock on the DELETE. One tinker line shows which lock yours use.
Read more [mozex.dev]
– ohdear.app – Edit
Oh Dear shares hard numbers on how the recent critical PHP vulnerabilities rippled through the ecosystem, with site outages peaking at 18.8 percent and down alerts rising to 25 times the normal level. It is a useful, data-backed snapshot of a chaotic day in PHP land from a monitoring service's point of view.
Read more [ohdear.app]
– wendelladriel.com - submitted by Wendell Adriel – Edit
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]
– laravel.com – Edit
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 clear overview of PHP 8.6's readonly property defaults RFC, why the old restriction existed, and why interface properties made it worth revisiting. It also covers the practical edge cases, so you know where the new syntax helps and where it still does not.
Read more [shocm.me]
A clear walkthrough of Laravel's Context feature and how it lets execution-scoped information travel through your app. It also explains why that matters for logging, queued jobs, and keeping trace data available without threading it through every method call.
Read more [dev.to]
– laravel.com – Edit
A practical engineering write-up on moving Pinkary from Laravel Forge to Laravel Cloud. It walks through the real migration issues they hit, including SQLite to MySQL differences, query rewrites, and storage assumptions in the codebase.
Read more [laravel.com]
by Freek Van der Herten – 3 minute read – Edit
I've been writing about There There a lot lately. It's a helpdesk we're building at Spatie, born from two decades of running our own customer support for our open source work and SaaS apps. After all that time being the customer of other helpdesks, we finally started on the one we actually wanted to…
by Freek Van der Herten – 5 minute read – Edit
Over the past few weeks I've posted a couple of times about There There, the helpdesk we're building at Spatie. After two decades of running our own customer support, we decided to stop compromising on tools and build the one we actually want to use. A lot of the fun is on the AI side. We're not…
by Freek Van der Herten – 4 minute read – Edit
At Spatie we build SaaS apps with Laravel on the backend and Inertia with React on the frontend. That split means two type systems have to agree about every payload that crosses between them. Laravel data going out, TypeScript picking it up. There There, the helpdesk we're building, is built exactly…
by Freek Van der Herten – 3 minute read – Edit
There There, the helpdesk we're building at Spatie, is a project of learned habits. Twenty-some years of writing Laravel apps has taught us which patterns pay off and which ones quietly rot. One that keeps earning its keep is a custom exception class for every domain error. This is a small pattern,…
by Freek Van der Herten – 5 minute read – Edit
A couple of posts back I walked through the agent and tools we built on top of the Laravel AI SDK for There There, the helpdesk we're putting together at Spatie. I ended that post on a small cliffhanger. We hand the agent off to a streaming service that turns the SDK's response stream into events…
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]
