$ cat why-i-think-we-should-write-our-own-pr-descriptions-2.md

Why I think we should write our own PR descriptions

The author argues that developers should write their own pull request descriptions rather than leaving them to AI agents. Writing them by hand, they say, sharpens your thinking about the change and makes you a more useful teammate to reviewers.

blog.laravel.com10 Sept 2026 · 1 min read · summary

Read on laravel.com ↗

Agents can write your PR descriptions, but they shouldn't. Here's why writing them yourself makes you a better engineer and a better teammate.

source

This is a summary of an article first published by blog.laravel.com. The full piece is on their site.

$ articles --latest

Keep reading

Career · 2 min readYou're Not Going to Do That Again, Are You?The author recounts shipping a bug at Steals.com that charged every customer 25 cents, and how CEO Rett Clevenger responded with a single question instead of firing him. The piece explains how that grace shaped the author's own leadership as a CTO, encouraging engineers to own and report mistakes early.via guywarner.dev Laravel · 2 min readPHP Is Not Dead. It Grew Up.The author, a longtime PHP developer and former CTO, argues that modern PHP 8 with Laravel is mature, reliable, and well suited for production systems. The piece explains why he would still choose it for a company, citing hiring, shipping speed, and scalability.via guywarner.dev PHP · 1 min readBuild an Agent-Friendly CLI Tool in PHP and Run It Anywhere With CPXShows how to build a PHP command-line tool that outputs JSON, package it for Composer, and run it from any directory using CPX. Also covers how CPX differs from globally installed Composer tools, including isolated dependencies and automatic updates.via freek.dev