It was a big week last week because PHP/JS Tek 2026 happened, which meant conference talks, post-conference sausage, and apparently a five-act musical. Here's everything I published this week.

Why Content Creators Need a Getting Things Done System

If you've ever sat down to work and spent the first twenty minutes just figuring out where to start, this one's for you. I walk through how David Allen's GTD framework maps directly onto content creation workflows. The short version: get it out of your head and into a system you trust so it's not taking up "space" inside your head.

Claude Code Commands That Get Smarter Every Time You Use Them

I kept correcting Claude on the same things run after run, which is exactly as annoying as it sounds. This post covers a pattern I landed on where custom slash commands accumulate a LESSONS LEARNED section that Claude reads at the start of each run so corrections stick instead of evaporating the moment the session ends.

Wurstcon: The Musical

After Wurstcon, someone started singing, and one thing led to another. I asked Claude to plan a five-act musical about the post-conference sausage-and-beer tradition, and I'm publishing the result unedited.

Advanced SQL: The Features You've Been Ignoring (But Shouldn't) - PHP/JS Tek 2026

Slides and links from my PHP/JS Tek talk on SQL features most developers walk right past, including triggers, stored procedures, views, and replication. If your app is doing in PHP what your database could be doing for you, this talk is the nudge you need to move some of your logic into your database.

Taming Time in PHP: Best Practices and Gotchas - PHP/JS Tek 2026

My other Tek talk this year covered the date/time handling mistakes that keep showing up in PHP codebases. Slides are linked and are worth a look if you've ever been burned by time zones or DateTime mutability.

The GitHub Issues Approach to AI Agent Orchestration

I lost an afternoon trying to remember which Claude session was handling which feature, and that was enough motivation to build a real system. This post covers using GitHub issues as a command center for working with multiple AI coding sessions, but having one place for context, requirements, feedback, and history instead of five browser tabs.