Started 99 Bottles of OOP, expecting technical design patterns.
Got hit in the face with thoughts about clarity, readability, and the human cost of code decisions.
Love it not being just about writing code β itβs about code people can live with.
Posts by Jeremy Nikolic
Laravel Herd a gift that keeps on giving π
π«‘
Laravel cloud getting the final polish π
We must ship! π
Most important part is to be building right ? π
How's it coming along?
Love a good retro logo!
Looks amazing π
Incredible logos for incredible projects, makes sense! π₯
Omw βοΈπ
Screenshot of a calendar app showing the schedule of Laracon EU 2025.
For folks attending #LaraconEU 2025: I've turned the conference schedule into a subscribeable calendar
user.fm/calendar/v1-...
Subscribe have the next talk right on your phone.
#laravel
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
Received a thank-you message from a former coworker.
He tackled a yearly task I had handled for several years using a documentated script I left behind π
A reminder: leaving a job on good terms and investing in clear, thoughtful documentation isnβt just professional β itβs kind π€
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 π
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 π‘
I'm a big fan of this new finally method for the pipeline helper in Laravel. Thank you @nunomaduro.com π
Warcraft 3 and AOE, yes sir π«‘
I would have to double check but I think I'm using "Darcula" for since I can remember π
Every little polishes count βοΈ
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
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)
Merry Christmas everyone! π
π»π
Hope you have a wonderful time with your loved ones π€
This week, we will do Laravel Livestream to discuss this fantastic year. My colleagues will join me @joshcirre.com and @nunomaduro.com .
Let's hang out together and have a good time β€οΈ
www.youtube.com/watch?v=LP8N...
Laravel VS Code extension ships Monday in public beta. β¨
Just had the easiest deployment experience ever π€―
I had set aside the rest of my evening so I could get my project deployed, and I ended up getting it done way quicker than I expected
I used to have the same guesstimate when it was time for deployment, there always was something going wrong and taking hours π
Super happy to hear Cloud did the job π€βοΈ
More time for you to spend on the code! π₯³
Way too cool π
First customer right here πββοΈ
Every winter, true sadness comes when I realise I'm out of Chocolate coated orangette π