Laravel devs, now that coding agents can generate classes in seconds, has your approach to code organization changed?
Do you still keep things simple, or are you splitting things up more? 🤔
commit 476bfa8
I tell it to follow the Action Pattern of slim controllers and invocable actions, @MrPunyapal, but they do like to ignore me.
Most of my current work right now is iterating over rules and architecture tests. So I spend less time fixing after the first prompts
Definitely split things up more. More distinct classes that do one thing.