Jeremy Nikolic
@jeremynikolic.com
Laravel Core team focused on ☁️
Cheese enthusiast 🧀
Cheese enthusiast 🧀
Laravel Herd a gift that keeps on giving 🙌
April 23, 2025 at 11:37 AM
Laravel Herd a gift that keeps on giving 🙌
Most important part is to be building right ? 😁
How's it coming along?
How's it coming along?
February 8, 2025 at 5:21 PM
Most important part is to be building right ? 😁
How's it coming along?
How's it coming along?
Love a good retro logo!
Looks amazing 💅
Looks amazing 💅
February 5, 2025 at 8:41 PM
Love a good retro logo!
Looks amazing 💅
Looks amazing 💅
Learnt a ton by following the same path. React's docs are the best I've ever read I think 🤔
In-depth understanding of rendering/effect (wip), has needed researching out of the docs though
In-depth understanding of rendering/effect (wip), has needed researching out of the docs though
January 25, 2025 at 8:47 PM
Learnt a ton by following the same path. React's docs are the best I've ever read I think 🤔
In-depth understanding of rendering/effect (wip), has needed researching out of the docs though
In-depth understanding of rendering/effect (wip), has needed researching out of the docs though
That carpet, so fluffy 🤩
January 25, 2025 at 7:44 AM
That carpet, so fluffy 🤩
Love a good eureka moment 🙌
The testing pros you mention is already super nice as I find frontend component testing far from fun 😅
The testing pros you mention is already super nice as I find frontend component testing far from fun 😅
January 20, 2025 at 8:48 AM
Love a good eureka moment 🙌
The testing pros you mention is already super nice as I find frontend component testing far from fun 😅
The testing pros you mention is already super nice as I find frontend component testing far from fun 😅
Looking forward to your journey!
Feels similar to my situation while I'm still looking to find the time and give livewire another real chance 👀
I never considered it that way but the mind shift you mention, really resonate 💡
Feels similar to my situation while I'm still looking to find the time and give livewire another real chance 👀
I never considered it that way but the mind shift you mention, really resonate 💡
January 19, 2025 at 9:00 PM
Looking forward to your journey!
Feels similar to my situation while I'm still looking to find the time and give livewire another real chance 👀
I never considered it that way but the mind shift you mention, really resonate 💡
Feels similar to my situation while I'm still looking to find the time and give livewire another real chance 👀
I never considered it that way but the mind shift you mention, really resonate 💡
Warcraft 3 and AOE, yes sir 🫡
January 10, 2025 at 6:42 AM
Warcraft 3 and AOE, yes sir 🫡
I would have to double check but I think I'm using "Darcula" for since I can remember 💅
January 10, 2025 at 6:38 AM
I would have to double check but I think I'm using "Darcula" for since I can remember 💅
This is also the issue that led me to get accounted with lazy loading and php generators 💡
January 9, 2025 at 5:15 PM
This is also the issue that led me to get accounted with lazy loading and php generators 💡
Chunking helped as well as the following practices adopted since then :
- consider raw SQL when possible for updates on large datasets
- If eloquent/models then be mindful of loaded fields, relations, default $with, events etc
- reach for jobs more
- consider raw SQL when possible for updates on large datasets
- If eloquent/models then be mindful of loaded fields, relations, default $with, events etc
- reach for jobs more
January 9, 2025 at 5:15 PM
Chunking helped as well as the following practices adopted since then :
- consider raw SQL when possible for updates on large datasets
- If eloquent/models then be mindful of loaded fields, relations, default $with, events etc
- reach for jobs more
- consider raw SQL when possible for updates on large datasets
- If eloquent/models then be mindful of loaded fields, relations, default $with, events etc
- reach for jobs more
Can't recall the full details but let me try to lay down a summary of the case.
Data manipulation in migration/command on large model collections ended with model hydration increasing execution time and memory by a ton (this was back in laravel 5 i think)
Data manipulation in migration/command on large model collections ended with model hydration increasing execution time and memory by a ton (this was back in laravel 5 i think)
January 9, 2025 at 5:15 PM
Can't recall the full details but let me try to lay down a summary of the case.
Data manipulation in migration/command on large model collections ended with model hydration increasing execution time and memory by a ton (this was back in laravel 5 i think)
Data manipulation in migration/command on large model collections ended with model hydration increasing execution time and memory by a ton (this was back in laravel 5 i think)