A strong PHP and Laravel batch, plus one timeless piece about SQL. The most immediately useful thing here: Laravel Prompts standing in for an entire admin panel, in 47 lines.
Brent Roose’s tempest/markdown started as a performance experiment and became a package. The story is the fun part: he built a naive single-pass, non-regex Markdown parser, benchmarked it against league/commonmark (5.9MB vs 21MB memory, 6.2ms vs 57ms), then someone on r/php sent a PR that merged tokenization and parsing into one pass and dropped it to 0.7ms: an 80x improvement over CommonMark. He walked it back slightly to keep extension points, landing at ~5x faster with frontmatter, code highlighting, responsive images, and tables built in. The real motivation isn’t raw speed (rendered Markdown is cached in production anyway) but escaping CommonMark’s bare-bones, copy-the-config-every-time setup. A great read on when building your own is justified.
The Apna Hive piece on Laravel Prompts as an admin panel is the most immediately useful thing in this batch. The argument: for 80% of “someone needs to manage something in production” cases, you don’t need Filament or Nova; you need a 47-line Artisan command with Laravel Prompts. The search() prompt does live database search as you type, form() builds multi-step wizards, progress() handles bulk operations with a visual bar, and confirmation dialogs guard destructive actions. The full walkthrough covers a real user-management command, a command hub pattern, PromptsForMissingInput for commands that work both scripted and interactively, and testing with Prompt::fake(). Build the command first; add the panel in six months if you still need it.
Mattias Geniar’s Don’t Mix $timeout Attributes and Properties is a beautifully-documented footgun. A base job class sets #[Timeout(40)] as a PHP attribute; a child sets public int $timeout = 1700 as a property. The child’s property silently loses, and the job gets killed at 40 seconds. The cause is subtle: Laravel’s resolution only uses the property when its live value differs from its declared default, and since 1700 === 1700, it falls through to the inherited attribute. A statically-declared property can never win that check. Mattias traced it, explained the PHP reflection limitation behind it, sent a fix upstream (merged into Laravel 13.x), and wrote it all up. The lesson: pick one mechanism per class hierarchy, and assert on the dispatched payload, not the property.
Leonardo Poletto’s 3 Years of Laravel Jobs is a fantastic data project. He subscribed to LaraJobs instant notifications in March 2023, never unsubscribed, and parsed 699 resulting emails with GPT-5 mini into structured JSON. Findings that surprised me: the Laravel market didn’t shrink: 2025 was the strongest year in the dataset. AI-adjacent job titles jumped from ~1.6% in 2025 to 11.1% in early 2026, but as a complement to Laravel, not a replacement. 74% of postings with a stated level are Senior, 88.5% are remote, and disclosed USD salaries average ~$103k-$134k. The whole pipeline is open source. A model for how to turn a passive email subscription into a longitudinal dataset.
Fagner Brack’s Learn SQL Once, Use It for 30 Years makes a point I keep coming back to. A SQL query from a 1995 textbook runs unchanged in PostgreSQL 18 today: same syntax, same mental model, 31 years later. Meanwhile a React component from 2015 throws errors on load and needs a full rewrite. His thesis: SQL endures because it’s built on relational algebra, a mathematical foundation, rather than on fashion. Even in the AI era, SQL teaches you to reason about problems logically without a wrapper masking the low-level logic. Worth sending to anyone early in their career deciding what to invest their learning time in.