ManuGlez  (@_ManuelGL_) header
ManuGlez  (@_ManuelGL_) profile picture

Father of two girls, full stack developer,Laravel lover and eternal learner.

España
Joined April 2011
Photo by ManuGlez  (@_ManuelGL_)Photo by ManuGlez  (@_ManuelGL_)Photo by ManuGlez  (@_ManuelGL_)Photo by ManuGlez  (@_ManuelGL_)Photo by ManuGlez  (@_ManuelGL_)Photo by ManuGlez  (@_ManuelGL_)Photo by ManuGlez  (@_ManuelGL_)Photo by ManuGlez  (@_ManuelGL_)Photo by ManuGlez  (@_ManuelGL_)Photo by ManuGlez  (@_ManuelGL_)
Europe - why innovate when you can regulate 🤡
30
11
1
160
15,169
I've worked with Laravel for 10 years. I've come up with 5 pretty random lessons from those 10 years. - - - - - - 1. Laravel became a full-stack framework. So should we. I'm a core PHP back-end dev, and that's what I enjoyed with Laravel. But then we had Vue, Inertia, TALL-stack, and now it's a mix. That shift to full-stack happened gradually, and then suddenly. But it reflects the market: everyone these days needs to be a full-stack, at least on some level. - - - - - - 2. You can structure your projects however YOU want. Laravel allows you a lot of freedom. Services, Actions, Repositories, Jobs, custom PHP classes, more strict design patterns - whatever you want. It's a blessing and a curse: newcomers are often lost what is the RIGHT WAY. And there isn't one right way. This comes with a caveat: the right way depends on the context of your project and the guidelines of the company you're working with. So whichever structure you choose, the goal is for others to understand it and maintain the project. - - - - - - 3. Most performance problems will be with DB. Whenever I see some page/API loading slowly, I check the Debugbar/Telescope first for the amount of queries. Then I check for individual slow queries. Then for the amount of RAM that the queries take: maybe they return too much data? So yeah, all of that Eloquent before any fancy restructuring, Octane or other optimization. - - - - - - 4. Rely on framework. Packages come and go. After 10 years with Laravel, I see so many packages abandoned or just not keeping up with the framework changes. So, I advice to trust only the packages that are: 1. Either from trusted creators who have reputation of maintaining things 2. Or, small enough so you would easily replace them in the future And quite often, framework itself has a very similar functionality as the package offers. Of course, packages are often a way to deliver project v1.0 faster. But, with every package, know the consequences for your v2.0 of your project. - - - - - - 5. Writing tests is NOT hard. Laravel team and especially Nuno Maduro went above and beyond so any developer would be able to start writing tests QUICKLY. So, if you are in a camp of "I don't have time to write tests", it's a lame excuse now. Heck, you can even generate tests with AI. - - - - - - Any other "global" lessons/advice from working with Laravel you would add?
8
25
128
7,701
ManuGlez  retweeted
If you'd rather watch this video on Youtube, we just uploaded it there as well. youtube.com/watch?v=-ezOz6vP…
I'm working on a Laracasts video today that will make 50% of you go...
20
10
4
87
25,994
The State Of Laravel 2024 survey has started! You can now participate to identify how the ecosystem changed over the past 12 months! Please RT for reach ❤️ stateoflaravel.com/?ref=2024
25
173
21
182
47,891
3
52
4
229
16,988
Let's rally around Ryan and his family. One of the most positive people in the PHP community needs our support. ❤️
So.... I have incurable brain cancer and I'm asking for your love & support 💖
5
155
2
885
83,220
Laravel 11 is now available. ❤️ Laravel Reverb is now available. 📡 I love this release. Beautiful simplicity is back. Thank you for all of your support and we hope you use Laravel to build amazing applications. We can't wait to see what you do. blog.laravel.com/laravel-11-…
56
591
113
2,196
165,818
ManuGlez  retweeted
🗓️ One month. 📼 One video per day. 👑 Everything you need to start building Laravel apps. 🙌 Free to all. Begins Tuesday, March 12th. laracasts.com
17
110
22
598
53,488
ManuGlez  retweeted
🤔 Have you installed `laravel-ray` as a dev dependency? 👀 Make sure to remove every `ray()` call in the code before deploying. Otherwise, your production application might break. 💡 An easy way to remove all calls is by running `php artisan ray:clean`.
3
11
62
6,230
ManuGlez  retweeted
Dude just destroyed the whole world of all software engineer’s dreams and beliefs 😆
152
110
68
2,637
666,549
ManuGlez  retweeted
If you missed it yesterday, I wrote about the "secret" (or lack of) to writing maintainable code yesterday. Zero code snippets and one Bluey reference, so it's worth a read. 🤣 blog.laracasts.com/posts/the…
4
8
2
46
7,121
👋 Calling all #Laravel developers! 🚀 Which VS Code theme do you find absolutely perfect while coding Laravel projects? 🎨 And hey, if there are any must-have plugins you swear by for a seamless Laravel development experience, please share them too! ⚡️ 🙌 #VSCode #LaravelDev
8
4
31
6,975
ManuGlez  retweeted
It's time. gowithphp.com/
50
310
39
1,302
171,469
ManuGlez  retweeted
💸 You (massively) asked for it and now it's here! The first pre-release of my @lemonsqueezy package for Laravel is out! Easily create checkouts, manage subscriptions, trial periods, webhooks and more. Enjoy! ✨ 📦 github.com/lmsqueezy/laravel
18
47
10
283
92,748
ManuGlez  retweeted
Do you want to be sure your type declarations are respected? We've added new rule to add declares to your files 🤙
1
5
28
3,727
The laws of the Internet: 1. Streisand effect. Any attempt to censor info on the web will lead to said info being widely spread. 2. Muphry’s law. If you leave a comment correcting someone, there will always be a mistake in it. 3. Cunningham’s law. The best way to get an answer to a question is to answer it wrongly yourself and wait for someone to correct you. 4. Armstrong’s law. The longer a conversation goes without mention of America, the more likely an American is to arbitrarily bring up the moon landing. 5. CAD’s theorem of topic culture. A smart is less likely to receive a reply than a stupid post because it leaves less to be said, but a really full and comprehensive post will bring the conversation to a halt. 6. Wadsworth’s content. The first 30% of any video contains no worthwhile information.
180
843
66
4,367
2,425,133