Separating reads from writes and having smaller controllers that are easier to follow seems like an excellent case for CQRS. A lot of code out there is trying to do way too much, so I'm all for breaking things down into smaller responsibilities. @grmpyprogrammer#phptek
@grmpyprogrammer talking about "the blurry shape of what code should look like" takes me back, once again, to John Kary's excellent talk, "Rethinking Loops", from way back at Midwest PHP 2016. There's no presentation that's had a bigger impact on my career. https://johnkary.net/slides/loops/midwest-php-2016/#/
Proposal for a conference talk: How to configure #PHPStorm and all its tooling extensions (xdebug, phpstan, php-cs-fixer, etc.) to use a docker container consistently.
Ever wanted to build and publish a #Composer package but don’t know how? Come to my tutorial at 2pm CDT in PHPUgly Hall, and I’ll teach you how! #PHP#PHPTek
Speaking of cutovers, planning on merging the PHP 8.2 upgrade PR for Joind.in's API over lunch today. That PR also includes a lot of type enforcement that wasn't there before, so I expect stuff to break. Plan is to have things fixed by the time folks want to throw #phptek feedback in for the last session of the day.
The best way I've heard AI(llm) assistance with coding is it's moving the work to code review instead of code generation. Considering how bad most people are at code review... this will not end well.