Matt Stauffer "Enterprise Laravel" - Laracon US 2023 Nashville

[@AlbertCloete]

The most best opinions I've heard in such a short time. So good. I need to share this at every company I work for.

[@sigma9]

Great guidance for the enterprise, those hoping to become enterprise, or really any Laravel dev that cares about their webcraft. Thanks Matt!

[@spaceemotion1]

Interesting bit at the end about Laravel and Symfony being buddies. I have been on a client enterprise project for the last year and within the team(s), we've constantly hit time sinks which wouldn't even have been there in Laravel, if it weren't for Symfony (or API Platform in this case). I feel that the "time to develop" is much shorter when using Laravel as a Framework instead of Symfony. Maybe it's because I know Laravel more intimately than Symfony (about 9 years now), but in over 6 years of doing on-and-off development with Symfony, I still have to dive deep into their, docs, source code and video lessions whereas in Laravel everything's quite intuitive.

[@JagdeepSinghKalsi]

Matt is one of my favourite speakers of all time - fast, focused and knows exactly what he is talking about.

[@mandjivatuva]

Fuck, great talk. Salut. Nashville was lit

[@adeolabada4662]

I may be wrong but I think the API-first approach is much better if you intend to build Mobile applications along with your web app. Great talk tho, learned a lot

[@shygrammer]

awesome stuff!

[@eduardpertinez4767]

Any news on the new edition of the book?

[@jp263]

The API first stuff is interesting. Makes me wonder what you think about HTMX?

[@RaymondMuller]

Great talk!

[@lukasneuschl]

I share the opinion on tech debt. Its nice to hear it out loud from someone else.

[@eu1492b]

Link from the slide: kzbin.info/www/bejne/q4K4qX2Fl92Hi9U

[@medilies]

29:53 Excuse me but something is wrong with the framework if it is built with PHP and senior PHP devs cannot build integrations without fighting the framework and being locked to conventions that are not PSR.

[@ramazanaktas748]

Bro, he is not even talking about that. Basically if you pick a fight with a built-in function and lose, don't blame the framework- which is true for literally every single framework and library. We use a library for pipeline in Spring Boot and tried to build my own for Laravel instead of using readily available pipeline impl. It didn't suck at best. The point is why would I blame it is not like the one there, that one is better? No, just use this and get over with it, it will make more sense down the road, it does. Still don't know php, tho.

[@zoba82]

Great talk!