|
Reviewing some newly written Laravel code. I made it clear to our dev team: "We're picking Laravel because, despite its known pitfalls, we know each other, and we trust our team to apply proper design principles, and the devs want to go with it. We'll certainly use it consciously" That completely disappeared within 1 week of dev work: all the anti-patterns present in the Laravel docs appeared immediately. It's so bad that it looks like going back to my high school code. Trouble from day 2. 4 comments
This is not a blame on the developers, BTW: they do exactly what's documented, and what they learned from the gazillion tutorials and guides out there. Dependency injection, separation of pure and impure operations, throw early / catch late, encapsulation, abstraction of data access: all very much out of the window, heh. It's SEP anyway, amirite? @ocramius if a tool is designed in such a way to make best practices difficult or impossible when using the tool as intended, it’s a bad tool. Period. @sarah more than the tool, everything around it. The tool itself is kinda like a good knife, with many other little knifes sticking out of the handle. |
Gregory's Server
People keep telling me "you can use Laravel properly".
I don't doubt it, but the average PHP developer is not experienced enough to make decisions that outlive their current task assignment.
It's hard to blame tools, but the tool is really just bad, from my PoV :-\